... which was me!
mbonwick is correct, the .pretrain command is used to make the signals change.
My Aln Valley route was written well before openBVE was even a twinkle in Michelle's eye, so there will probably be a number of issues when you try to drive it in openBVE.
I'll see if I can look at it this week.
Regards
eezypeazy
--- old post above --- --- new post below ---
... and, having looked at the route and asked a question over on Michelle's forum, the error was, as we suspected, down to my poor coding... I really must improve!
The problem was caused by using both .runinterval and .pretrain commands. The easiest solution for Adam (and anyone else) is to open each route in Notepad and remove the .runinterval 0 statement, which is quite near the top of the file.
But a reminder that this route was written some years ago, and there are transparency issues when running it in openBVE. I will address these later this year.
Regards
eezypeazy