derklaro

I'm running on Linux, not on Windows, but hopefully this can be looked at anyway. When trying to join a train or dispatch post on de3, the game just freezes. For dispatch posts it happens after the loading screen (join, short lag, freeze), for trains it already happens in the loading screen before the progress bar makes any progress (stays at 0). I attached the corresponding logs (first 2 are dispatch posts, last one is a train). Trying to join trains or dispatch posts on any other server works perfectly well without any issues. Also contacted someone else who is running on Linux, the same issue occurs on his end as well. If any other information is required, I'm happy to provide it. SimRail_log_2026-03-14_20-57-16.txt SimRail_log_2026-03-14_21-22-11.txt SimRail_log_2026-03-14_21-24-09.txt

On the next branch in Gr (maybe other stations as well) the short train routes between signals P[1-4] and the free route are not releasing automatically after a train passed them. They can however be released using ZD/ZW commands (after that they work as expected again).

Exiting from Warszawa Wschodnia towards Warszawa Podskarbińska you (might) come across signal C12 which permanently shows a stop aspect. However, due to the live map I was able to figure out that the signal is actually fake, and that I can just drive past it (next actual signal was entry signal of Podskarbińska). Would be nice if this signal could be removed/crossed out, to prevent confusion of other players. Route past the signal was set for IR 111XX (not sure anymore which one exactly I drove) on INT9. The map border is shortly after this signal as well.

I've compiled a list of things that look odd to me or are just wrong on the new timetable: https://gist.github.com/derklaro/cad559bb6c97d44ba2f684afda03c53c (checkmark indicating that the issue applies). Note that I can recompile the list (it's autogenerated) if needed and that it contains all points, even the ones that aren't playable in the game currently but mentioned in the timetable. Hope this helps. Explanation of the table headers: General Issues: Loco Type Missing - the locoType field is not filled in First Event Has Arrival Time - the first event in the timetable has an arrival time set Last Event Has Departure Time - the last event in the timetable has a departure time set Point specific issues: Point - the name of the point in the timetable where the problem was found Platform Invalid - the platform info is invalid, e.g. the specified platform doesn't exist or isn't formatted properly Stop Type without Overlay - a stopType is filled in the for the event, but the arrival and departure time are the same instant Overlay without Stop Type - the arrival and departure time and are not the same instant, but no stopType has been filled in (maybe that's intentional for marking optional technical stops?) Departure before Arrival - the departure time is before the arrival time (I don't think there is an occurence of that currently) Platform Without Commercial Stop - the platform/track info is filled in but the stopType is not set as a CommercialStop