Moderator: MacroQuest Developers
If you are strictly talking about the recording portion just change the number in red to like 18 or something and see if this helps. This should ensure that it only plots a location in your path file at a minimum of an 18 loc measurement from the previous loc.flightrecorder wrote:OK, stripped down the number of locs in my ini and this ran smoothly
I know see the finesse of the InitAPFVars speed value although this could get messy recording a complex path at a low value
What this leads me to think is that it would be very cool to have some kind of single loc record function that allows us to make keypress/simple function call selections of locs the toon is at, that are then being written to a single path file.
eg. run to certain point, record that loc, run to another, record that, etc, and each loc going into the same path file...?
I'm happy to manually edit loc files in initial creation, but this would be very cool... it also sounds diff to a newb like myself :-)
[edit]
I'm thinking something like a pause and a file append with file name specified perhaps?
Code: Select all
| --------------------------------------------------------------------------------
Sub RecordPath
/if n @RecordPathFlag==1 {
/if n @NumLocs==0 {
/varset LocArray(@NumLocs) "$char(y) $char(x) $char(z)"
/varadd NumLocs 1
} else {
/if n $distance($arg(1,"@LocArray($calc(@NumLocs-1))"),$arg(2,"@LocArray($calc(@NumLocs-1))"),$arg(3,"@LocArray($calc(@NumLocs-1))"))>[color=red]12[/color] {
/varset LocArray(@NumLocs) "$char(y) $char(x) $char(z)"
/varadd NumLocs 1
}
}
}
/doevents
/return