The short version. Zero Company leans harder on your processor than your graphics card, so the settings people usually reach for first are the wrong ones. Cap your frame rate at 60, turn on upscaling, then drop Effect Quality and Hidden Objects Detail before you touch shadows or textures. If it is crashing rather than stuttering, skip to the crash section: that is a different problem with different fixes.
Six days after launch there is still no patch, so everything here is something you do at your end.
Which problem do you have?
Stuttering, frame drops, bad performance but the game stays open: the settings section below. Crashes, black screen, or it will not launch at all: the crash section. They rarely share a cause.
Why the usual advice does not work here
Zero Company runs on Unreal Engine 5, and it is unusually processor-heavy for a game that mostly shows you a squad standing still. Independent testing at games.gg found the CPU pinned at 50 to 60 percent while the GPU sat at 70 to 80, meaning the processor gets there first and everything waits on it.
That matters because it changes the order you should work in. Turning textures down is the reflex, and textures are one of the last things worth touching here. A better graphics card will not fix stutter that the processor is causing.
The settings split roughly three ways:
| Load | Settings |
|---|---|
| Processor | Effect Quality, Hidden Objects Detail |
| Graphics card | Shadow Quality, Global Illumination, Reflections, View Distance |
| Video memory | Textures, Shading Quality |
Fix stuttering, in this order
1. Cap your frame rate at 60. Destructoid's testing found this made the single biggest difference of any change. An uncapped frame rate on a CPU-limited game produces exactly the uneven frame times that feel like stutter, even when the average number looks fine. This is a turn-based tactics game. You do not need 140fps.
2. Turn on upscaling. DLSS on Nvidia, FSR on AMD, XeSS on Intel, or TSR if you have none of those. Balanced or Performance. This is the cheapest large gain available and the visual cost in a game with a fixed tactical camera is small.
3. Drop Effect Quality. This is the first quality setting to lower, not the last. If your stutter shows up when a mission starts or when a firefight gets busy, this is the one causing it.
4. Set Hidden Objects Detail to Simplified. The other processor-side setting. Worth doing on any machine showing strain.
5. Only now touch the graphics-card settings. Shadow Quality first, then Global Illumination, Reflections and View Distance.
6. Textures last, and only if you are short on video memory. If your card has the memory spare, leave them up. They cost you almost nothing in the places that hurt.
A starting point
These are the values Destructoid landed on, tested on a Ryzen 7 5700X with a Radeon 9060XT and 32GB of RAM, and aimed at machines nearer the minimum specification than the top end. Treat it as a baseline to claw quality back from, rather than a target.
| Setting | Value |
|---|---|
| Frame rate limit | 60 |
| VSync | Off, unless stutter persists |
| Upscaling | FSR / DLSS / TSR, Balanced or Performance |
| Effects | Medium |
| Hidden Objects Detail | Simplified |
| Shadows | Low |
| Global Illumination | Low |
| Reflections | Low |
| Shading Quality | Low |
| View Distance | Low |
| Post Processing | Medium |
| Textures | Low, or higher if you have the VRAM |
| Frame Generation | Off |
One point of disagreement worth knowing: Destructoid suggests turning Environment Geometry Detail off on older cards, while games.gg found newer cards gain almost nothing from disabling it. If your card is recent, leave it alone.
If it crashes rather than stutters
Different problem. Work through these in order, and stop when it holds.
1. Verify your game files. Corrupted or partial installs are the most common cause of a launch crash, and this costs you nothing but time. Steam: right click the game, Properties, Installed Files, Verify.
2. Install the DirectX runtime and Visual C++ Redistributables. Unreal Engine 5 games need current versions and will crash on startup without them. This catches a surprising number of "it will not launch at all" cases.
3. Update your graphics drivers. Nvidia, AMD and Intel all shipped drivers around this launch window.
4. Try disabling Resizable BAR. ReBar lets the processor address all of the card's memory at once, and some games do not cope with it. Turning it off in your motherboard firmware has resolved immediate-crash reports for this game.
EA also has an official troubleshooting page for the game, which is worth a look before you go further.
Our own experience, for what it is worth
We had two crashes in our first hour on launch day and none since changing graphics settings. That is one machine and not a controlled test, so treat it as a data point rather than a diagnosis. The fixes above come from testing and reporting by others, linked throughout.
What we are not recommending
Community config files and engine tweaks. They exist, some people report good results, and they involve editing files the game does not expect you to edit. If you are comfortable with that you do not need us to tell you where to find them. If you are not, the settings above get most of the benefit with none of the risk.
Buying a new graphics card. Whatever else is true, this is a processor-limited game. That upgrade will not fix the thing you are trying to fix.
The details
- Settings values and the frame-cap finding: Destructoid, tested on a Ryzen 7 5700X and Radeon 9060XT.
- The CPU-versus-GPU load split and the utilisation figures: games.gg.
- Crash fixes are the ones that recur across player reports and EA's own troubleshooting page.
- We have seen no EA statement about the game's processor load, so nothing here should be read as the publisher's position.
- Our review covers the game itself, and the difficulty guide covers the settings that change how it plays rather than how it runs.
