Separate the symptom
Menu only
Record whether only menus are slow. One Steam poster reports very low menu FPS, but that is a single community report.
Repeatable mission point
Use the same checkpoint and camera direction to compare frame pacing. Do not mix mission density changes with graphics-setting changes.
Random hitch
Record duration, first-run versus repeat-run behavior, background activity and whether every squad member sees it.
Use a controlled test
- Confirm the current game and GPU-driver versions.
- Close nonessential overlays for one comparison run; this is general isolation, not a confirmed fix.
- Choose one repeatable scene and record average FPS plus frame-time behavior if your tool supports it.
- Change one graphics option at a time.
- Restore the original option if the result does not repeat.
What Patch 1 actually says
The official note lists an Xbox Series X frame-drop fix when fire hits a Pathogen gas bag, multiple animation/cover synchronization fixes, and an enemy-density rebalance in an unnamed late-game mission. It does not state that all PC stutter is fixed or identify shader compilation as the universal cause.
What this page will not claim
No retrieved authoritative source establishes a DLSS state across every build, a best preset for each GPU, or a specific FPS gain from shadows, effects or post-processing. See Best PC Settings for a measurement-based setup process.
When to report it
Include CPU, GPU, RAM, resolution, display mode, driver, mission/checkpoint and whether the hitch repeats. A report tied to a reproducible scene is more useful than “it runs badly.”
Evidence used
Steam performance discussion with conflicting replies · Reddit launch discussion · official Patch 1
Community reports describe individual experiences and demand. They do not prove that every player, platform or mission has the same result.