- This topic has 8 replies, 2 voices, and was last updated Oct 5, 2025 8:31am by
.
-
Posts
-
Setup:
Headset: Meta Quest 3
PC: i5-11400f, rtx4070ti S, 16gb ram, Win11 24H2
Streaming: Virtual Desktop VDXR
Game Example: Outlast
VorpX v25.1.2Issue:
When connected to my PC via VD and launching a game with VorpX injecting on startup, performance is smooth and stable (e.g., ~80fps in Outlast).However, if I first start VorpX Desktop Viewer and then launch the game with VorpX injection, the game suffers from severe FPS drops every few seconds (down to 35–45fps), making it stuttery and unplayable.
Expected:
Performance should remain the same regardless of whether VorpX Desktop Viewer is launched before the game or not.Yes, I tested it again, and it’s definitely related with VorpX Virtual Monitor status before the game launch.
If I first start VorpX Desktop Viewer and enable VorpX Virtual Monitor, and then launch a game with VorpX injection, the game suffers from severe FPS drops every few seconds (from a stable 80fps down to 70fps, and sometimes even to 35–45fps), along with flickering in the right eye, making it stuttery and unplayable — despite my PC having plenty of performance headroom.
However, if I launch the game with VorpX Desktop Viewer but with VorpX Virtual Monitor disabled, and let VorpX inject on game startup in the same way, performance is smooth and stable (e.g., ~80fps in Outlast).
Visually, the injection and startup look the same, but if VorpX Virtual Monitor was active before starting the game, the game will stutter.
If VorpX Virtual Monitor was disabled before game start, the game will run smoothly.Is the game running at the same resolution in both cases?
I’m asking because a recent Windows 11 update seems to have broken vorpX’s fast capture method for (rare) 64-bit DX9 games (only Outlast and Crysis as far as supported games are concerned). At high resolutions that leads to a severe FPS drop. Might be the actual cause of your problem if you run the game with higher resolutions on the virtual monitor than on your actual monitor.
Unless MS changed something fundamental, I should be able to address that for the next maintenance update.
Yes, same resolution in both cases (1400×1440), my actual monitor resolution is 4K.
p.s.
I also described some other bugs in v25.1.2 topic, don’t know if you already saw them:EdgePeek convergence / perspective switch bug (post number 222198)
OpenXR API virtual controllers 3D-model position bug (post number 222199)
OpenXR API Tracking prediction wobbling lag bug (post number 222200)
And another one (which I discovered yesterday)
OpenXR API bug in Hunted: The Demon’s Forge:
The game can’t be injected with OpenXR API, and injects correctly only with SteamVR API.Also before i managed to make it work, many many times it refuses to inject even with SteamVR, and refuses to create alternative hook (error of extraction somewhat data error). After I changed game version, and after many many tries at last it gives me alternative hook (dll) which works now (I created a backup for that dll in case of any problems with other games in the future), but if I delete hook dll and try to create it, Vorpx refuses to create one again. I don’t know why.
It would be nice, if VorpX can suggest manual DirectX hook dll selection (for example as Reshade installer does).
It would be especially useful in case of games which user know should work correctly, but for some reason doesn’t hooked correctly. (Hunted has RjK G3D profile, it also confirmed on his profile database with his screenshots, so obviously it should work).
I know that it may be wrong (I saw other forum topic when you already discursed that earlier), but in situations when you tried many many times, but game don’t injecting, and hook doesn’t creates automatically it should be a alternate bypass route.p.p.s.
I also want to thank you for all your hard work, because despite some little bugs, VorpX works just flawless in such games as Outlast with FullVR/DirectVR mode, and in Hunted: The Demon’s Forge with FullVR G3D mode, providing real VR experience.Just in case you didn’t see my reply in the release thread:
Your issues sound as if you are using Virtual Desktop together with vorpX. Don’t. Really, just don’t!
Exit the VD Streamer on your PC. Set your headset type to ‘Meta Quest Link’ in the vorpX config app and enjoy vorpX like intended. Will feel like upgrading a 10 year old PC to something recent. Prefer wired Link for the best exprience. VD might work well in other cases, but with vorpX it produces performance issues, micro stutter and lag/latency even on fast WiFi that are beyond bad.
Yes, I use Virtual Desktop, and it works just great (apart from those few minor bugs with VorpX I mentioned earlier).
I don’t agree that Meta Quest Link / Air Link is the best connection method for Meta Quest headsets, nor that it provides the best performance.In fact, if you use the OpenXR mode in VorpX together with Virtual Desktop’s VDXR (selected inside the VD PC client), the performance is just as high as when using Meta Quest Link / Air Link.
I suspect that when you wrote “Will feel like upgrading a 10-year-old PC to something recent. Prefer wired Link for the best experience. VD might work well in other cases, but with VorpX it produces performance issues, micro stutter and lag/latency even on fast WiFi that are beyond bad.” you might have been referring to the performance boost that comes from switching to OpenXR itself.
To clarify this point, I retested it in Outlast (which supports VorpX FullVR/DirectVR) as well as in VorpX Desktop Viewer (streaming a regular game and measuring performance), so I wouldn’t be just speculating:
VorpX in SteamVR mode (presumably using OpenVR): 53 fps
VorpX with Meta Quest Link / Air Link (also using OpenXR): 80 fps
VorpX in OpenXR mode with Virtual Desktop’s VDXR: 80 fps
At the same time, Virtual Desktop offers far greater convenience (fewer steps to get started, fast switching between VR and desktop mode, more reliability and simplicity), as well as much more flexibility (on-the-fly changes to refresh rate, bitrate, codec — including AV1 10-bit support) compared to Meta Quest Link, which by 2025 feels very outdated. Quest Link UX/UI feels stuck back in 2015, not to mention its poor stability (with Air Link it’s still considered “normal” to have to reboot the headset if, for some reason, it refuses to connect to the PC yet again).
In my personal circle of friends, 99% of Quest 2/3 users rely on Virtual Desktop and avoid Meta Quest Link / Air Link whenever possible.
I absolutely don’t mean to sound negative or offend anyone in any way.
I just really hope that those few minor but annoying bugs I reported earlier regarding OpenXR support can be addressed in VorpX — that would be truly fantastic!To a degree your mileage may certainly vary, and as said above, VD may work well in other cases, not so when used with vorpX however unfortunately. Both simply don’t play well together. That’s all.
With vorpX VD introduces wild lag (OpenXR), heavy performance issues in some games, as in FPS almost half of what it should be (OpenXR and SteamVR), upside down controllers since vorpX updated to OpenXR 1.1 (OpenXR) and other minor issues.
I didn’t say VD doesn’t work well in general, I wouldn’t even know that. I can say with certainty though that in case of vorpX Quest Link objectively is the (far) better option. At least half the issues you reported here stem from using VD + vorpX, it takes you only a couple of mouse clicks to fix them right away.
- You must be logged in to reply to this topic.