Ok, so today I was making a scenario in tsw3, when I encountered a very strange glitch. Every A.I train I put in the scenario dose not move and will stay at the beginning station for as long as the scenario lasts
That happens in TSW2 if you set the AI start time to be before the player start time. Have you done this?
Yes becuz my main service starts at 8:45, but there is a service that starts at 8:15. Though it effects every train.
Maybe every train starts before the player? The way to get around this is to set the start times for the AI to be the same as or after the player start time, then move the start location to where the AI should be at that time. Example: The train leave Brighton station at 8:15, and arrives at Gatwick Airport Station at 8:45, before continuing to London Victoria station. Instead of starting the train at Brighton at 8:15, start the train at Gatwick at 8:45, and then tell it to go to London Victoria.
I find the key to making your scenarios work with this scenario planner is to have a rough idea of how long it takes for trains to travel between stations. You can do this by timing it or if it’s a modern route you can look at the real timetable. It does not have to be precise as you can only start in 5 minute increments anyway. Screenshot the times or write them down and use it when placing trains. This means you will have trains arriving where you want, when you want. Also useful for setting up red signals as you can have a train in front by just enough to give adverse signals. Unfortunately even the best planned scenarios will require a few practice runs to smooth out any issues and you are always at the mercy of bad or broken pathing from the developers.
You need to make IA trains depart not before the player train. Since nothing is timetabled, you can let the player train wait a while. Trains will get a green signal aspect in the order you place them in the scenario.
