Forum Replies Created
-
Posts
-
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.
@ gawky: Ideally please no “me too” posts below replies that contain solutions or fix announcements. Thanks! Makes life easier for everyone here and in every other forum on the planet. :)
Just a heads-up that I could pinpoint two potential issues with the game, using the demo. One can cause a crash directly at start on CPUs with >12 cores and another one can cause a crash when loading a map.
Both issues are addressed, so the game should work fine under all circumstances after the next maintenance update. No date set yet, but shouldn’t take too long.
There are three settings that affect actual gamepad input:
– The X-Box gamepad override (which maps gamepads to mouse/kb)
– Motion controller support if set to mouse/kb emulation.
– Head tracking sensitivity for default mouse emulation tracking.All three can make vorpX simulate mouse input, which as an unavoidable side effect causes gamepad issues in games that can’t gracefully handle simultaneous mouse and gamepad input, which are quite a few. The first option actually exists to deal with such games by translating gamepad to mouse input, which allows gamepad usage in affected games together with mouse emulation head tracking.
Disabling all three makes sure gamepad input stays unaltered and no simulated mouse input can interfere with games that can’t handle both at the same time.
Disabling all three also completely breaks everything motion controller related and head tracking related except DirectVR head tracking if available for a game.
Motion controllers set to gamepad emulation should be safe unless the X-Box gamepad override is enabled.
That’s all.
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.
Not a bug. An incompatible unsupported game. I changed the misleading topic title.
That aside: I’ll take look at it. No promises at all though regarding unsupported games.
BTW: who is “we”? :)
Can’t replicate. Do not diable vorpX’s automatic setting feature and reset the game’s graphics settings to default. Sometimes 3D modes working depend on one or the other game settings being set to a certain value.
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.
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.
I can’t replicate this here, using the Steam version.
1. Reset the profile to default in the config app.
2. Make sure you didn’t accidentally disable automatic settings in the config app.
3. Reset the game options to default.(Only!) if that does not help:
Create a trouble shoot data archive in the config app and send it to support at vorpx dot com.
Just a heads-up that I could pinpoint two potential issues with the game, using the demo. One can cause a crash directly at start on CPUs with >12 cores and another one can cause a crash when loading a map.
Both issues are addressed, so the game should work fine under all circumstances after the next maintenance update. No date set yet, but shouldn’t take too long.
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.
As far as the start room is concerned, check the hint badges around the center screen. They tell you which buttons/keys you can press.
If you happen to be on vorpX 25.1.0, make sure to update to 25.1.2 by running your web installer. 25.1.0 did not work with outdated OpenXR runtime implementations like VD’s OpenXR. Unfortunately auto updates from 25.1.0 to 25.1.2 are broken, so you have to run your web installer manually. If you didn’t keep the installer, check the support FAQ for a new link.
As far as the start room is concerned, check the hint badges around the center screen. They tell you which buttons/keys you can press.
Both the latest vorpX 25.1.2 and the standalone mod currently are based pretty much on the same code, so whether it’s vorpx 25.1.2 or the standalone mod doesn’t matter. Also no need to update CET, just make sure to use CP 2077 2.31 and the latest vorpX OR standalone mod.
DLSS works fine, just frame generation doesn’t. Graphics settings wise start with medium settings and go from there. Aim for a high resolution over raytracing. Raytracing+DLSS is possible on high end GPUs (4090/5080/5090), on mid tier hardware you’re almost certainly better off without raytracing.