Forum Replies Created
-
Posts
-
Sorry for the spam detection troubles you encountered. The alternative to having spam detection on in the forum software would be a 3:1 spam:content ratio unfortunately, extra bad since the beautiful invention of drivel bots like ChatGPT etc.
Your actual issue:
Maybe some weird issue related to Pimax’s software that puts itself in between vorpX and the headset. Reversed eyes are conceptually impossible with vorpX’s G3D method (at least unless the profile author intentionally inverted them, which obviously isn’t the case here).
Possibly related to the time vorpX hooks into the game (before or after Pimax initializes its stuff). Enabling alternative hooking in the config app may be worth a shot. That aside maybe check whether there is some stuff in the Pimax software you can turn off. Haven’t checked a Pimax headset in a long time, but a few years back they had some custom reprojection that could change the IPD and make things appear cross-eyed occasionally.
vorpX does not change the power plan. Some VR runtimes do howewer. At least the Meta (Oculus) runtime does. Not sure about Pimax.
Yeah, in cases where head movement is bound to the mouse, you may have to calibrate the sensitivity. Unfortunately sometimes it depends on the ingame mouse settings, or even the resolution, so providing perfect defaults for everyone is not always possible.
There is a setting in the vorpX menu (main page as well input page) called ‘head tracking sensitivity’ that you can adjust.
Hint: A good way to calibrate the sensitivity is finding a spot in the game where you can easily tell when you turn 90°. Any flat wall will do for example. Stand before the wall, facing it straight while at the same time facing your monitor in reality just as straight. Then turn 90° in the game and check how far you turned in reality. Adjust the sensitivity accordingly. After 2-3 quick iterations you typically get a perfect 1:1 match.
Hint 2: Useful hints like the above and more can be found in the vorpX help under ‘Essential Game Hints’ and ‘The 1-2-3 Game Setup’.
Sharpness has nothing to do with G3D or Z3D. Depending on the game however some glitchy effects may be disabled with G3D, which is not the case for Bioshock, but IIRC is the case for Metro Exodus. That’s probably why Z3D looks better in that case, at least in some places.
On a sidenote, just in case you haven’t discovered that yet: On the image page of the vorpX menu is a set of options named ‘Clarity’, which provide very well working post process sharpening.
Just a heads-up that G3D for the new WoW DX11 renderer will work with the next vorpX version. Required quite a few changes to the vorpX codebase, so no way to address this with just a profile update.
Until the next vorpX gets released, WoW G3D support is limited to WoW Classic, which as of today still has the ‘DX11 Legacy’ renderpath.
The game camera in first person shooters is controlled by your mouse normally, i.e. looking around and aiming are the same in a game typically. Since vorpX (except for a few exceptions) doesn’t alter the inner workings of a game’s controls, looking around with the headset also means aiming.
Then for whatever reason either the VC download failed or your Windows registry is broken so that the installer couldn’t determine whether it needs to download the VC runtime or not.
Check the link below. BOTH the x86 and x64 versions are required.
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
Please make sure to be online while installing vorpX. If necessary the installer downloads potentially missing dependencies like the VC runtime.
vorpX per default tries to set sound output to the headset when launching a game. Maybe that doesn’t work right in your case for some reason. This feature isn’t really needed anymore anyway admittedly, basically a leftover from the very early days of Oculus. I should probably remove it, all headset runtimes handle that by themselves these days.
You can disable it on the ‘General’ page of the config app and let SteamVR handle audio on its own. If it still doesn’t work afterwards, check the according SteamVR options, which let you select a device you want to use if auto-switching fails.
Not sure about the mouse issue, that definitely didn’t happen when the profile was done back then. There is a cursor toggle keyboard shortcut that *might* help, can’t recall currently what the default is, but you can check under ‘ingame key bindings’ in the config app. Also switching between fullscreen/windowed is worth a shot in such a case.
Aiming is usually bound to mouse movement with vorpX. There are some exceptions from this rule, most notably Cyberpunk that comes with free VR controller aiming in the latest vorpX 24.1, but those really are exceptions.
As far as visual glitches are concerned, try to tinker with (turn off) graphics settings. The profile is supposed to adjust settings automatically, but who knows. Stuff like motion blur or some antialiasing methods are typical candidates for potential glitches.
That shouldn’t be necessary since PSVR2 works with SteamVR. You should be able to use vorpX with the headset type set to SteamVR on the ‘General’ page in the config app.
Since that might be somewhat confusing: you can also play non-Steam games with SteamVR. Steam needs to be installed for SteamVR to work, but you can play any game with SteamVR.
If the D3D11 Legacy option had been removed, you’re out of luck for the time being. At least as far as Geometry 3D is concerned. The other D3D11 renderer doesn’t play nice with vorpX. I’ll take a look at it for the next vorpX update, but no promises.
Sounds suspiciously like one of those antivirus programs that chose to be more of an annoyance than helpful. If you happen to use anything else than Windows Defender, make sure to exclude the vorpX program folder. Even better: get rid of the invasive third party AV altogether. For all normal intents and purposes Defender is more than enough since a decade. Windows Defender will kick in automatically when removing third party AV.
Good to know. I’ll take a look at it. I’m currently in the middle of the yearly nothing-but-fixing-and-optimizing-for-a-month-festivities anyway. ;)