- This topic has 17 replies, 4 voices, and was last updated Aug 19, 2025 10:33am by
.
-
Posts
-
The latest Nvidia driver 580.88 is giving me a black screen using the Quest 3, 5090, the sound is working. All previous drivers work fine. Has anyone else got the same issue ?
I had the same issue with the latest nvidia driver 580.88. I rolled the driver back to the previous version and now vorpx is working again.
@Ralf
Is there anything from your end that can be done to fix this or is it purely an Nvidia driver issue?
No problem with driver version 580.88 as far as I can tell (4090/Quest 3/Meta Quest Link/vorpX 21.3.5). Checked with various DX9/11/12 and OpenGL games.
If you haven’t done so already, selecting the ‘fresh’ or ‘new’, or whatever it’s called exactly, option in the nVidia driver installer might be worth a shot. That resets all driver settings to default.
Thanks for checking Ralf. I always do a clean install of the Nvidia drivers so maybe this is a 5 series issue.
It does look like it. I’ve installed the driver again, same problem. The 5090 really needs the latest driver to take advantage of the bug fixes/performance improvements.
@Ralf I’m guessing if you haven’t got a 5090 to test this, there isn’t much you can do ?
Frankly I can’t even really imagine how a driver update could cause such an issue. vorpX captures the game output before it is sent to the driver and sending the final image to the headset later works through the VR APIs (Meta/SteamVR/OpenXR) like in any other VR app. Not a single point in that pipeline touches the graphics driver directly. Very, very weird.
Either way, since for me 580.88 works fine, so that I can’t replicate your issue, all I can recommend is:
- Trying all three VR APIs in the config app, a Quest should work with all of them.
- Using a driver version that is working for you.
- In case this is related to a gaming laptop, try to disable the integrated GPU to ensure that games run on the same GPU that the headset is connected to, which usually is the dedicated GPU in a gaming laptop.
If you want, you can create a trouble shoot archive with log files and system infos in the config app and send it to support at vorpx com. Probably won’t show anything useful, but can’t hurt to look at it.
What games are you playing that have this issue?
Just in case someone stumbles over this thread.
The issue appears to occur with certain DX12 games. Should it persist longer than the next few nVidia driver versions, I will try to find a workaround. Until then let’s hope they clean up their messs.
The last non-broken driver appears to be 577.0
https://www.nvidia.com/en-us/geforce/drivers/results/251131/Please no “not working for me too” posts below this one, so that others can find this answer easily. The issue is the latest nVidia driver and the current solution is using the last non-broken driver (577.0) instead.
I just wanted to chime in that I’m also having issues with this driver and my 5090. It only happens in some games. For me it is with Farming Simulator 22 and 25. One of the issues is that the problem is intermittent. One thing I noticed is that when you change the tracking to “Safe” inside the game, it always replicates the issue, otherwise it’s intermittent for me. Sometimes the game is black, otherwise, it starts to flicker with no movement or action in the headset while the tracking in game often continues to work. Rolling back to 577.0 to see if that helps.
Just in case someone stumbles over this thread.
The issue appears to occur with certain DX12 games. Should it persist longer than the next few nVidia driver versions, I will try to find a workaround. Until then let’s hope they clean up their messs.
The last non-broken driver appears to be 577.0
https://www.nvidia.com/en-us/geforce/drivers/results/251131/Please no “not working for me too” posts below this one, so that others can find this answer easily. The issue is the latest nVidia driver and the current solution is using the last non-broken driver (577.0) instead.
- You must be logged in to reply to this topic.