Christopher Lees

May well be fixed by the build from today, but without the offending file I can't check.

32-bit .Net only supports ~1.5gb of RAM per process, which is going to be why Object Viewer is suddenly closing on you. I don't think it's a leak per-se, just...

Black textures are also a probable side-effect of hitting the 32-bit memory limit. Basically, if the process runs out of memory, bad / unexpected things can and do happen.....

Unfortunately, XP went end of life 10 years ago. For that matter, Windows 7 is technically EOL, but at present there's no real support difference between Windows 7 and 10....

I think this probably needs a couple of things changing: 1. Change **NearestTrain** to consider TFOs. 2. Add a new animated instruction to return the current rail. For static objects,...

Build from today will now take into account TFOs when looking for the nearest train. I've also internally re-named **TrackFollowingObject** to **ScriptedTrain** The XML has not changed at the minute...

This is 'intended' behaviour (or at least not directly a bug), as the TFO is currently closest. They would have been activated in the same way by a RunInterval /...

That's correct at the minute. It's on the list of things to sort out, but my initial implementation has some pretty far-reaching design changes which I'm not totally happy with....

Thanks. I'd overlooked the edge-case where the rail we switched to existed in the first block. I think that should work now.

PlayerPath seems to work from one rail to another here at the minute, but I'm testing with somewhat less complex files to start with :) I haven't yet got as...