TrailMyx's Master Rail Engine/Developer

[Khameleon]

I'm trying to do search for something after each way point, and i'm not sure if i'm going about this the right way....
it seems to be skipping over a bunch of WayPoints...

Code: [Select]

For %KhamRail 0 31
    {
    Event ExMsg #CharID 3 0 Railing to Position %KhamRail
    call %railsubs TM_RunRail %rail_label present %KhamRail FW
    Wait 2s
    FindItem xxx
    event ExMsg #charID 3 0 Searching....
    if #FindKind = -1
        goto end
    else
       ;Do something here
End:   
}


[TrailMyx]

Did you walk when you recorded the waypoints? 

You might want to query the present rail position and use that for the starting index instead of using "present".  From you're code, it looks like you are just single stepping through the rail.  Also, you might give this a go:

Code: [Select]

    call %railsubs TM_RunRail %rail_label %KhamRail %KhamRail FW


[Khameleon]

Yes.. I recorded them slowly, I tested them with your Generated, everything works fine.. but when I call it from my script using the above code, it rails way point 1-3 ok, then waypoint 4 is where waypoint 6 or 7 is.. and it keeps jumping up from there.

[Khameleon]

ok after further investigating..
each time it loops it keeps doubling for some reason.
from 1 to 2, to 3, then to 6.

[TrailMyx]

Here's another snippet to try:

Code: [Select]

set %continue #TRUE
while %continue
{
  call %railsubs TM_DetermineCurrentWaypointIndex
  if #RESULT <> 31 ; check for end of rail
  {
    set %next_index #RESULT + 1
    call %railsubs TM_RunRail %rail_label #RESULT %next_index FW  
    Wait 2s
    FindItem xxx
    event ExMsg #charID 3 0 Searching....
    if #FindKind <> -1
    {
      ;Do something here
    }
  }
  else
  {
    set %continue #FALSE
  }
}

What may be actually happening is the index is advancing by +1 at the end of the rail execution.  You may need to correct for this.  Using the above code, it should be easy to subtract one.  But give the above code a whirl because it should update you present rail index upon each movement.

[Khameleon]

 call %railsubs TM_DetermineCurrentWaypointIndex
seems not to be updating..
I keep getting a #Result of 0

I think the problem here is the first waypoint is 0
so it keeps trying to add 1 to 0

[TrailMyx]

Hmm, should be.  That's the index that runs at the core of the engine.  You wouldn't be running rails at all if that value wasn't updating....

[TrailMyx]

ok, try this:

Code: [Select]

set %railsubs tool_railengine30k.txt
set %rail_filename railfile.txt
set %rail_label  RAIL_LABEL1

call %railsubs TM_Initialize

call %railsubs TM_LoadRail %rail_filename

if #RESULT = #TRUE
{
  display ok Rail file not found
  stop
}
set #LPC 1000

set %continue #TRUE
while %continue
{
  call %railsubs TM_DetermineCurrentWaypointIndex
  if #RESULT <> 31 ; check for end of rail
  {
    set %current_index #RESULT
    call %railsubs TM_RunRail %rail_label present 2 FW
    Wait 2s
    display ok %current_index
  }
  else
  {
    set %continue #FALSE
  }
}

On thing to note about the rail engine is that the second index isn't the destination index, but the number of steps. 

Code: [Select]

call %railsubs TM_RunRail %rail_label present 2 FW

This steps once forward but does miss the first waypoint.  There's probably a ">" that should be a ">=" somewhere in the engine.  But you can live with the above code.

[Khameleon]

thats it.. TYVM, I thought that was the next waypoint in line.

[TrailMyx]

thats it.. TYVM, I thought that was the next waypoint in line.

heh, I forgot also!

[Alpha]

Just getting around to playing with this & it's GREAT !   I'm thinking ok I get the whole index thing & can run them forwards & backwards I'm Good!   Then I start thinking about the next step & go back to look at the callback Function & I realize I probably just need to understand it all 100% or I will be just using a small fraction of the POWER !   Anyway....   Thanks !

Only TM can write a Tool that Requires 25+ pages of PDF to use / understand correctly.  I LoL'ed when I opened the PDF & went "hmm more to this than I'm prepared for!"

[TrailMyx]

Heh yeh, I can't remember when I had the time to write that PDF.  lol - I must have been bored at one point in my life.

Well, I'm glad you're getting some use out of it.

[Alpha]

Is there some way to make it so that the rail engine doesn't take command of the mouse when it moves?

[TrailMyx]

There's around 8 instances of the "click" instruction in the rail engine.  Just comment all of them out. 

The next question should not then be "my rail doesn't work anymore while I play games on facebook"  heh.

[Alpha]

Yea thats what I ended up doing before I even read this.  I had forgotten about the "n" parameter for click though.   It wasnt ME.....it was the wife playing on facebook & shes happy now!

One last question just to confirm something.  When i record a rail being mounted / not mounted DOES matter correct?  Ive had a few instances where i ran a rail on foot when it was recorded mounted & it would get stuck but im thinking it simply cannot reach the Z-coord?