PC Requirements & Performance

Official minimum

Steam lists Windows 10 or 11, i7-10700K or Ryzen 5 3600, 16 GB RAM, RTX 2060 Super 8 GB or RX 6600 8 GB, DirectX 12 and 30 GB.

An SSD is explicitly required. Confirm installation there before tuning around a storage bottleneck.

Clean first launch

Install current GPU drivers, close unneeded overlays and allow first-launch asset work to finish before judging steady performance.

Record resolution, preset and the exact failing scene. A vague report cannot distinguish traversal stutter, sustained load or a crash.

One-variable ladder

Lower resolution or one costly setting, replay the same scene and record whether frame time improves.

If performance does not respond to graphics load, restore it and investigate CPU, storage or background activity.

Resolution or upscaling
Shadows and effects
Overlays
Driver and file verification

Beta boundary

The official beta warned about bugs and performance because it was in development. Do not treat an old beta workaround as a launch requirement.

For a repeatable crash, verify files, reproduce with a clean configuration and include hardware and location in the report.

Frame-time evidence sheet

Record hardware, driver, storage location, resolution, preset and an exact repeatable scene before changing settings. Test one variable, replay the scene and note frame pacing as well as average speed, because a higher average can still hide disruptive traversal spikes.

Restore any change that does not affect the problem. That keeps the configuration understandable and avoids stacking folklore fixes that cannot be reversed confidently.

Crash escalation package

For a repeatable crash, verify files, disable nonessential overlays, reproduce on a clean configuration and save the location plus action that triggers it. Include CPU, GPU, RAM, driver and whether the game is installed on the required SSD when reporting.

Beta warnings do not prove a launch defect. Confirm the issue on the current build and remove beta-only workarounds unless the same failure is independently reproduced.

Performance comparison rule

Compare captures from the same route, camera direction and combat state, then keep only changes with a repeatable frame-time or stability effect. Hardware results from another system are context, not a promised outcome. Revalidate recommendations after driver, patch or shader-cache changes alter the test environment.

PC Requirements & Performance FAQ

What GPU is required?

The official PC requirements list an SSD, so install on the required storage class before diagnosing traversal behavior. Also record CPU, GPU, RAM, driver, resolution, and preset. Without that baseline, another player's improvement cannot be compared meaningfully with your system.

How much RAM?

Change one setting at a time and replay the same route, camera direction, and combat state. Compare frame pacing as well as average speed because a higher average can hide disruptive spikes. Restore a setting when it does not affect the measured problem.

Is an SSD required?

For a repeatable crash, verify game files, disable nonessential overlays, and reproduce from a clean configuration. Save the exact location and action that triggers failure with hardware and driver details. This package is more useful to support than a generic report saying the game crashed.

What should I lower first?

A beta limitation is not automatically a launch defect because code, drivers, and shader behavior can change. Confirm the same symptom on the current release before applying an old workaround. Remove beta-only changes that no longer produce a measurable improvement.

Do beta issues prove launch problems?

Performance recommendations cannot promise identical results across different hardware. Use another system's data as context, then reproduce the scene locally under controlled settings. Revalidate after a game patch, driver update, or shader-cache rebuild changes the environment being measured.