a dodgy workaround, but try moving the delay just by -100Quote:
could be different issues then. Mine seems pretty linear. I've watched the bot and all the missions that started after the threshold(it seems) the cursor was just lagging slightly behind...enough to fail.
my log doesn't have any over my 34040 that was a win
being slightly early is always the better option
by default, on this crap computer, i have all missions set to 1800, even though i record ON THIS COMPUTER at 2000 (all default missions included in downloads use the files from this computer). i really dont know why that is, but that just is. however, when using THE SAME FILES on my brothers better computer, i can keep the delay there at 2000 and it works perfect.
/shrug
i am currently in the process of making event files for all missions (except maybe the minefield, but ill see), and will include them in the next update (or as a temporary download until the next update is available)