jeroezie Posted Friday at 04:49 PM Author Posted Friday at 04:49 PM It could be a bug in the new version of SimRail. I have not done a test since the 13-12-2024 update.
jeroezie Posted Saturday at 02:49 AM Author Posted Saturday at 02:49 AM (edited) On 12/20/2024 at 11:45 AM, Indiana said: I'm ready to go but signal won't change... The stuff down here won't be of any help completing the scenario, because the bug with departing from DGZ is still prevalent in my test run. I will do more testing soon. I had already typed the whole thing in, so I am sending it anyways. It seems like, a bunch of shunting routes at Dandowka have disappeared/been removed in the current game version. You could circumvent this issue by changing the signal the players train spawns at, to the SDn_T signal, where the train departs after shunting. You will have to wait for the planned departure time still, and in my trail run the bot 42948 showed up a couple minutes late (15:09) and the signal trigger needed in order to depart, is only created when bot 64948 has reached about halfway the platform. Only then you can call the signaller successfully. Manipulate the mission.lua file the following way: Look fore line 20, replace "SDn1_H" with ("TYPO -> SDN_T") CORRECT -> "SDn_T" The result should look like this: PlayerTrainset = SpawnTrainsetOnSignal("Treintje", FindSignal("SDn_T"), 36, false, true, false, true, Please let me know, if this is successful. The trick should work with all three version of the scenario. Edited 2 hours ago by jeroezie Corrected a typo
Indiana Posted 12 hours ago Posted 12 hours ago W dniu 21.12.2024 o 03:49, jeroezie napisał(a): The stuff down here won't be of any help completing the scenario, because the bug with departing from DGZ is still prevalent in my test run. I will do more testing soon. I had already typed the whole thing in, so I am sending it anyways. It seems like, a bunch of shunting routes at Dandowka have disappeared/been removed in the current game version. You could circumvent this issue by changing the signal the players train spawns at, to the SDn_T signal, where the train departs after shunting. You will have to wait for the planned departure time still, and in my trail run the bot 42948 showed up a couple minutes late (15:09) and the signal trigger needed in order to depart, is only created when bot 64948 has reached about halfway the platform. Only then you can call the signaller successfully. Manipulate the mission.lua file the following way: Look fore line 20, replace "SDn1_H" with "SDN_T". The result should look like this: PlayerTrainset = SpawnTrainsetOnSignal("Treintje", FindSignal("SDn_T"), 36, false, true, false, true, Please let me know, if this is successful. The trick should work with all three version of the scenario. It won't work for me... 😞
jeroezie Posted 2 hours ago Author Posted 2 hours ago (edited) 10 hours ago, Indiana said: It won't work for me... 😞 Could you discribe what happend? And show your missio.lua after the edit please? I also noticed, that I made a typo. The correct signal discription is SDn_T, not SDN_T. (The whole line of code that I posted was correct, the part where I discribe the instructions was not.) Edited 2 hours ago by jeroezie
Recommended Posts