Forum Replies Created
-
Posts
-
False positive, can happen after an update due to antivirus programs guessing wrong.
Three options:
- Exclude the vorpX program folder from your AV scanner, usually C:\Program Files (x86)\Animation Labs\vorpX.
- Report the issue to AVG as a false positive so that they can fix the problem they have with their poorly working guesswork.
- Get rid of your unnecessary third party AV. Windows Defender is more than good enough since more than a decade. It kicks in when you uninstall your unnecessary third party AV program. I usually make sure that new updates get whitelisted by Defender before release if necessary.
The prior ‘OpenXR (Windows Mixed Reality)’ selection simply reads ‘OpenXR’ now, just a cosmetic change. No underlying technical changes except updating the OpenXR library to the latest version.
Probably the WMR OpenXR runtime is outdated and doesn’t support the latest OpenXR API version. There will be a small update shortly that falls back to OpenXR 1.0 if a runtime doesn’t support 1.1. Until then please use SteamVR instead.
At some point OpenXR 1.1 may become mandatory though, so please direct any potential future complaints in this regard at Microsoft for abandoning WMR.
If you happen to use SteamVR as your OpenXR runtime, configure vorpX to use SteamVR directly instead.
Valve’s OpenXR implementation is not only outdated (i.e. doesn’t support the latest OpenXR version). It also, spec violation one, has no 32-bit support for older games. And, just as bad, messes up two OpenXR functions, spec violation two, that are used to snychronize frame timing in more complex multithreaded environments, causing severe FPS drops with vorpX compared to working OpenXR implementations or using SteamVR directly.
They ignore reports from several devs in both regards since several years, so they probably won’t fix any of that.
TLDR: Valve’s OpenXR objectively sucks. Do not use.
NO!, as in NO! with capital letters :). Only do that if you want to play games that need to be run as admin. Avoid running vorpX as admin like the plague otherwise.
On a healthy install the vorpX control app communicates with a background service for handling the virtual display and the desktop viewer. My guess is that your install is somehow borked and either the service isn’t running or for some reason hasn’t been updated. A fresh install should fix that.
The virtual monitor is disabled in the device manager on Windows start on purpose. It should get enabled when you launch vorpX. Check whether maybe it’s disabled in the config app on the ‘Virtual Monitor’ page.
However, considering that you also have issues with the desktop viewer, something might have gone wrong during the update. Try to reinstall vorpX using your web installer. If you didn’t keep it, you can get one here: https://www.vorpx.com/request-new-download/
KCD1 works perfectly fine with vorpX 25.1.0.
If for some reason it doesn’t hook on your machine, which would be fairly weird, wait until the trouble shoot dialog appears and try the trouble shoot options that are offered there.
If that doesn’t help, try a factory reset (config app > trouble shooting page).
@ garken
Your symptoms are typical for a CET version mismatch or otherwise not fully loaded mod. Double check that you really have the right CET for your game version and that it’s installed in the right place.
If you are 100% sure both conditions are met, the mod doesn’t work with 2.1 anymore. Unlikely, but not impossible. In that case you have to switch CP2077 2.3, which will work out of the box with the current mod version.
@ djbert
There is a ‘Resolution Quality’ option in the mod’s options menu (DEL key). With your 5090 you should be able to crank it up fairly high. Go has high as you consider OK performance wise with the image quality settings you prefer. No raytracing yields the best possible performance, no DLSS the best possible image sharpness. If you want raytracing you’ll probably need DLSS too though to keep the framerate high enough.
When you switch the ‘Play Style’ (first option in the vorpX menu) to ‘Immersive Screen’ everything should basically work as it did in 21.3.5. IIRC that was what you wanted in the first place. Except G3D doesn’t have shadow glitches anymore now.
There is nothing that actively prevents hooking into any version of the game. That aside: the profile now comes with a dedicated mod that (among other things) does G3D for the game without the prior shadow glitches. If so far you didn’t consider upgrading the game to the latest version worthwhile, that alone should be reason enough.
Too many vital things broken in 21.3.5 by now. Most prominently:
– DX12 games only show a black screen in the headset with nVidia drivers 580.88+.
– DX9 games run at half speed on Windows 11, probably even less at high resolutions.
– Tons of game profiles not working correctly anymore due to game patches.Witcher 3 ironically is one of the games where G3D has been broken entirely in 21.3.5 by a game patch. If you want the 21.3.5 experience (no 3D, immersive screen mode), you can disable the connection mod on the DirectVR page of the vorpX menu and then switch to immersive screen mode.
Having two branches in parallel for the last year or so was an exception. In the future there will be only one branch again like before.
25.1.0 will be available again soon. Had to pull it after only an hour so last week due to Windows Defender now apparently being just as annoying as some of the other super annoying AV programs. It’s cleared by Microsoft in the meantime, just waiting a few days until it’s reasonably safe to assume that everyone has the latest Defender definitions.
Just a heads-up that I have removed the link to first list. That list was never complete in the first place and hasn’t been updated since at least seven or eight years, making it grossly misleading.
RJK’s list also isn’t complete anymore, but at least it gives a somewhat better impression in regard to games released up until 2020 or so,
Sorry! I really appreciate your post otherwise.
2025/08/23
A new update is available that fixes crashes when changing the display mode and some graphics settings in the game options, which were introduced by the earlier fix for the nVidia 580.88+ issue. Also addresses an annoying non-critical crash when exiting the game that could occur since a while.
Download link as always in the first post of this thread.