Forum Replies Created
-
Posts
-
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.
2025/09/12
A new update is available that adds support for Cyberpunk 2077 2.31 and updates the core components to match the latest vorpX version.
Download link as always in the first post of this thread.
The whole point of the virtual monitor is less fiddling with custom resolutions. The current way to add your own via the – fairly slick if I may say so – dialog is as far as customization will go. Sorry. It’s actually already the result of listening to user wishes about more customization, although that rarely should be necessary at all.
Aspect ratios below 1:1 practically never makes sense since in FullVR you’d always want a few pixels left and right as a buffer for extra frames vorpX can generate. In games that aren’t too demanding actually even 4:3 is the best FullVR choice, as that will provide enough buffer for fast head rotation without black sliding in from the sides. And in terms of wider resolutions everything is there that makes sense for immersive screen/cinema.
If what you have in mind is adding precisely the display resolution of your headset, that’s not how things work in VR. There can’t be precise pixel mapping due to the reverse lens distortion applied to the image on screen anyway.
I can’t really think of much else than the bug I described above, 90% sound particularly weird as that would mean the service used almost all your cores, which it never does. At worst it should occupy one core when said bug occurs. Let’s see how things turn out after the next update. Keep me posted once the next version is out.
Resolution:
Disable foveated rendering in the Pimax app. Can’t test since I only have an older Pimax lying around here, but others reported that’s the source of the problem. Foveated rendering is not of much use with vorpX anyway since when hooked into a game most of the GPU heavy lifting is done by the game, not in vorpX’s own rendering thread where the foveated rendering gets applied.
Desktop viewer/virtual display:
Sounds suspiciously as if the vorpX service can’t perform its desktop viewer related tasks like it is supposed to on your system, which would prevent both the virtual display from kicking in and the desktop viewer from launching when trying that from the tray menu.
That may occasionally happen due to bug that can send the service into an infinite loop currently. Will be fixed in the next update. As a workaround restarting the service (or your PC) would help until then.
It can also happen if you are running your PC with dedicated admin/day-to-day user accounts, where the logged in day-to-day user user is never allowed to have admin rights. To use the virtual display as intended you’d have to change your Windows setup to default (i.e. the logged in user can obtain admin rights via Windows’ user account control if needed). If you don’t want to change that, you can still use the desktop viewer with your actual monitor like you currently do, of course.
If none of the above is your issue, try to reinstall vorpX if you haven’t tried that already. Just in case.