The International Simutrans Forum

 

Author Topic: Further desync investigations  (Read 206 times)

0 Members and 1 Guest are viewing this topic.

Offline freddyhayward

  • Devotee
  • *
  • Posts: 661
  • Languages: EN
Further desync investigations
« on: June 07, 2020, 11:11:39 AM »
I made a thread earlier about a desync (then-crash, though the crash itself was fixed: https://forum.simutrans.com/index.php/topic,19892.0.html) occurring when a schedule was being edited is interrupted by a force-sync. I have since discovered that this occurs in many more cases, including:
- renaming a stop
- renaming a city (which shouldn't be allowed regardless)
- renaming a line
- renaming a convoy
- renaming an industry/factory
What all of these have in common is that they are all tool actions created when a window closes. In this case, the windows are closed as a result of the force-sync.
However, there are some actions that fit this description that do not cause desyncs, including:
- renaming a player
- creating or renaming a marker.