Forum Replies Created
-
Posts
-
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.
@ 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.
Glad you got it sorted. Temporarily switching to a VPN or using a phone as a temporary access point via USB/WiFi tethering is a good way around this issue whenever caused by some internet hiccup.
Glad you found a way to address this. Normally the UI should be scalable in the game, and the cursor should fit accordingly. Unfortunately UI scaling can break when a game gets updated. I look into that.
Changing the UI scale to 1.0 in the vorpX menu can serve as a workaround until I upload an updated profile.
If you want to dive into stuff like that yourself, you can also enable shader authoring on the general page of the config app, and try to find the new UI shader(s) yourself. If you are a little bit tech savvy, that should be fairly easy. Otherwise check the cloud profiles in the config app in a few days for an updated official profile.
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!
Your post offended the spam filter due to the many links, sorry. I removed most of it to make sure it stays.
In regard to your actual problem I can’t say much unfortunately. If you maybe have some mail forwarding to your own server configured in Gmail that’s probably the issue. Just a wild guess though, other mails from Gmail arrive without problems.
Anyway: As an alternative use the contact form (Support > Contact in the menu above), although it says to not send key requests that way. Will take a bit longer since the license server can’t respond to messages sent via the form automatically, but I’ll make sure your key is sent manually.
With Windows 10 and Windows 11 < 24H2 you should still be able to use the old WMR SteamVR plugin from Microsoft in the meantime. IIRC the community WMR SteamVR driver was supposed to be released yesterday. But I might be mistaken in that regard.
Works fine here. Reply from a few days ago in your other thread:
I could fix the issue by making SineMoraEX.exe large address aware, which raises the amount of RAM available to the game above the 2GB limit old 32-bit games have per default.
That’s always worth a shot if you encounter issues like this with older 32-bit games on modern systems, regardless whether they actually run out of memory or not. Especially if you know they worked before.
A small tool that can make 32-bit .exe files large address aware can be found here:
https://www.techpowerup.com/forums/threads/large-address-aware.112556/Caveat: Only try this if you actually run into issues with a 32-bit game. In some, although probably rare, cases making a game large address aware can introduce new problems.
Some of the more annoying/invasive third party antivirus programs are fairly difficult to disable. The three options you have are listed in my reply above.
False positive, can happen after an update due to antivirus programs guessing wrong.
Three options:
- Exclude the vorpX program folder from your AV scanner, usually C:\Program Files (x86)\Animation Labs\vorpX.
- Report the issue to AVG as a false positive so that they can fix the problem they have with their poorly working guesswork.
- Get rid of your unnecessary third party AV. Windows Defender is more than good enough since more than a decade. It kicks in when you uninstall your unnecessary third party AV program. I usually make sure that new updates get whitelisted by Defender before release if necessary.
The prior ‘OpenXR (Windows Mixed Reality)’ selection simply reads ‘OpenXR’ now, just a cosmetic change. No underlying technical changes except updating the OpenXR library to the latest version.
Probably the WMR OpenXR runtime is outdated and doesn’t support the latest OpenXR API version. There will be a small update shortly that falls back to OpenXR 1.0 if a runtime doesn’t support 1.1. Until then please use SteamVR instead.
At some point OpenXR 1.1 may become mandatory though, so please direct any potential future complaints in this regard at Microsoft for abandoning WMR.
If you happen to use SteamVR as your OpenXR runtime, configure vorpX to use SteamVR directly instead.
Valve’s OpenXR implementation is not only outdated (i.e. doesn’t support the latest OpenXR version). It also, spec violation one, has no 32-bit support for older games. And, just as bad, messes up two OpenXR functions, spec violation two, that are used to snychronize frame timing in more complex multithreaded environments, causing severe FPS drops with vorpX compared to working OpenXR implementations or using SteamVR directly.
They ignore reports from several devs in both regards since several years, so they probably won’t fix any of that.
TLDR: Valve’s OpenXR objectively sucks. Do not use.
NO!, as in NO! with capital letters :). Only do that if you want to play games that need to be run as admin. Avoid running vorpX as admin like the plague otherwise.
On a healthy install the vorpX control app communicates with a background service for handling the virtual display and the desktop viewer. My guess is that your install is somehow borked and either the service isn’t running or for some reason hasn’t been updated. A fresh install should fix that.
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/