Recently some stations are showing strange behaviors.
Station A and Station B have no direct connections except for a mail train. But p****engers have appeared trying to travel between these stations.
Station C has all services withdrawn for more than one year. However it is still appearing as green, and p****engers are still waiting for trains that have been withdrawn.
Are there any ways to force re-calculations of routes?
1.) Goods (as well as p****engers and mail) don't need a direct connection. They will try to find a possible route with the least number of transfers (up to a maximum set in your config files... usually something between 7 and 9). So they may in your case travel from A to C, then to D, E, F and only then to B
2.) Maybe you have only sent all the ****igned vehicles (or just one) to a depot, without selling them, or ****igning them to new lines/schedules? In that case for the game the line is still active. So check if there's any vehicle left on your map (incl. all depots) that still have C as a stop in their schedule.
Thanks for replying. But this doesn't help in my situation.
In Case 1, P****engers are waiting for a non-existant direct connection from A to B. There is a indirect route with one transfer, but they have ignored it.
In Case 2, no trains have stopped to Station C for 1 year. All routes used to call have been deleted and all trains previously used are sent to other routes. Station C occansionally turn yellow for a while then back to green again. Waiting p****enger number unchanged since station closure.
So I'm wondering whether there is a way to force the program to redo the routing to and from these stations.
Hmm, which version of Simutrans do you use and which pak? And do you use normal Simutrans or Simutrans Experimental?
I am using Simutrans stable 102.2 with pakBritain 1.05.
Sorry, all I can say is that this usually happens when a there's still a vehicle scheduled but forgotten (in a depot). If you are sure there's none left anywhere... then I have no idea. Maybe it is a bug then. You could try and see if a nightly also behaves like that or if this was a bug that has been corrected since...