For performance or stability trouble, update first, then verify game files, disable DLSS, and disable Frame Generation in that official order before changing several graphics settings together.
Start with one reproducible scene
Record the game build, resolution, display mode, GPU and driver, DLSS state, Frame Generation state, and whether the symptom occurs at the colony or during combat. Revisit the same scene after each change.
This separates a useful comparison from a general impression. Base scale, enemy and projectile activity, resolution, and upscaling state can all differ between samples, so changing everything together makes the result hard to attribute.
Follow the official three-step sequence
Use these actions in order and retest after each one:
- Verify game files through Steam.
- Disable DLSS and repeat the same scene.
- Disable Frame Generation and repeat it again.
The developer's troubleshooting notice gives this sequence for performance and stability reports. Keep the order intact so a corrupt file, DLSS interaction, or Frame Generation interaction can be isolated rather than blended.
Compare colony and battle symptoms separately
A colony slowdown and a combat slowdown may not share one cause. For the colony, record population and the visible activity when the issue begins. For combat, record mission, encounter, enemy and projectile pressure, and whether the drop starts at loading or after action begins.
Official updates have improved specific scenes, tutorial combat, window-switching response, loading stability, and enemy or projectile behavior. That history is a reason to install the latest patch before diagnosing—not evidence that one patch fixed every performance case.
Lower load only after the official checks
If the three-step comparison does not isolate the issue, lower resolution or one heavy graphics setting and repeat the same scene. Preserve the original value so it can be restored. Do not delete broad configuration directories, edit the registry, or install an unverified third-party patch.
Official updates also added a maximum-frame-rate option whose documented use requires VSync to be disabled. Apply that condition only if the current interface still presents the option and its description agrees.
For an ultrawide scaling symptom rather than general load, use the ultrawide guide so aspect ratio, DLSS, and Screen.ini evidence remain separated.
Preserve information for a report
If the problem persists, collect the build, hardware, driver, Windows version, display mode, resolution, video settings, reproduction scene, and whether each official step changed the symptom. For loading problems, preserve the relevant log and save rather than deleting them.
Community troubleshooting around returning to base shows moderators asking for system specifications, video settings, logs, and saves and suggesting verification and SSD context. That is reporting guidance from a specific case, not proof that waiting or moving an installation fixes every system.
Stop when the comparison changes category
If the game exits to desktop or only one mission or save fails, switch to the mission-load crash guide. If the system does not match the published hardware table, use the requirements guide to describe that boundary honestly.