Forum Replies Created
-
Posts
-
Under normal circumstances the service should not consume any noteworthy CPU time.
However, there currently is a fairly stupid bug that can occasionally cause this after lock/unlock, waking up from standby or similar events. Unless your issue is caused by something else, it should be fixed in the next update.
If you still experience this issue in vorpX 25.1.2, which will be out shortly, let me know.
The profile currently has no gesture predefined. You can add some yourself though. Check the video in the release post for a short introduction.
Can’t replicate. Checked with Odyssey under various conditions. Neither in generic 3d, nor with a headset, with and without virtual monitor. One time I had to ALT+TAB after opening the game’s key rebind options for some reason though. Might have lost input focus.
That aside I could rebind the C key to everything I tried. vorpX wise everything at default.
The C key is used in the ALT+C hotkey for toggling cursor visibility if neccessary per default. Nothing has changed in that respect for ages though.
Would be great if you could check whether the same happens with a different key you assign in the config app for cursor visibility toggling or whether it’s still the C key that causes issues afterwards. Both would be equally weird, but at least I’d have some halfway useful information that way.
You should be able to automate large parts with a batch file and some command line tool that can change the resolution. An alternative would be AutoHotkey, which can change display resolution itself, I think. Never used it, but many consider it quite useful for Windows automation tasks.
I’ll add a selection for a preferred virtual display res in one of the next updates. Probably not directly the next, but that sounds like a useful idea.
Nothing has changed in respect to immersive screen controls. The profile now comes with a dedicated mod-portion though. You may have to disable that on the DirectVR page of the menu, switch to Z3D, immersive screen mode on the main page and restart the game to make everything behave like before.
Builds prior to 25.1.0 don’t work anymore with Cyberpunk at all since nVidia decided to break vorpX’s old DX12 renderpath in drivers 580.88+.
As said above already, there might be nothing to fix on my end. Meta, WMR, even Valve within the boundaries of its flaws work. So to me it looks quite a bit more likely that the Pimax OpenXR runtime does something weird. I’ll still check, of course.
I see. I’ll check whether my old Pimax uses that. OpenXR should be universal though, taht’s the point of it. So without having tested anything, I would carefully tend to blame the Pimax OpenXR runtime for your issue. I’ll check anyway.
Do they have their own OpenXR driver independent from SteamVR or do they use Valve’s god awful (no 32-bit support, broken multithreaded syncing) OpenXR runtime?
In the latter case using SetamVR directly is better anyway. The latest vorpX should actually do that automatically if it detects that Valve’s OpenXR is set as the active OpenXR runtime.
Really weird, just disable the virtual monitor in the config app then. You’ll lose its benefits (no more custom resolutions fiddling + matched refresh rates), but everything should work like before, i.e. your actual monitor is captured by the desktop viewer.
The days of WoW with vorpX may be over, at least as far as the main version is concerned. Just checked it two days ago and apparently they added some new DLL blocking/anticheat system. According to various posts on the WoW forum stuff like Reshade doesn’t work either anymore. A true shame, I just updated vorpX to work with the last iteration of their renderer not too long ago. Maybe things will change again after one of the next WoW updates, but I wouldn’t hold my breath.
WoW Classic still seems to work at this point (or at least it did two days ago) and got a dedicated profile with automated settings optimization in 25.1.1.
It’s not so much about performance, but about having resolutions available that your actual monitor does not without fiddling. With the virtual monitor you can skip the whole tedious task of adding custom resolutions to your display driver manually.
In regard to the desktop viewer also about not having to do refresh rate conversions from e.g. 60 on your actual monitor to e.g. 90 on your headset, which causes subtle microstutter. With the virtual monitor the desktop and the headset always run smooth at exactly the same refresh rate.
1.
Sounds as if everything works as it should. With the desktop viewer vorpX now switches to its new virtual display, which supports all vorpX specific resolutions per default, let’s you easily add even more in the config app, and for a uniquley (at least I think so) smooth desktop experience runs at the refresh rate of your headset. Other displays are blanked out on purpose since 1. mirroring the virtual display on them is unlikely to work due to resolution/refresh rate mismatch, 2. that way games only see the virtual display, which makes using it in games hassle free.
If you don’t need/want that, e.g. because you want to show others what you do in VR, you can easily revert back to the prior behavior by disabling the virtual display in the config app. However, the virtual display is so useful in so many ways that I’d heavily recommend to only disable it if you absolutely need your other displays while in VR.
2.
That sounds weird. The desktop viewer should launch in immersive screen mode. Try a factory reset in the config app (trouble dhooting page).
Just realized that the issue might have been caused by a small change in the installer I made yesterday, will probably work now if you try again.
If not:
If you didn’t keep your web installer, you can get one from the link below.
If the issue is caused by your antivirus, that might not work either though. If you use something else than Defender, really just get rid of it. There is zero reason to use some extra annoying third party AV since many, many years.