Vaultbreakers lists Windows 10 64-bit, a 4-core 3.2 GHz processor, 12 GB RAM, GTX 960 or Radeon R9 380 graphics, broadband internet, and 10 GB storage as minimum-level store requirements. The base game lists DirectX 12. The Demo store still says DirectX 11, but the newer October patch notes say DX11 is no longer supported because it caused crashes and instability.
Requirements comparison
Interpret the minimum correctly
A minimum specification means the developer lists that class of hardware as a supported entry point; it does not promise a specific resolution, preset, or frame rate. Vaultbreakers is still in public testing, and July notes reported performance degradation around minimum-spec hardware at that time.
Compare the complete system, not only the GPU. Twelve gigabytes of RAM, available storage, a 64-bit operating system, and a working broadband connection are part of the listed boundary. Background applications and a nearly full drive can reduce the working margin.
The CPU entries are generic core-and-clock descriptions rather than named models. Do not rank two processors from clock speed alone. Architecture, sustained boost, thermal limits, and current client workload can change the result.
Resolve the DX11 and DX12 conflict
The Demo store’s minimum block says DirectX 11. The base store says DirectX 12, and the October 8 notes explicitly say DX11 was removed because it caused severe crashes and instability. The dated developer note is the newer operational warning.
Do not edit undocumented launch options to force DX11. Update the GPU driver, ensure the hardware supports DX12 at the required Windows level, and launch through Steam normally. If the client still offers a renderer choice, record the exact build and option before drawing a conclusion.
This conflict can only be fully closed by updated store metadata or direct current-client verification. A guide should preserve both statements with dates instead of deleting one.
Check storage and installation
Steam lists 10 GB available space. Keep extra room for the download, unpacking, updates, cache data, logs, and Windows activity. An install can fail even when the final game size appears to fit exactly.
An SSD is recommended in the store metadata. It can reduce storage-related waits, but no official loading-time target is published. If loading is slow, record the drive type, free space, whether the same scene repeats, and whether a party or network transition is involved.
Install the separate Demo AppID 4488770 when trying to play now. The base AppID 306910 is unreleased and does not provide the full game download.
Controller and handheld boundaries
Steam labels base-game controller support partial and Demo support full for Xbox controllers. That difference belongs to the product listing, not a promise that every device has correct prompts and remapping.
Steam Deck compatibility is Unknown. No native Linux or macOS requirements are listed. Do not convert a community success report into official support. A useful handheld result must name device, SteamOS, Proton version, client, settings, controls, performance, and date.
What to record when performance is poor
Capture Windows version, CPU, GPU, RAM, driver, install drive, free space, display resolution, graphics settings, frame behavior, temperature or throttling signs, client, region, mode, party size, and exact scene. State whether the problem begins at launch, Haven, matchmaking, Wolfswood, combat, or extraction.
Change one setting at a time and retest the same reachable situation. Do not publish a universal preset from one machine. Public tests can change workload and optimization between patches.