- This topic has 59 replies, 15 voices, and was last updated Sep 27, 2025 6:29am by
.
-
Posts
-
@Ralf
Uninstalled, rebooted then installed again – no luck. Also noticed with SpaceEngine (running in windowed mode) after game is loaded height of the game window is reduced maybe by 10-25 pixels (can’t tell for sure about width). Also vanilla game allow mouse cursor go to any area, while with Vorpx it’s limited to client area where game front buffer is displayed.
Here is the list of the process in the task manager, as you can see I keep pc clean as much as possible, so there are no other apps which could mess with input or hooking graphics:“while with Vorpx it’s limited to client area”
That is to be expected and on purpose. It’s meant to keep the mouse inside the game window when run windowed. Some, especially older, games don’t handle that correctly by themselves and don’t work right without catching the mouse. I’ll put SpaceEngine on my nice-to-have official profiles list, looks interesting enough. There I would be able to override this behavior.
Can’t say anything more to your input issue before running some Windows 10 tests myself. So far no other reports like this several days after release though, which hints more towards an individial config issue than something general.
I somehow doubt logs will contain anything really useful in this case, but please create a trouble shoot data archive in the config app and send it to support at vorpx com. With some luck I can spot something.
@Ralf
Thanks for reply, sent troubleshoot data to e-mail.
I know such kind of issues difficult to track, but from my experience helps to give to the user different old versions till find one which have issue. Then compare code, make minor changes and give again for testing. As I already found vorpControl64.dat is culprit most likely, could be easier and safer swapping it than sharing entire old builds. I can live with old version of Vorpx with internet disabled (don’t remember if any game need to be online), but don’t mind to test as described above. In that case, better to connect in some chat application to make the testing quicker, discord f.e.SpaceEngine do have native vr, I just have it installed, so used it as one of testing applications which do not have native Vorpx support and quick to start. Not sure if there is any benefit to add vr via Vorpx to it, unless there are some exotic helmets which can’t run it by default.
I see. I settle this issue then. Please try some other games. Preferably some with official profiles.
@Ralf
I’m very sorry for wasting time, false alarm. Didn’t wear helmet before, because usually skip while games are in the menus, so didn’t know about new behavior of the Vorpx, which requires to press some buttons in the new vr windows and until then input is partially locked.All good, glad you got it sorted. Always a good idea to use a VR headset when checking a VR app, I guess. :)
For some reason, when using the virtual desktop now (and my monitor is shutdown), after exiting the virtual desktop, my actual desktop goes to some really low resolution, sometimes so low that I have to reboot the whole system coz I can’t see what I am trying to do (change the desktop resolution back to normal). A small weirdness, but a strange thing nonetheless.
That is definitely not supposed to happen, should return to the prior state normally. If that happens often, disable the virtual monitor in the config app.
Would be great if you could answer the following question so that I have a starting point for replicating the problem: how do you invoke the virtual monitor? By switching your physical monitor off manually or by launching the desktop viewer and then putting on your headset?
Ok, first I tried the method that was on by default, when I put on my HMD, the monitor shuts down and so on. I tried to change the method to fully manual, where I have to shut down the monitor my self, but that resulted in black screen on the HMD when the monitor was shut down and I had to reboot the HMD to get any picture back. Using the method where Vorpx shuts the monitor automatically works fine otherwise, been gaming quite well with that, but finishing a session is a problem because the desktop is on some wanky low resolution after that. I have Pimax Crystal headset, I don’t have the latest Pimax Play release because that broke something with Vorpx, I think I couldn’t use the Vorpx Virtual Desktop at all with the latest release (they broke other things too when they added the Sharpening and GPU scaling functions to the Pimax Play so I reverted to the latest working release and been using that ever since). Windows 11 with all the latest updates aswell.
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.
Tried something else last night. While on Virtual Desktop, I switched the Virtual Monitor off first, desktop came back to my monitor on a correct resolution, HMD went black, but that just needed a reset on the HMD. Yeah, I can live with this coz everything else works just fine but a weird thing nonetheless.
I’ve had to set vorpX menu key override to NO in a few games recently to get functionality of my C key. Reporting in case this was left in from dev mode or something. Didn’t happen before 25.1.1.
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.
I rebound vorpX cursor to U and restarted vorpX. The cursor toggled with U as expected and the key override setting had no effect either way.
The C key however still won’t work with the menu override on — at least as a short press. It worked as a long press in AC Odyssey for loot scanning, but as a toggle it won’t work. I can’t bind C to anything in the 3 games I tested (no input detected) until I turn the menu override off. Override off and C works as expected.
I don’t have C bound to anything in the vorpX config other than default Alt + C for cursor. Only custom bindings I have for config are:
recenter = Shift + Q
edgepeek = Pad+
enable stereo = Pad-
switch G3D/Z3D = Pad*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.
- You must be logged in to reply to this topic.