Forum Replies Created
-
Posts
-
Your GPU is a bit on the low end of the spectrum regarding what makes sense for vorpX, also WMR headsets are bit prone to judder, with WMR games have to run at least with half the headset refresh rate, otherwise there will be heavy judder. If nothing else helps, switch to Z3D.
However: The CPU usage sounds sverely off. If you see CPU usage that high while vorpX is just waiting, something is wrong. Sounds a bit like some annoying antivirus program that dislikes how vorpX checks for newly launched programs. If you happen to use anything else than Windows Defender, please try to exclude the vorpX program folder or – better – get rid of that AV program. There is no real need for invasive third party AV on Windows 10. Windows Defender is more than good enough for several years now.
A little follow-up on the OpenXR plan mentioned above: I have a first implementation working since yesterday. Only tested about half a dozen games so far, but as much I can tell from that WMR via OpenXR seems to be a significant improvement over WMR via SteamVR. One layer less between vorpX and the headset driver is clearly a good thing.
Not only do uneven game/headset framerate ratios work much better, also game framerates below half the headset refreshrate are working in FullVR mode as they are supposed to. Pretty much exactly what I was hoping for, both major WMR annoyances largely gone, at least with the games that have been checked so far. Really promising.
Still lots of work to do, the headset part isn’t done yet and I haven’t even started with porting over the controller stuff. So don’t expect anything final in the immediate future.
Just in case you overlooked it, please check the reply two posts above yours. There isn’t really anything else to recommend than that.
Sounds as if game and headset FOV don’t match. Please reset the game’s profile to default in the config app and make sure not to disable automatic settings. With everything at default and auto settings enabled vorpX ensures that game and headset FOV match.
VorpX backs up the current state of the Windows mouse acceleration setting on start and resets it to the backup value on exit.
Please reset the the profile to default in the config app.
You essentially created both issues by changing the aspect/zoom setting. The game’s field of view can’t be set high enough to fill the whole view while still matching the FOV of your headset. This FOV mismatch causes the wrong scale as well as the distortion. The profile default accounts for the missing game FOV with the borders. Not a 100% perfect solution, but as good as it gets in this particular case.
BTW: If you want to learn more about FOV and the various options that exist to deal with it (varying from game to game), check the Essential Hints Guide in the vorpX help. It explains the basic concept.
The game is rather popular and also has been tested here for hours on two different machines (nVidia as well AMD), so it’s safe to say that there is no general issue, has to be something individual.
Can’t really suggest anything else than general trouble shooting stuff:
1. Make sure you have the latest display drivers installed.
2. Do not overclock anything.
3. Try to lower the game’s graphics detail settings.
4. Disable any potentially interfering background application (e.g. CPU/GPU tools of any kind, messengers like Discord, generally everything that can display an overlay in games).
5. In case you have any mods installed, try without.Please first check whether maybe something is different on your PC than it was a few fays ago. E.g. if you have some tool running that also hooks into games which wasn’t there before. If you happen to have the Windows system restore functionality enabled (unfortunately its off per default in Windows 10 for some reason), try to go back to a restore point from before the issue started to occur.
Apart from that: running games windowed instead of fullscreen can often help with such issues.
Please DO NOT change any settings in the vorpX menu, you probably messed up the settings. The profile is set up for correct FullVR playing out of the box. Reset the profile to default in the vorpX config and then just follow the instructions shown in the top left corner of the game window. Don’t change anything else.
There isan’t really anything else I can suggest, sorry. With default settings the game works perfectly fine. All you have to do is setting a 4:3 resolution and running the DirectVR scanner.
Currently not, defining the shaders requires temporarily enabling G3D. It is planned to change that at some point, but I have no timeline it ATM.
Virtual Desktop can only capture SteamVR games not the native Oculus runtime. You have to switch the headset type in the vorpX config app to SteamVR AND enable SteamVR capturing in VD.
If you continue to have problems with VD, please switch to Oculus Link instead, which is the better choice anyway since no additional network latency is involved.
Are you using Virtual Dektop by any chance to stream the image to the headset? if so, please use Oculus Link instead like suggested above.
With everything working correctly (which it does at default settings) the image fills the entire view.
Also just in case: vorpX does not work with the (years old) mod version of Black Mesa, only the the version that you can buy on Steam is supported.
Good find! Clearly makes sense to leave that off (which seems to be the default BTW, just checked with a fresh install).
FluidSync should still be at ‘Auto’ or ‘On’ with WMR, the general issue with WMR making it harder for vorpX to maintain the full headset framerate in some situations does still occur.
The installer is one of the most commonly used installers out there (Inno setup). Having the documents folder on a network drive is rather unusual though, sounds as if the environment variable that normally points to it is not set correctly (or not in a way that allows Inno setup to properly resolve the path).
However, provided you can skip the error there isn‘t really anything you have to be concerned about. The only file that the installer puts in the documents folder is an optional background image for cinema mode. Not required for anything at all. You can add any number of background images later in the config app.