- This topic has 5 replies, 3 voices, and was last updated Oct 4, 2025 10:30pm by .
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
- You must be logged in to reply to this topic.
Homepage › Forums › Technical Support › Vorpx Virtual Monitor is not working
Hello dear Ralf and VorpX Team.
I have a core issue with vorpx:
virtual monitor is not enabled by default when i put on headset and i cannot enable it manually. Just nothing happens. That means desktop viewer is not working also.
I was able to see virtual monitor only once after installation of fresh Vorpx. (i did try 24 and 25 latest versions). After fresh installation the screen was flickering, but i was able to see extra monitor in steam VR, so i successfully turn off my real screen. After reboot, however, no virtual monitor and i cannot enable it. (when i click on button enable virtual monitor – nothing happens).
I have next specs: RTX4080, Pimax Crystal Light, Samsung Odyssey G8 (120Hz mode, 10bit, HDR on), latest Nvidia drivers, Windows 11 Pro, no AV installed.
Can you please help to troubleshoot issue? Can it be Nvidia drivers or settings? (i also sent troubleshooting info from vorpx to your support email)
i check all the threads on the forum, and seems no similar issue described here. I want to add that i have foveated rendering disabled in Pimax.
Hi!
I am running the original Pimax Crystal headset and I’ve noticed that only the PimaxPlay version 1.40.1 or earlier works like it should with Vorpx. I tried the latest update, nothing shows up on the HMD, no Virtual Desktop, no game, just the Pimax star background image, so I rolled back to 1.40.1 (you can find the installer for 1.40.1 if you google it).
i can play without issues on latest PimaxPlay. only the virtual monitor problem.
if that will be useful i fixed that issue by enabling vorpx desktop monitor in device manager.
On some PCs the vorpX service can’t handle the virtual monitor due to fairly convoluted Windows access rights issues. I implemented a fallback method for affected configurations in the meantime. Will come with the next maintenance update. Until then manually enabling like you did is the right workaround.