When playing on a map where instances of the enhanced vehicle were spawned, either due to the AI-list, or directly by the user, the OMSI process fails to terminate normally ("app-hang" / "app-crash"). Trying to switch map / situation, also causes the process to become unresponsive.
Identified causes and resolution progress
We have not been able to identify the cause yet (OMSI emits nothing relevant in its logfile, even under -logall / -debug). For all we know it might be due to something as trivial as a Unicode character in some configuration file where Unicode is not "tolerated" by OMSI, or something as hard-to-overcome as OMSI being unable to handle reading from too many script files.
User-level workarounds
Quit OMSI via Windows' task manager, should it fail to gracefully terminate on its own, or hang during situation reload.
Symptoms
When playing on a map where instances of the enhanced vehicle were spawned, either due to the AI-list, or directly by the user, the OMSI process fails to terminate normally ("app-hang" / "app-crash"). Trying to switch map / situation, also causes the process to become unresponsive.
Identified causes and resolution progress
We have not been able to identify the cause yet (OMSI emits nothing relevant in its logfile, even under
-logall/-debug). For all we know it might be due to something as trivial as a Unicode character in some configuration file where Unicode is not "tolerated" by OMSI, or something as hard-to-overcome as OMSI being unable to handle reading from too many script files.User-level workarounds
Quit OMSI via Windows' task manager, should it fail to gracefully terminate on its own, or hang during situation reload.