Applies to: Windows and Linux
Topic: Linux and crashes
Everything worked, then you updated Azimuth, Extra Options or a mod, and now the game crashes at start, crashes in menus, or loads forever.
Why
Each Azimuth version changes the game in memory. Mods built for another Azimuth version patch the wrong places, and the game crashes. The same happens when an old file from a previous version is left behind.
Fix
1. Check the versions. If you play FH2MP, the launcher decides: see [Which Azimuth and mod versions work with FH2MP](/tutorials/supported-versions). Don't update Azimuth ahead of the launcher.
2. Press PLAY in the launcher. It puts the right Extra Options, Mod Platform and HonkHonk back and removes the old azimuth-tls.dll.
3. Turn off your other mods and start again. If it works, turn them back on one at a time to find the one that isn't updated yet. See [Turning a mod off without uninstalling it](/tutorials/turning-mods-off).
4. Still crashing? Start fresh. Back up data\titles, install Azimuth into a new empty folder with the launcher's setup wizard, copy titles back, and add mods last. See [Keep Azimuth, the game and mods in separate folders](/tutorials/keep-folders-separate).
Mods that haven't caught up
Some mods only list support for an older Azimuth. Check the mod's page for a version made for yours before you update Azimuth, or keep a separate install of the older Azimuth for that mod (offline only).
Reporting the crash
When the launcher offers to send a crash report, send it. Otherwise collect the files in Which logs to send. A crash in d3dcompiler_47.dll (FH2 Mod Platform) or DWrite.dll (FH2 Mod Platform) usually means one of the platform's mods crashed, not the platform: the report in fh2-mods\crashes names the mod.