Forum Replies Created
-
Posts
-
Just a heads-up that an update that addresses the issue caused by nVidia drivers 580.88 and higher is on its way. Just needs a bit more testing.
2025/08/19
A new update is available that fixes a severe issue caused by nVidia drivers 580.88+.
If you experienced a black screen or crashes after updating your nVidia driver recently, please redownload the mod and reinstall it. That should fix the issue. As a side effect of the according changes the updated version may/should also run a bit smoother under high GPU load.
Download link as always in the first post of this thread.
The latest mod download is for 2.3, but the latest nVidia driver breaks vorpX in some games, incl. Cyberpunk 2077. For the time being reverting to an nVidia driver 577.0 from a few weeks back should help:
https://www.nvidia.com/en-us/geforce/drivers/results/251131/
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. THANKS! THANKS! THANKS!
The issue is the latest nVidia driver and the current solution is using the last non-broken driver (577.0) instead.
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.
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.
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.
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.
Seeing the desktop in the headset after ALT+TAB while vorpX is hooked into a game is not possible. vorpX always sends the game/app to the headset that it is hooked into, no matter whether it runs in the foreground or not.
I’m not even sure whether handling that differently would be a good idea, as it would mean that every time a game loses input focus vorpX would change to the desktop viewer. Although beneficial for ALT+TAB, there probably are just as many occasions where such a behavior is unwanted.
What you can do while using vorpX’s virtual monitor however is taking off the headset to get the desktop on your actual monitor after a few seconds. Might crash one or the other game, but in most case that should work I think.
Another key has been sent to your Gmail address.
Please clarify the iinet.com.au problem with iinet.com.au. Essentially the bounce back messages said “rejected because on our ABL list”, which means their spam detection didn’t work right.
Quest:
- Download and install the Meta Quest (Oculus) PC-App from the link below.
- Make sure Oculus is selected in the vorpX config app as your headset type.
- If you want to use the wired Link, connect the Quest via USB
- Launch the Meta Quest Link PC App.
- Launch Quest Link (wired) or AirLink (Wi-Fi) in your Quest.
Afterwards your Quest is connected to the Quest Link app and vorpX can send images to it via the Meta Quest PC runtime.
Caveat: AirLink only works well with fast Wifi 5/6 and your PC connected to the routher via an Ethernet cable. If you are unsure about that, use wired Link via USB.
https://www.oculus.com/download_app/?id=1582076955407037
Cinema mode:
Whether games are shown in cinema or vr mode depends on the game and whether there is a profile for it. If there isn’t an official profile for a game, maybe there is a user profile in the cloud. You can browse user profiles in the config app on the Cloud Profiles page.
You can also create your own profiles for games that don’t have one. More details on that in the vorpX help (‘User Profiles’ and ‘1-2-3 Game Setup’ pages).
Sounds as if the game switches back to a lower res, which would be super weird. Never heard of anything like that before. Try to add a custom res in the nVidia control panel and then switch your desktop res to that res before launching the game. Some games limit their resolution to the current desktop res. A step-by-step guide for adding custom resolutins can be found in the vorpX help.
Running a game windowed may also help (again provided it doesn’t limit its window size to the desktop res).
If you want to use the full potential of your new Pimax headset you must run games at resolutions at or above 4K, i.e. 2160p or more. Roughly 3000p is what your Pimax Super wants as an input res with default SteamVR settings. Might be too much performance wise in modern games though.
If things still look pixelated when running a game at such high resolutions, there has to be something weird going on after vorpX sends the image to SteamVR, e.g. in the Pimax app or on the headset itself.
I didn’t receive a rejection notice after the last mail two days ago, so I’d assume it went through this time. Please double check your spam folder.
That aside: yes, an alternative mail address would probably help.
You can temporarily change the file extension of [CP2077]\bin\x64\plugins\vpx2077.asi from .asi to e.g. .asi_off if you want to switch to flat without uninstalling the mod.
Just in case: the easiest way to locate the install folder is:
Steam: right click the game’s name, select “Properties”, then “Installed Files > Browse”
GOG Galaxy: right click the game, hover over “Manage Installation”, select “Show Folder”