Minimum-spec evidence

Graphics-Intensive Scene Frame Drops

Official performance caveat

Steam warns that frame rate may drop in graphics-intensive scenes even on the published minimum, so a light tutorial is not a complete stability test.

Minimum targetEstimated 30 fps
DropsOfficially possible
Likely stressorsNot benchmarked
Recommended specTBD

Confirmed evidence

The store note explicitly allows performance to fall below the estimated target in intensive scenes. Official footage highlights layered clouds, dense city combat and massive enemies, but no primary source assigns an exact frame-rate cost to any one effect.

How to make the decision

Benchmark a repeatable busy mission or online environment before declaring a configuration stable. Average fps in a quiet sky can hide frame-time spikes that affect aiming and high-G turns during dense combat.

Evidence boundary

No official benchmark scene, CPU/GPU utilization profile, shader-compilation behavior or optimized-driver list is available. It would be speculative to blame a specific cloud, weapon or destruction effect without measurement.

Practical procedure

Use the retail version, record preset and upscaling mode, test both quiet and busy scenes, inspect low-percentile frame times and change one setting at a time. Publish measured results with full hardware details.

Verification checklist

  1. Use the retail version, record preset and upscaling mode, test both quiet and busy scenes, inspect low-percentile frame times and change one setting at a time. Publish measured results with full hardware details.
  2. Keep mode, platform, edition and account entitlements separate when applying this answer.
  3. Recheck the linked primary source after a store update, online-mode reveal or launch patch.

Graphics-Intensive Scene Frame Drops FAQ

What is the direct answer for Graphics-Intensive Scene Frame Drops?

Steam warns that frame rate may drop in graphics-intensive scenes even on the published minimum, so a light tutorial is not a complete stability test.

What should not be inferred yet?

No official benchmark scene, CPU/GPU utilization profile, shader-compilation behavior or optimized-driver list is available. It would be speculative to blame a specific cloud, weapon or destruction effect without measurement.