Hello. The following was observed specifically when the (latest) railx build was added to a 1.20.1 / Forge 47.4.10 modpack; Running Java 17.0.15; on fairly large world with 111 trains, most of them scheduled
Trains, which happen to be going over switches when the world is loaded in, take consistently a wrong turn, which causes trains to either report a navigation error, or to endlessly roll on a wrong path until something stops them (end of track, crash with an other train). After a few minutes that the world is loaded in, train stop consistently failing their navigation.
When the game is immediatly paused after entering, and left for a few minutes, it seems that fewer trains (if any at all), are affected by the issue. Alternatively, when the large railway network was segmented into multiple track graphs with the graph seperation tool, it seemed like that this issue lasted for a shorter time period after entering the world.
As to avoid throwing a wall of text at you, the following snippets from my debug logs can be highlighted
railx.mixins.json:middleTrack.TrackTargetingClientMixin: Class version 61 required is higher than the class version supported by the current version of Mixin (JAVA_8 supports class version 52)
[Server thread/ERROR] [railx/]: Mismatch in rail registry for railx:railways__track_oak_wide
Expected: 3329, Got: 3469
If necessary, i can provide detailed logs.
Hello. The following was observed specifically when the (latest) railx build was added to a 1.20.1 / Forge 47.4.10 modpack; Running Java 17.0.15; on fairly large world with 111 trains, most of them scheduled
Trains, which happen to be going over switches when the world is loaded in, take consistently a wrong turn, which causes trains to either report a navigation error, or to endlessly roll on a wrong path until something stops them (end of track, crash with an other train). After a few minutes that the world is loaded in, train stop consistently failing their navigation.
When the game is immediatly paused after entering, and left for a few minutes, it seems that fewer trains (if any at all), are affected by the issue. Alternatively, when the large railway network was segmented into multiple track graphs with the graph seperation tool, it seemed like that this issue lasted for a shorter time period after entering the world.
As to avoid throwing a wall of text at you, the following snippets from my debug logs can be highlighted
railx.mixins.json:middleTrack.TrackTargetingClientMixin: Class version 61 required is higher than the class version supported by the current version of Mixin (JAVA_8 supports class version 52)If necessary, i can provide detailed logs.