STAR WARS Zero Company Stutter & Optimization Notes

The official answer for poor framerate

The launch FAQ addresses this question directly, under the heading of what to do if you experience poor framerate or stuttering on the recommended specification. Two things in that answer matter more than any community workaround.

That is first-party guidance, and it is specific: the 60 FPS at 1440p target assumes an upscaler is on. If you have forced upscaling off in pursuit of a sharper image, you are no longer running the configuration the recommended tier describes. Details of both tiers are on the PC requirements page.

• Upscaling is the intended route to the recommended target. Reaching 60 FPS at 1440p “is best accomplished using the game’s recommended default setting: TSR or vendor upscalers DLSS/FSR.”
• “Native” was removed from the published specifications before launch — the FAQ describes this as being “fully transparent ahead of launch.”
• The game is CPU bound. The FAQ says the team “validated the game is actually more CPU bound,” and that changing individual graphics settings has less effect on framerate than in other genres.
• There is an official troubleshooting destination for players who still see problems after that, on EA Help.

Why the CPU-bound note changes your first move

Most stutter advice starts with graphics settings. If the developer’s own profiling says the bottleneck is usually the processor, dropping shadows and textures is the wrong first lever — it can leave the framerate roughly where it started and lead a player to conclude the game is simply broken.

The FAQ does not publish frame-time data, name affected CPUs, or promise that upscaling resolves every hitch. It establishes where the load sits and what the default setting is meant to be. Everything past that still needs measurement.

What the dated community reports say

The August 28 Steam snapshot includes player concerns about stutter and optimization. Those reports do not, by themselves, establish one cause, one affected hardware group, or one reproducible fix, and they are not the same kind of evidence as the FAQ answer above.

Build a useful reproduction note

Before calling a setting a fix, record the game version, operating system, CPU, GPU, RAM, driver, resolution, preset, upscaler setting, and the scene where the hitch occurred. A consistent note makes a community report easier to compare without claiming more than it shows.

• Compare the PC against the official minimum or recommended tier.
• State whether the report concerns average performance or brief stutter.
• Record whether TSR, DLSS or FSR was enabled, since the official target assumes one of them.
• Keep community anecdotes separate from measured frame-time data.

No community fix is asserted as universal

Beyond the official guidance above, this page does not prescribe an undocumented graphics setting, driver workaround, file change, or launch option as guaranteed. Any further fix should be tied to a dated patch note or reproducible, attributable testing.

Do not rewrite reports as official defects

Steam review sentiment is useful context, but it is not an engineering diagnosis. Optimization concerns stay labelled as community-reported until the developer or a controlled test provides stronger evidence — and where the developer has spoken, as in the FAQ, this page quotes them rather than paraphrasing. The rest of their launch answers are collected on the launch FAQ page.