Forum Replies Created
-
Posts
-
Try this for CyberPunk instead: click.
I could fix the issue by making SineMoraEX.exe large address aware, which raises the amount of RAM available to the game above the 2GB limit old 32-bit games have per default.
That’s always worth a shot if you encounter issues like this with older 32-bit games on modern systems, regardless whether they actually run out of memory or not. Especially if you know they worked before.
A small tool that can make 32-bit .exe files large address aware can be found here:
https://www.techpowerup.com/forums/threads/large-address-aware.112556/Caveat: Only try this if you actually run into issues with a 32-bit game. In some, although probably rare, cases making a game large address aware can introduce new problems.
I could only try Sine Mora EX, not the original Sine Mora, which can’t be purchased anymore.
That said:
Runs a bit longer for me here, but eventually crashes at 90% on the loading sceen in any of the actual VR modes (Oculus/SteamVR/OpenXR), works fine though with ‘Generic 3D/VR’. Probably the same issue though.
Funny enough it doesn’t even work anymore with the old vorpX version that the user used who created the cloud profile for the game. So might be related to how newer Windows versions handle DX9.
I’ll look into this, but since this is not an officially supported game, I can’t give you any guarantee or timeline for a fix.
Can’t replicate that here. The only weird thing I encountered is that the first loading screen only gets displayed in the left eye when the game is launched with G3D activated. That definitely wasn’t the case with older vorpX versions. Fixes itself once the main menu is reached though, so not really an issue.
Please provide more detail. What exactly happens? Is an error message displayed?
Ideally create a trouble shoot data archive in the config app and send that together with your more detailed issue description to support at vorpx dot com.
Please reinstall using your web installer. If you don’t have it anymore, you can get a new one here:
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.