Update from a clean configuration: disable mods before updating, make sure Engine.ini is not read-only, verify the Steam files, then enable Frame Generation and reload the game because the Week 1 version no longer applies the change in real time. If crashes begin only with Frame Generation on, switch it off, preserve the save and report the GPU, driver, build and trigger instead of adding more configuration tweaks.
Live verification board
Checked 2026-09-01. Status labels separate confirmed rollout from workarounds and unresolved reports.
Frame Generation now applies after a reload and should not activate before the world finishes loading.
Updating with mods installed or Engine.ini locked read-only can interfere with the change.
One tracked report says Week 1 resolved the transition crashes; other hardware reports still describe failures.
Do this first
- Close the game and make a dated backup of SaveGames before troubleshooting.
- Disable installed mods and remove read-only from Engine.ini if you previously set it.
- Install the Week 1 Update and verify the game files in Steam.
- Launch the clean game, select Frame Generation, then reload as the setting description requires.
- Test one repeatable route with ray tracing and overlays off.
- If only Frame Generation triggers the crash, turn it off and submit the build, GPU, driver and exact transition.
Why the reload matters
Week 1 changes Frame Generation so it applies after a reload instead of conflicting in real time. Toggling the option and immediately judging the same loaded scene can produce a false result; apply it, reload, then repeat one controlled route.
Clean the update path before changing more files
The developer-pinned patch post specifically warns against leaving mods installed or Engine.ini read-only during the update. Back up custom files, return to a clean writable configuration, update and verify first. Do not delete the SaveGames directory or paste an unrelated Engine.ini pack as a shortcut.
- Back up before removing custom files
- Disable mods rather than stacking more fixes
- Restore Engine.ini write access before updating
- Verify the Steam installation after cleanup
Not working and causing crashes are different
A missing or ineffective option needs a clean update, reload and hardware/driver check. A repeatable crash that disappears with Frame Generation off is a stability path: leave it off, use the game's crash diagnostics and report the exact transition. Do not assume NVIDIA and FSR reports share one cause.
When to stop troubleshooting
Stop after the clean update path reproduces the same failure. Reinstalling Windows components, disabling security protections or repeatedly deleting local data adds risk without isolating the cause. Keep Frame Generation off and wait for a version-specific developer fix if the clean test still fails.
Evidence log
Sources checked
External sources are linked for verification. Community reports describe symptoms and are not treated as universal fixes.
PlatformThe Week 1 UpdateOfficial Frame Generation rework, reload behavior and graphics-option changes.
↗OfficialThe Week 1 Patch - detailsDeveloper warning to remove mods and unlock Engine.ini before updating.
↗CommunityFrame generation causing crashesDeveloper acknowledgment plus mixed player results before and after Week 1.
↗Found a build mismatch?
Help keep this page current.
Send the page URL, platform, pause-menu build string, and a reproducible observation through the corrections desk. Game bugs still belong in the official developer channels.
Open corrections guidance →