Forum Replies Created
-
Posts
-
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.
As always no promises in regard to unsupported games, but I’ll take a look at it for the next maintenance update.
As always no promises in regard to unsupported games, but I’ll take a look at it for the next maintenance update.
Not tried, but if it can process side-by-side 3D (SBS3D), which is quite likely, then yes.
BTW: I changed your display name since you probably didn’t intend your mail address to be displayed. You can change it to something else by clicking ‘Edit Profile’ in the user menu above if you want.
Nothing really, except that something like KAT VR is probably the perfect platform for playing with gesture controls, so don’t skip the gesture tutorial on launch. And graphics settings wise depending on your PC aim for a high resolution over raytracing.
Something else must be going on, vorpX deosn’t load any shaders except for its own. Maybe you have some other app running that also hooks into DirectX. Either way: happy testing!
If you have the latest vorpX 25.1.2 installed, vorpX is a bit better since it comes with additional stuff like the virtual monitor, which the mod does not have. Also when you use vorpX you get notified automatically when updates are available. In terms of ingame features both are quite similar though.
No, that looks fine. Should work.
Please start vorpX, try to launch the desktop viewer trom the tray menu a couple of times and then create a trouble shoot archive in the config app. Send it to support at vorpx dot com. I get back to you *if* I can spot something unusual.
Than it has to be some rights specific issue. Not quite sure what you meant by ‘admin account’. If that means that you have an admin account and a sescond account for day-to-use, it will not work.
You need to be logged in with a default Windows user account, which doesn’t have admin rights when logging in, but can get admin rights if necessary. Otherwise the service can’t do all it needs to do to handle the virtual monitor.
Also if you happen to run vorpX as admin, don’t. That’s only neccessary to hook games that require admin rights.
Besides that I’m out of ideas. You can however still use the desktop viewer like before vorpX 25.1.0 with your actual monitor.
That sounds fairly weird, but I’m glad you got it sorted!
Maybe you have displaying file extensions disabled in Windows Explorer? In that case your dxgi.dll0 would actually be dxgi.dll0.dll. Should still not load though even in that case.
Almost certainly related to interprocess communication between the vorpControl app and the service not working. If you aren’t onthe latest buld 25.1.2 yet, try that first.
If it’s still not working afterwards, check whether for some reason the service did not update by checking its version in the file properties windows. Has to be 25.1.2.0 for both vorpService.exe and vorpControl.exe.
Please check whether you have some other DirectX injector/mod installed in the game folder. Or maybe some game recording app running. Remove anything that potentially may also hook into DirectX and by doing so may cause double injections and other weird issues. This does not happen with vorpX alone.
25/09/12 | vorpX 25.1.2 has been released
Another maintenance update with about a dozen noteworthy changes and fixes.
- Head tracking mouse emulation did not work anymore in desktop viewer.
- Messages shown in some games on start could become unresponsive.
- Mod component install with the virtual display failed due to an unclickable prompt.
- Some games did not exit cleanly since vorpX 25.1.0.
- Workaround for 32-bit games that use too much RAM on CPUs with many cores.
- Potential workaround for old games that assign small stack sizes (untested).
- In games with .ini and mem-scan FOV, ini-controls weren’t shown before scanning.
- Avoid more annoying virtual monitor related Quest Link self-restarts.
- Communication between the service and 32-bit vorpControl was broken.
- The service could use an entire CPU core after lock/unlock, standby/resume etc.
- Custom sync selection in the vorpX menu selected different options than shown.
- Trouble shoot data now includes all relevant log files.
- Better service handling in the installer.
- Elder Scrolls Online: HUD shaders updated (again).
- Cyberpunk 2077: mod components updated for CP2077 2.31
- As always numerous smaller fixes and optimizations.