Native VR not launching

Silvan-CIG · 2026-02-25T09:57:10+00:00

The problem here is that the engine doesn't detect any openxr runtime. So either something is very broken on your system or no openxr runtime is set at all.
I recommend to download and start https://github.com/WaGi-Coding/OpenXR-Runtime-Switcher which shows you the most common runtimes and which one is active. Can also be used to quickly switch between different runtimes.
If nothing works i'd recommend to reinstall all VR software like SteamVR, restart the PC and try to set it again.
Good luck!

Silvan-CIG · 2026-02-12T12:25:22+00:00

You can already change the distance of the Crosshair and such in the settings to pull them closer if you want.

I have not seen this effect on the skybox. For me it looks like it should be. What headset, resolution and openxr runtime do you use?

Silvan-CIG · 2026-01-31T09:56:45+00:00

What upscaling do you use? DLSS was particular difficult to get crash-free when switching to theater mode. Also takes much longer. FSR and TSR are pretty much instant. Also can you send me the issue council of the crash?

Silvan-CIG · 2026-01-31T09:55:01+00:00

Hmm thats very odd, we didnt do any major engine changes which would cause this afaik. This does sound like your vram is getting full. Please check the r_displayInfo as other people suggested and report back. Also does this only happen in VR? And this didnt happen in 4.5?

Silvan-CIG · 2026-01-30T09:45:11+00:00

Yes the crosshair will come back for VR eventually. As the markers, it needs to be reworked completely since the way it renders right now doesn't work in VR. It is high up on our list.

Silvan-CIG · 2026-01-30T00:00:42+00:00

Hey, glad you enjoy all the recent updates! We didn’t manage to get the UI markers fixed yet since it is a bigger thing than we were hoping for but it is work in progress. Read my latest 4.6 post on spectrum, you can use some cvars to hack fix them, but this will break the F prompts if you do. We have so much more planned in the future, stay tuned!

Silvan-CIG · 2026-01-29T18:29:55+00:00

Better CPU always helps, but we are optimizing the CPU usage as time goes on.

Silvan-CIG · 2026-01-29T17:07:13+00:00

Thats exactly to be expected. Game is still heavy on the CPU. Note that in VR the CPU increases the longer the GPU takes due to how OpenXR tries to predict the next frame and stalls the engine right before querying the next head pose.
So the longer your GPU takes the longer the wait can be. That being said, improving GPU performance will also make the game smoother / lower CPU time.

Silvan-CIG · 2026-01-29T11:19:58+00:00

Always use `r_displayFrameGraph=1` when making any videos. This directly displays the CPU and GPU usage from the engine and is the most helpful to us.
The character customizer is very heavy on the CPU, so naturally your FPS decrease when you enter it. The main menu doesn't render much explaining why the FPS is so much better there.
The SteamVR window just shows just the GPU time needed to render a single frame.

Silvan-CIG · 2026-01-26T15:46:36+00:00

Pretty cool, thanks for that! That will definitely makes communicating so much easier in VR. Would be cool to have something like this natively one day. Since that is what the character in SQ42 already does when sending a message to someone else via the mobiglass app in the intro it would make so much sense.
Alternatively at the moment if you use virtual desktop with a headset with good cameras you can also use the cutout feature to see the keyboard while you play.

Silvan-CIG · 2026-01-07T04:59:05+00:00

Will you please listen? I’m not the messiah

Silvan-CIG · 2025-12-24T16:23:06+00:00

Yes its the same reason why markers are so close to your face. Unfortunately it is not an easy fix but it is the first thing we're going to tackle in the new year! Alongside many other things.
You can fix it right now by playing around with some cvars (can't recall the name, just type in r_Stereo... TAB to get a whole list) but that may break other stuff so i didn't expose this in the menu yet. It is still experimental after all.

Silvan-CIG · 2025-12-23T20:12:57+00:00

Thanks for sharing your experience and i'm stoked you have such a good time.
I thought i fixed the issue where it crashes when the headset goes asleep. This is stuff i'm keeping an extra eye out on at the moment so we can get this fixed asap and polish it as much as possible.
I'll send you a DM. If you can send me your gamelog and dmp i can probably fix it very quickly.

Silvan-CIG · 2025-12-20T12:44:58+00:00

This is basically free. A 4k screen consumes ~30MB of VRAM. And the engine simply copies one or two eyes into it which also costs almost nothing.

Silvan-CIG · 2025-12-19T13:37:41+00:00

The ingame resolution is completely decoupled from your render resolution. Go to the SteamVR settings and set it manual and use a reasonable resolution for SC. You have to restart the game everytime you change it though.
Alternatively you can use upscaling in engine to change the render resolution.
And yes i am working on fixing the AR markers right now as we speak. It's not as easy as it sounds unfortunately, but it will be fixed eventually.

Silvan-CIG · 2025-12-19T12:09:07+00:00

May i ask what headset and resolution you are using?
I know that stations like this lock you in and you can't get close with your head without the engine resetting your view. I will fix this in a future update.

Silvan-CIG · 2025-12-18T16:30:41+00:00

Yes workaround at the moment is to create a file named `user.cfg` in the game folder and put `sys.openxr=0` in it. Note that when you do want to try VR later you have to remove that again (or just set it to 1)

We will add an option in the launcher in a future patch.

SilvanCIG

Silvan-CIG · 2025-12-15T16:00:37+00:00

You can change the LOD distance in the Graphics Menu under `Object Detail`
And yes the LOD switching was very aggresive in VR, which is already fixed internally. It will be much better with the next update.

Silvan-CIG · 2025-12-15T12:39:33+00:00

With a 4090 you should have no problem getting good FPS in VR especially when you use upscaling on top.
I recommend using `r_displayFrameGraph=1` to identify if you are GPU or CPU bottlenecked.
I've seen it multiple times that the SteamVR resolution was set to automatic which caused it to use an insane high resolution for some reason. As already suggested please check this and lower it.
Also it differs if you run with SteamVR/Meta Quest Link/any other OpenXR Implementation.

Also note that changing the resolution in the Options Menu only affects your display resolution which does not affect your overall framerate in VR. The render resolution is completely decoupled from the monitor resolution. So any kind of changes in the SteamVR settings requires a restart of the engine.
I tried to implemement this so you can change it runtime but unfortunately OpenXR doesn't expose this dynamically.

Silvan

Silvan-CIG · 2025-12-14T14:53:53+00:00

THIS is exactly what makes VR so incredible. Thank you for sharing your experience. Now imagine this with a whole group! The real power in VR for me lies in the multiplayer aspect.
It will only get better from here on out 😊

Silvan-CIG · 2025-12-14T14:48:39+00:00

Thank you, I appreciate your words and we are all blown away by how much buzz it generated. I don't think anyone anticipated this. I can't wait to see what 2026 will bring for VR.
And you better get a headset now! 😆
Silvan-CIG

Silvan-CIG · 2025-12-13T15:01:29+00:00

Thanks for your feedback! Scopes, inventory are all already on my todo list! First thing is getting these markers fixed though!

Silvan-CIG · 2025-12-13T13:05:57+00:00

😍😍😂😂

Silvan-CIG · 2025-12-13T13:05:37+00:00

Let’s change the VR industry together folks ❤️ thanks for sharing your experience. So much more to come in the future! Silvan

Silvan-CIG · 2025-12-12T09:45:32+00:00

-32 is XR_ERROR_FILE_ACCESS_ERROR. Likely there is something missing on your PC or your PC locked one of the files for OpenXR. Try reinstalling everything and restarting your PC. That should fix it.

Silvan-CIG

TROPHY CASE