jeroezie Posted Thursday at 12:42 AM Posted Thursday at 12:42 AM I noticed some bot trains passing cleared signals in my scenario, and after passage, the signal remained clear like the train has not passed at al. This makes it impossible to have signals react to the bot trains, the set route will remain locked eternally. This is very annoying, since it breaks all my self made scenario's. The shunting movements in the yard seemed unaffected, I saw it only with train movements. I do not know, if spawning distance and train server state played a role in this. Bug observed in the next SP branch, build 03/08/2026 - 19:26.
jeroezie Posted Thursday at 12:49 AM Author Posted Thursday at 12:49 AM (edited) I will provide the scenario where I was testing and noticed the bug here, log file included. Easy train to see the signals to remain clear after passing (although it does require to play until reaching DGZ): 1429, seen at DGZ signals B, G11 and O. 37130, signal DGZ S102 and Z. Jeroezie_Lazy_Katowice_Cargo (13-085-2026-0248).zip SimRail_log_2026-08-13_00-45-02.txt Edited Thursday at 12:59 AM by jeroezie
jeroezie Posted Thursday at 12:56 AM Author Posted Thursday at 12:56 AM Edit: I just noticed the signal leading to the players train remained clear too, here DGZ signal F with the players train behind it. When setting routes using VD it is working normally (as long as it does not interfere with any already set route).
jeroezie Posted Thursday at 01:27 AM Author Posted Thursday at 01:27 AM I just realised I overlooked an important detail. During every try I did, all shunting movements and train around Lazy worked normally. So the bug did not manifest itself over their or during that time. I am very sure about that, the player cant even leave the spawn point if multiple bot trains do not pass as planned.
SIMRAIL Team Admin BOT Posted Thursday at 09:22 AM SIMRAIL Team Posted Thursday at 09:22 AM Thank you for reporting this issue. A similar problem has already been reported by other users. Dziękujemy za zgłoszenie tego problemu. Podobny problem był już zgłaszany przez innych użytkowników.
Recommended Posts