MacSergey
Intersection Marking Tool error on load
IMT Stable
Windows 11
Needs to be updated because of game update.
Drops out an error after game loading and removes all marks that was made to intersections.
From my own testing, it seems to be that all of MacSergey's workshop mods have the same issue where games that used those mods will cause a crash since the update. This does not happen with any other mod that has not been updated for a while.
Starting a new game with the mods enabled will cause the save to fail when you save the game. With the mods disabled, the game can be loaded and saved without issue.
From my own testing, it seems to be that all of MacSergey's workshop mods have the same issue where games that used those mods will cause a crash since the update. This does not happen with any other mod that has not been updated for a while.
Starting a new game with the mods enabled will cause the save to fail when you save the game. With the mods disabled, the game can be loaded and saved without issue.
Same issue here when testing with the following mods by MacSergey:
- Intersection Marking Tool v1.14.5
- Node Controller Renewal v3.5
- Building Spawn Points v1.4.1
I’m able to create a new city, but the game crashes when I try to save. I’m running the game on Arch Linux. With other mods (non-MacSergey), the game runs and saves normally.
Interestingly, the only MacSergey mod I use that still works without issue is Network Multitool v1.3.5.
Has anyone found a workaround or fix for this?
I am running an Arch-based distro and have had zero issues since the game update. I have heard that unsub/resub fixes the issue as it is a bug with Steam Workshop erroneously removing mod files. Can't confirm that, but worth a try.
I've been having the same issue as @TheDevick using the Steam flatpak. Saving the game gives the following error in the Player.log on crash
Player.log: 115,093ms | [IntersectionMarkingTool][115.1332] Start save map data
Receiving unhandled NULL exception
#0 0x00724fe26fdec0 in __sigaction
#1 0x00724fe26fe478 in (Unknown)
It seems to be mono related and occurs even with the Legacy Runtime.
