- This topic has 59 replies, 15 voices, and was last updated Sep 27, 2025 6:29am by
.
-
Posts
-
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/
I removed vorpx and reinstalled, same issue. If I double click the vorpx desktop viewer icon and right click the task bar icon, “disabled virtual monitor” is greyed out and “start vorpx desktop viewer” does nothing.”Enable virtual monitor” in the config app is enabled. As I said, using vorpx as I always have done works with FS25 with Z3d, using a clone of the FS22 official profile. Will there be an official FS25 profile and is it worth sending you the vorpx logs to look at. I was just wondering if the virtual monitor would give better performance given I have a 5090 and use a high resolution. Thanks Ralf.
The next release will focus more on games and less on internal improvements/clean-up. Besides that no promises at this point, a FS25 profile is not unlikely though.
Logs would be great. You can create a trouble shoot archive in the config app.
However, due to an oversight on my end that won’t contain the log(s) I’m mostly interested in in your case. Please also collect the following two logs manually: C:\Windows\Temp\vorpService.log, which is the most important one, and (if it exists) vorpService.log from your user temp folder. To easily find the latter you can paste %TEMP% into the Windows Explorer location bar.
Please send everything to: support at vorpx dot com. Thanks in advance!
I’ve found if I removed my headset while playing FS25, the image goes crazy, horizontal moving lines. If I bring up the vorpx settings and change the “Headset Sync to either “Favor Latency” or “Judder Protect” the image returns to normal. Select Default again under headset sync, which is what I have it set to at the start and the crazy image returns. Everything is fine providing I don’t remove the headset while playing.
After upgrading to 24.1.0 and 25.1.1, the Desktop Viewer is not usable (double-clicking on vorpX Desktop Viewer has no response). Could you provide version 21.35 instead?
Having bug with last update – keyboard input is locked and don’t work. Copying all the files from 21.3.5.0 version of vorpxControl.exe resolves the issue. Tested only with SpaceEngine and Tomb Raider 3 via voodoo wrapper, cause don’t have other games installed. In the menu of SpaceEngine can use mouse, but while in the game it’s also do not work at all. Game have native vr support, but for testing used regular gave.
Oculus Rift CV1, Win 10 with auto updates removed, NVidia drivers without geforce experience, no overlays or any kinds of trash which hooks in to the games, no exotic input devices with their services, no motherboard vendor bloatware. Latest Quest software. I didn’t run vr for a long time, so have no idea if there are any versions in between 21.3.5.0 and last one.
I can confirm that my HP Reverb G2 works again with OpenXR after the latest patch. One weird thing I’ve encountered only when launching Desktop Viewer, though, is that it disables all my monitors in Windows display settings, and doesn’t allow me to re-enable them while VorpX Desktop Viewer is running, unless I set each monitor to mirror the display from the headset display, instead of choosing to extend the desktop on them.
@ ENBSeries
Can’t replicate that here unfortunately, trying TR3. So the only suggestion is to make sure that the game runs in the foreground by clicking in its windows once after it started. BTW: IIRC only DX7 games work in 3D with dgVoodoo+vorpX, not DX1-6.
@ ryoshenron
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.
I had to turn off the headset auto activation setting in the Virtual Monitor config to prevent the Desktop Viewer from auto recentering every 5 seconds. I don’t know if this is intended behavior for detection, but it affected both headsets I tested. I don’t recall this happening in 24.1.
I like being able to navigate my desktop and launch games from the viewer, but it very rarely resumes after I close a game. I assume it is meant to resume, right?
I do feel a slight performance improvement in games I tested though. Nice work.
Yes, it’s supposed to resume after exiting a game. Also the auto recentering every 5 seconds is not supposed to happen, only once when the desktop viewer switches to the virtual monitor. For the lack of a better suggestion, try a uninstall/reboot/reinstall. Maybe the background service didn’t update correctly for some reason. Both the not-resuming part and the recenter issue point at something being wrong service wise.
@Ralf
Regarding issues with non functional input. If I keep old version of vorpControl64.dat, then issues do not happen. Maybe there is another combination of files, didn’t test more.
The same problem happens in A Hat in Time. Reinstalling Vorpx via web setup multiple times – no difference. Even Vorpx own ctrl+alt+shift popup message ignores keyboard in A Hat in Time game. The only thing suspicious to me is when first time after long break started Vorpx and it initiated an update, at some stage of installation terminated it manually because was busy with other pc tasks. Still, that don’t explain why problem remains after executing web setup later, after reboot as well. As mentioned earlier, in the SpaceEngine some actions do work in certain moments, like game first popup warning with Esc button to hide it fails, then main menu works for cursor and mouse buttons both, then in-game cursor works but mouse buttons and keyboard are dead. I know some of the last patch(es) of Win11 (I’m on Win10) have changes to GetAsyncKeyState, breaking some apps, maybe workaround was done on Vorpx and it do not works in my case.Interesting, never heard of that. vorpX does use GetAsyncKeyState(), but not in the hooked game. It updates the keyboard state in the vorpControl app and then relays that to the game via interprocess communication. It does hook the function though inside the game for various reasons. I’ll check TR3 in Windows 10. If I find something unusual, I’ll let you know.
BTW: vorpX quite heavily relies on interprocess communication like the one described above between all its parts, which makes mixing components from different versions dangerous and likely to cause havoc. Don’t do that.
Just in case you may also try a uninstall/reboot/reinstall like I suggested to Dellrifter above. Just to be 100% sure everything is really at 25.1.1.
- You must be logged in to reply to this topic.