Finish installing available updates, restart, then verify game files if crashes continue. For a GTX 10-series or RTX 20-series card, EA's 1.1 notes recommend testing Environment Geometry Detail set to Off. Compare the same scene before making another change; this is not a measured performance guarantee.
Choose the first check from the symptom
| Symptom | First comparison | Useful result |
|---|---|---|
| Fails to start or crashes during the same load | Update, restart, then verify/repair files | Whether the same load completes after each step |
| Low FPS on the named older NVIDIA cards | Options → Graphics → Environment Geometry Detail → Off | Whether the same route is smoother; do not infer results for other GPUs |
| Brief spikes during traversal | Repeat the same route with nonessential overlays closed | Whether the same locations still cause spikes |
| Combat turn stops while menus work | Use the enemy-turn recovery page | Do not treat an FPS change as proof of a repaired turn state |
Keep the comparison controlled
- 1
Note the game version, GPU, driver version, resolution and current preset. Finish any pending installation and restart the game.
- 2
For repeatable crashes, use the storefront's verify or repair option. Preserve saves; deleting progress is not part of this checklist.
- 3
Close nonessential background programs and retest. Restore them one at a time if this changes the result.
- 4
Use a graphics driver supported by the GPU manufacturer. If a problem began immediately after a driver change, record both versions when contacting support instead of choosing a random old driver.
- 5
Test one graphics option or preset at a time on the same route. Keep resolution and upscaler unchanged when evaluating a different setting.
- 6
If the problem remains, report the exact error and sequence plus the comparisons you already tried. For firmware or processor-instability questions, use your hardware manufacturer's support rather than improvising tuning settings.
A performance log that is actually comparable
| Field | Why record it |
|---|---|
| Route and duration | A quiet room and a busy fight are not equivalent workloads. |
| Resolution, preset, upscaler and frame generation | Generated frames and a lower render resolution change what an FPS number means. |
| Average FPS and visible stutter | An average can improve while intermittent pauses remain. |
| One changed variable | A useful result tells you which change to keep or reverse. |
We have not benchmarked this patch. Add your own observations rather than treating this table as expected FPS.
Stop repeating unproductive tests
Same repeatable crash
Once the basic checks fail, collect the error and reproduction for support. Repeating the same reinstall without new evidence may not narrow the cause.
Only one mission affected
Record the mission and save state. A global quality preset is not necessarily related to a mission-specific failure.
Frequently asked questions
Does Patch 1.1 mean all crashes are fixed?
No. A released fix list establishes what the developer addressed; it is not a guarantee for every PC, save or future bug.
Sources
What this answer is based on
Official EA and Steam material establishes the current rules and support status. Independent performance tests are labeled and never presented as developer guarantees.
- EA Patch 1.1 — September 9, 2026 Official released changes; checked September 19. Specific fixes do not establish that every similar symptom is resolved.
- EA troubleshooting and saving guidance Official troubleshooting and guidance on waiting for progress to save; checked September 19.
Checked September 19, 2026. Updates, support ratings and game rules can change.