Jump to content

Recommended Posts

Posted

SimRail development team:

Hello.

I noticed that in the autumn rain or winter snow scenario, the following code would unexpectedly block program execution. This results in some scenarios where the virtual dispatcher is unable to open the signal.

RailstockGetPlayerTrainset().SetTimetable(LoadTimetableFromFile("Timetable.xml"), true)

As an example, in "08_Scenario_EIP_Wwa_Krk" and "04_Scenario_Tlk_Kato_Krk", the original codes are:

Comms("Caller_You", "Krk_04_tlk_KatoKrk_K7")
Comms("KO", "Krk_04_tlk_KatoKrk_K8")
RailstockGetPlayerTrainset().SetTimetable(LoadTimetableFromFile("Timetable.xml"), true)
coroutine.yield(CoroutineYields.WaitForSeconds, 10)
coroutine.yield(CoroutineYields.WaitForTrainsetPassengerExchangeFinished, RailstockGetPlayerTrainset(), TimeSpanCreate(0, 0, 0, 30, 0))
CreateRoute("KO_E18", "KO_Akps", VDOrderType.TrainRoute)
CreateRoute("KO_M8", "KO_E18", VDOrderType.TrainRoute)
CreateRoute("KZ_P", "KZ_E", VDOrderType.TrainRoute)

However, in the state of autumn rain and winter snow, the loading timetable will get stuck, resulting in failure to open the signal.

But if you open the signal first, then load the timetable. Both work fine.

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy