Are the red lights in the scenario planner when used on NTP supposed to be fixed now? I've just spent a while creating my first scenario using the HST on NTP using off the rails mode. I left Leeds okay and a 101 I'd placed at one of the first stations passed me as I was heading up the hill. Shortly before the 50mph limit on the curve to the right I was stopped by a red light. Another 101 I'd placed ahead of me was stuck in the station ahead, also blocked by a red light. I scanned ahead and there were several more red lights ahead even though there were no services present. A bit disappointing to try the planner for the first time, spend ages adding services only to grind to a halt within a few minutes when you actually start driving. Hopefully the ability to pre-populate the route with a random selection of services will be added in a later version. This could at least be used as a starting point rather than starting with a totally blank canvas.
Trains in the scenario planner will not move if you set the departure time before the time your train is meant to leave.
They are all set after or the same time as the player controlled train though. Or are you saying that if the train I control starts at 10:30, every other service should be 10:35 or later? I tried it again earlier with the same result. I did then change the player controlled train to one from Manchester and did manage to get just outside Leeds but the platform was blocked by a train that had failed to depart. I also passed the only other two services running from Leeds to Manchester both stuck at reds.
I think the problem was fixed in GWE in last week’s patch but NTP wasn’t included. It’s on the roadmap though.
NTP was fixed (or partially fixed) as you can now select more platforms at Leeds and Manchester. They also fixed the permanent red light bug at the start point (usually Leeds).
It is indeed true that AI trains in scenarios have to be scheduled to move after the player train. Otherwise they don't move at all. I think is regarded more of a feature of scenario planner rather than a bug, so I'm not sure there's any plan to solve it.
