Fix SteamVR error 450 in flight simulators with ordered checks for the compositor, GPU driver, OpenXR runtime, overlays and headset connections.
SteamVR error 450 is a compositor graphics-initialisation failure, not normally a fault in the flight simulator itself. Close all VR software, reboot, confirm the headset uses the discrete GPU, verify SteamVR’s files, then repair or roll back the graphics driver. Disable overlays and SteamVR add-ons before testing the simulator again.
What does SteamVR error 450 mean?
In OpenVR’s error definitions, code 450 identifies a failure while the SteamVR compositor creates a Direct3D blend state. The compositor cannot finish preparing the image sent to the headset, so the error may appear before the simulator enters VR or while its VR session is starting.
The code does not identify one damaged component. Common causes are a broken or incompatible graphics driver, SteamVR choosing an integrated GPU, software injecting an overlay into Direct3D, corrupted SteamVR files, or a stale headset session after sleep or reconnection.
Fix SteamVR error 450 in this order
- Start with a clean VR session. Close the simulator, SteamVR and any headset software. If
vrmonitor.exe,vrserver.exeorvrcompositor.exeremains in Task Manager, end it or restart Windows. Wake and connect the headset, start its required platform software, launch SteamVR by itself, and only then open the simulator. Our headset-to-simulator launch sequence explains the normal order. - Confirm SteamVR is using the discrete GPU. Connect the headset’s DisplayPort or HDMI lead to the graphics card, not a motherboard video output. On a hybrid-graphics laptop, assign SteamVR and the flight simulator to the high-performance GPU in Windows graphics settings. A compositor running on the integrated adapter can fail even when the simulator uses the correct GPU.
- Repair the graphics driver. Install the appropriate stable driver for the installed GPU and reboot, choosing a clean installation when the driver package offers it. If error 450 began immediately after a driver update, rolling back to the previous working driver is more useful than repeatedly reinstalling SteamVR. Return GPU overclocks and undervolts to standard settings during testing.
- Verify SteamVR and leave its beta branch. In the Steam Library, find SteamVR under Tools, open Properties, select Installed Files and run Verify integrity. Under Betas, select the normal non-beta branch unless a particular headset manufacturer explicitly requires otherwise.
- Disable overlays and optional SteamVR add-ons. In SteamVR’s Manage Add-ons screen, temporarily disable non-essential dashboard tools, performance overlays, capture hooks and third-party input extensions. Close other software that injects an on-screen display into 3D applications. Do not disable the driver required to make the headset itself work; re-enable optional components one at a time after SteamVR starts successfully.
- Set one correct OpenXR runtime. Only one OpenXR runtime should be active. A headset that depends on SteamVR must use SteamVR’s OpenXR runtime, while a headset with a native PC OpenXR runtime may be able to run Microsoft Flight Simulator 2020 or 2024 without SteamVR. Changing this setting will not repair error 450 if SteamVR also fails when opened alone, but it matters when the error appears only after the simulator starts. See our runtime-selection and VR graphics checks for the full setup.
- Reconnect the headset directly. Power-cycle the headset or link box, reseat its display and USB connections, and test direct computer ports rather than an unpowered hub or display adapter. This is especially relevant when the problem follows sleep, a cable reconnection or intermittent headset detection.
- Reinstall SteamVR last. Uninstall and reinstall the SteamVR tool through Steam, reboot, and test it before adding overlays or opening the simulator. Reinstalling the entire flight simulator at this stage usually wastes time because code 450 originates in the VR compositor.
What if error 450 appears only when the simulator starts?
If SteamVR runs normally by itself, the trigger is more likely the simulator’s render path, OpenXR selection or software loaded alongside the simulator. Run Steam, SteamVR and the simulator at the same normal privilege level; remove any setting that forces only one of them to run as administrator.
| Observed behaviour | Most likely area | Best next step |
|---|---|---|
| Error before any SteamVR scene appears | GPU selection, graphics driver or compositor files | Repair the driver and verify SteamVR |
| SteamVR works until the simulator enters VR | OpenXR runtime, API layer, overlay or VR plug-in | Disable injectors and confirm the active runtime |
| Error began after joining a SteamVR beta or updating the GPU driver | Software regression | Leave the beta or roll back the driver |
| Error follows sleep or reconnecting the headset | Stale USB or display session | Power-cycle the headset and use direct ports |
For Microsoft Flight Simulator, test with optional OpenXR layers and VR overlays disabled before removing aircraft or scenery; ordinary content add-ons are much less likely to cause a compositor initialisation error. Our Microsoft Flight Simulator VR fault-isolation steps cover runtime conflicts and session initialisation in more detail.
Lowering render scale or scenery detail rarely fixes code 450 because the failure occurs before normal heavy rendering begins. If the error clears but Microsoft Flight Simulator produces a headset image with no visible cockpit, continue with the separate VR black-screen diagnosis.
Do I need to reinstall the flight simulator?
No—do not reinstall the simulator unless SteamVR works reliably by itself and every other VR application starts normally. In that case, verify the affected simulator’s files, reset its VR-specific configuration where supported, and test without VR plug-ins before considering a full reinstall.
If SteamVR still reports error 450 after a clean graphics driver, verified files, no optional add-ons and confirmed discrete-GPU use, create a SteamVR System Report. Check which GPU and third-party drivers it lists; a persistent standalone failure at that point points to the headset display connection, the selected graphics adapter or the GPU driver rather than flight-simulator content.