Christopher Lees

The immediate cause of the is that you're issuing a .RailEnd command at the same position as the switch. If you switch your rails to null and move the railend...

Build from today *should* sort this.

That was intended to control spring return switches. Haven't implemented it yet as it got a little complex. to make work correctly. Must update the documentation, thanks....

Made a couple of changes which will help a bit. Essentially, was only changing the index of the front axle follower accidentally on trailing switches, However, ending the track at...

Again, there is only one of me, and I've got limited free time to work on this...... I haven't got as far as investigating the void track issue properly yet,...

Made a few changes for the current build. I think this probably fixes what you were seeing (running through a reverse switch with the 'wrong' direction set could get into...

Current build makes most things OK. However, the use of the .Turn command and the .Switch / .SwitchT command in a routefile are no longer supported, and an error will...

I wouldn't reccommend re-using rail indicies at all where switches are concerned- Keep anything drivable completely separate. Track elements are a linear array, which really doesn't work too well for...

Fixed the AnnounceAll rear axle trigger issue, which was unintentional. Adding a new event type which triggers on all axles would possibly be do-able, although I'm not sure that your...

Apologies, errant return statement that I thought I'd removed....