- This topic has 4 replies, 2 voices, and was last updated Dec 13, 2025 2:54pm by
.
-
Posts
-
OS: Windows 10 latest with ESU
AMD driver: 25.10.3 – 25.12.1
GPU: XFX RX 6900XT (Both OC and non OC tested)
CPU: 9800X3D
RAM: 32GB DDR5-6000
Module: SteamVR – OpenXR
Headset: PS/VR2 with PC adapter – Displayport connection.
VorpX: 25.1.2I’ve noticed that the app is constantly crashing when using VorpX on any game. Tested Fallout 4, Cyberpunk, Stalker Anomaly, Left 4 Dead 2, Ghost Recon Wildlands, Factorio, 15+ others.
The Virtual desktop starts fine and works fine(usually, sometimes VorPX will attempt to hook vorpDesktop and timeout), until the moment I try to actually play a game. Game will usually start, but inevitably crash after less than 5 minutes. SteamVR reports ‘ IPC Namespace Unavailable ‘ and AMD driver reports that the driver has crashed. Notably, the driver crashes to the Virtual Desktop and in rare cases, crashes out of the VR experience outright.
This happens only with VorpX. SteamVR home works fine, mods for Cyberpunk like RealVR work great, so it’s a very specific VorpX problem with the headset.
Effectively this appears to make the software completely unusable under Windows 10 at this moment.
Hope this helps you ascertain the issue Ralf. I can provide additional info and tests if you need them, to hopefully help you get some more customers for the software.
Please first try with only SteamVR, exit Virtual Desktop. Also make sure to select SteamVR in the vorpX config app, not OpenXR. Valve’s OpenXR misses 32-bit support for older games and on top of that is broken in regard to a function that is important in multithreaded rendering pipelines like vorpX’s.
If that does not help, check whether something is running on your PC that also hooks into games. Issues like this almost certainly are caused by another app getting in the way.
The trouble shooting guide in the vorpX help (altenatively pinned to the top of this sub forum) has more details.
I have tried with both SteamVR and OpenXR, tried the latter when SteamVR failed.
I have checked and removed other overlays, including those of AMD drivers themselves. GameBar is also functionally cut out of my Windows install with a Debloater.
The options were:
– Rivatuner from MSI Afterburner
– Wallpaper Engine
– AMD Overlay
– Discord Overlay
– Lossless Scaling
– Game Bar
– Browser
– HWINFO (reads sensors for system, I figure safe bet to shut down)
– Windows PowerToys (has overlay componets that are turned off).
– Steam OverlayAll of these have been disabled for the test as you asked. I inspected Task Manager for any processes that may be related, found none.
VorpX is allowed to turn off overlays and runs in admin mode. Alternative hook method has been tried to no effect, so it’s turned off again.
I checked again and the app just crashes on the virtual desktop too, after the same amount of time. I had been using it to launch games so didn’t test the obvious scenario of leaving it running.
The desktop mode is thus also a bust.
The in-app troubleshooter was read back to front before I came to the forums: Googling also didn’t show any similar results to mine.
FAQ above was read.
Tested with just SteamVR and Left 4 Dead 2, crash behaviour is _identical_: Crashes about 2-3 minutes in. Seems to last the exact same amount of time before crashing each time, suggesting a timeout somewhere.
If it’s helpful I can roll back drivers to last year or something similar.
Hope this helps.
Tested again with a timer: timeouts occur exactly 90 seconds after utilizing the program, whether in Desktop mode or in Gaming mode.
There is also a non optional Overlay that the PS/VR2 imposes, namely the psvr2 overlay to be able to sue the motion controllers. This is impossible to turn off, so I suspect any other users with a PS/VR2 will either have the same issue, or have it running without issues, suggesting it can’t be a problem.
I don’t know how many people you have with a VR2, but it’s a bit of info.
- You must be logged in to reply to this topic.