Skip to content

Latest commit

 

History

History
63 lines (42 loc) · 3.64 KB

users-troubleshooting-after-a-game-update.md

File metadata and controls

63 lines (42 loc) · 3.64 KB
description
The game just updated, and you're crashing. Now what?

Users: Troubleshooting after a game update

Overview

Who doesn't know it? Your modded game is working, then there's an update, and from one moment to the next everything is a smoking crater. Unfortunately, that's normal: as long as you're living on earth, things fall down when you let go of them, and game updates break mods.

This page will give you a brief overview on what you can do in the situation described above by linking to the corresponding sections of the troubleshooting guide.

{% hint style="info" %} If you are on Linux and have exhausted these options, make sure to double-check the launch options, as Steam sometimes resets these between updates. {% endhint %}

What can I do?

The first step is to update your core frameworks. Check every mod on this page — make sure that you have a version from after the update.

There are no framework updates!

You're too fast, choomba: modders haven't gotten around to updating the frameworks yet. That leaves you with two options:

I updated my frameworks, but the game is still crashing!

{% hint style="info" %} You can try to temporarily disable any mod from the script section of known problem children. Sometimes, that fixes your issues. {% endhint %}

Your game and the core frameworks need to be version-compatible. You can make sure of that by

  1. resetting your install
  2. One by one, installing all of the frameworks you need
  3. Restoring your mods from the backup

{% hint style="success" %} Make sure to follow the instructions carefully – they will prevent you from running into a bunch of other issues. {% endhint %}

What other options do I have?

If these instructions didn't help you, there probably are no updates yet and you'll just have to wait. You can find warnings about version mismatches in these log files.

Of course, you can always

{% hint style="warning" %} You might want to deactivate ReShade before you start debugging. Especially after DLSS, it has been known to cause crashes.

Likewise, you'll want to turn off your antivirus to rule it out as a problem source. {% endhint %}