- This topic has 3 replies, 2 voices, and was last updated Sep 28, 2025 9:44am 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.
- You must be logged in to reply to this topic.