Game will not start after Autumn update

Hello everyone.

The game will not start after the Autumn update. I get an internal error (see photo) but no stdout file is produced. I have verified the integrity of the files but this has not helped. I can revert to the previous build (35732) with no issues. Is there a known problem with one or more mods not co-operating with the update (I am currently subscribed to 643 mods) or is there a bigger issue? Is there anything else I should be trying?

Thanks for any help with solving this problem.

That's the problem. No stdout file is produced, so there's nothing to analyse. The game doesn't crash, it just refuses to start and shows the 'internal error' message.

Thanks, MaikC - that's what I thought I might have to do. Hopefully it won't take too long!

I have unsubscribed from all my Steam Workshop mods and removed all TF.net mods from my local mods folder, but the game still refuses to start with the Autumn update and shows the same internal error message. I've verified the integrity of the files but this makes no difference. There is at least 200 GB of free space on the disk and the previous build still works fine (with and without mods). As before, the game doesn't actually crash on starting - it just fails to start and no stdout file is produced. Any idea what to do next? Completely uninstall and reinstall the game? Any help will be gratefully received.

Thanks for responding.

Unfortunately, the only stdout file in the local/crash_dump folder is the existing one from the last time the game worked under the previous build 35732. I should have said no *new* stdout file is produced.

I can revert to the previous build by right clicking on the game in my Steam library and navigating to “properties” then “betas” and choosing b35732. The game will then start and play normally (and create a stdout file as normal).

If I close the game and then go back to the library and choose “none” in Beta Participation, Steam downloads the latest version of the game (autumn Update). I can then verify the integrity of the files and Steam says everything is OK. But when I click “play” (or start the game from my desktop) the loading screen appears for a second or two and then the internal error message is displayed. No crash message appears on screen and no crash report is created. When I look in the local/crash_dump folder, the only stdout file in there is the *previously existing one* from the last time the game worked under build 35732.

Are there any implications in deleting local/settings.lua and are there any files I should back up first?

Thanks for your help.

I have reverted to the previous build b35732 with no mods (other than the 22 built-in ones from Urban Games). I have several unmodded savegames that I can still play, and they play with no problems.

The latest stdout file shows I am using just the built-in 22 mods. However, when I investigate the settings.lua file, it seems to show I still have 122 active mods and the “activeFilters” entry relates to the last savegame I was playing before I tried to update the game with the Autumn Update (although *that* savegame actually had 212 mods enabled).

Is this what is causing the internal error when trying to update the game and could deleting settings.lua solve the problem? But if the mismatch between the stdout file and settings.lua is the problem, why does the game work OK with an unmodded b35732?

Many thanks to MaikC and Vacuum Tube. Deleting/renaming settings.lua has solved the problem and the game has successfully updated. After re-subscribing to all my mods, all my various savegames can be played.

Vielen dank!