Bugs on Multiplayer and Temporary Solution
Before you start to read
1.All these solutions MAY NOT always effective for AI accidents.
2. This small handbook only shares what CN community has found available when dealing with similar problems.
3. If it doesn’t work, DO NOT blame us.
4. Trying to solve a traffic jam is a tough job, so in this handbook I only draw the situation instead of using in-game screenshots.
Preface
In this page, we conclude some common reasons about why sometimes there are many trains blocked at one station. Since this handbook is pretty experience-oriented, therefore, you should only take what we advise as a reference, not something that will 100% work.
Also, due to the differences between different sections, the situation may change if one station can actually be dispatched by humans.
If there isn’t any description about stations’ conditions, please consider it as one station is human, the other is AI.
Hope this page might be helpful, and I’ll update it from time to time.
3N (SimRail CN Community)
2023.4.22
1.Two trains contradict with each other (2023.4.22)
A brief image of the situation (happened on EN3)
Possible cause
The situation is caused by a contradiction between Sosnowiec Południowy and Sosnowiec Dańdówka. Now we use SP and SD to represent these two stations:
- SP: please accept 42940
- SD: no
- SP: please
- SD: no
- SP: (use substitute signal to send 42940)
- SD: (just accept 24939, and don’t know what to do)
Solution
Since Line 62 & 171 has very long sections, and the limit speed is slow, you can derail one of them by driving at 150km/h (reverse 24939 to last station until you meet a red light, and accelerate by putting your handle to 100%)
2.AI block all trains and refuse to send them (2023.4.22)
A brief image of the situation (happened on CN1)
Possible cause
There is a small possibility that AI sometimes would stop working, if the trains are coming together, especially when a train comes on the route with semi-automatic interlocks. Like in this example, 442023 was blocked because it comes from the semi-automatic track of Łazy.
Solution
Just consider AI as a part-time noob, who may forget which train he should receive first. So, you can just use telephone, select “XXX can be accepted”, and it may start to work. In this example, we tell Łazy you can send 442023, and the problem is solved.
Notes (2023.4.23)
This issue happened again on 4.23, IT1, at Dąbrowa Górnicza. Train 644010 was blocked by AI, and other trains are affected by the incident.
3. Huge number of trains stuck into one section (2023.4.22)
A brief image of the situation (happened on CN1)
Possible cause
This is caused by a lack of cooperation between stations AI again. It’s very common at Sosnowiec Główny(SG), AI would always accept the permission to proceed lower than 20km/h. Because there is a single-track between SG and SP, then the trains have to wait. While sometimes Katowice Zawodzie even use left-track which would totally block the route.
Solution
Send it gradually, and when there is a left-track train stopped at there, you can either give a substitute signal to 24XXX, and call somebody to derail it or crash it with that left-track train.
Another solution is to let 42XXX enter SP, and send it to the derail track (which would be track 6)
4.Ghost trains (2023.4.22)
A brief image of the situation (happened on PL4)
Possible cause
It is based on the AI logic to deal with the signals. When AI was approaching the stations, and the entry signal was red, AI would start to brake. If the signals turned green when AI was just about to stop there, AI would get confused about the situation and just keep stopping without any movement.
Solution
Call somebody to drive that train.
We’re not sure about why using this method cause this problem:
