Forum Replies Created
-
Posts
-
Could be related to GPU switching from your integrated GPU to the nVidia GPU when the game starts. Try do disable the integrated GPU if possible to ensure that your Vidia GPU is always used.
Also try to disable any tools running in the background that may also hook into games. E.g. your ‘Intel Extreme Tuning Utility’.
More detailed infortmation on both matters can be found in the pinned trouble shooting guide on top of this sub forum.
Depends on the game. Whenever vorpX can change the resolution for a game you can select a quality preset on the DirectVR page of the ingame menu and vorpX then figures out the actual resolution depending on various parameters, e.g. the chosen play style and what resolutions a game supports or not.
For Conarium that isn’t the case though, so for this game you have to set the resolution in the game’s option menu. Typically a 4:3 resolution (e.g. 1920×1440) is a good choice for for playing in FullVR mode. Caveat: some games have the unfortunate habit of not showing anything higher than the current desktop resolution. In such a case you would have to change your desktop res before launching the game.
With a 1440p resolution you roughly get 1:1 pixel mapping between game and headset, everything above results in supersampling.
Please check whether the game’s renderer is set to DX12. Normally vorpX does that automatically, but maybe that doesn’t work for you for some reason, e.g. if you happen to have disabled automatic settings.
You can run games at higher resolutions for better image quality. Please check the ‘Custom Resolutions’ section in the vorpX help for more detailed information on the matter, including a step-by-step guide how to add resolutions to your PC that is does not support otherwise.
If you haven’t done so already, also check the ‘Essential Hints Guide’, which explains some general concepts.
Resetting the game settings to default anf then not touching AA/scaling options afterwards should help.
A restart after settings changes is only required when vorpX shows an according notification, i.e. when you change settings that are handled by vorpX’s DirectVR.
Please add -dx9 to the game‘s launch options in Steam. Rocket League recently got a DX11 renderer, but the vorpX profile (currently) is for DX9. Unsure yet whether DX11 will be possible, I will check it shortly.
Maybe your PPS nails it better than I would like it to. A few years back Robinson — The Journey was another supposed VR must have and I was completely blown away by its similarly great graphics and atmosphere, exactly until the game literally wanted me to play some children’s game. Can’t remember what that was anymore, but I never touched the game again afterwards.
I’ll give Alyx another try over the weekend. I’d really appreciate a grumpy-old-man-mode though that cuts what I consider distracting fluff. As much as I love to explore artfully crafted worlds, even more so combined with some well done action and a halfway decent story, I just don’t really see me grabbing behind my back and then cumbersomely reload a gun 500 times in each and every game from now on. Doesn’t add one bit of immersion for me at all.
Maybe in the long term. If you already have Virtual Desktop, you can use that to stream vorpX to the Quest though. You just have to set vorpX to SteamVR in the config app and then use VDs SteamVR streaming.
My personal recommendation would be to use an Oculus Link capable USB3 cable instead since that has slightly better latency (less lag), but if you prefer to stay wireless, streaming via VD is a valid option too.
Bioshock: there are two flavors of positional tracking. The default positional tracking that is theoretically possible with every G3D game and DirectVR positional tracking. If available DirectVR positional tracking is a bit better since it changes the position of the actual game camera, but if you encounter any issues with it, just disable it on the DirectVR page of the vorpX menu. The default G3D pos tracking will still be available in Bioshock.
What you could also try is re-running the scanner if that happens. In Unreal Engine 3 games the memory addresses for DirectVR can become invalid over time. Usually not within the same level, but maybe sometimes they still do, can’t rule that out entirely.
Black Mesa res: the resolution isn’t set by DirectVR in this game, hence resetting the profile doesn’t change it. You have to set it manually.
Try to reset the profile to default in the config app. You shouldn’t really have to touch any of these settings.
Lower the 3D-Strength setting, like most settings in vorpX 3D-Strength is not a more-is-better setting. The higher the 3D-Strength (separation), the smaller the world seems to be, that’s how stereoscopy works. In official profiles base parameters are typically dialed in to provide realistic stereo 3d/world scale with 3D-Strength at the default 1.0.
Falling back to default positional tracking isn’t really a big deal, so that’s the best thing to do in case of issues with DirectVR positional tracking, you don’t lose much. Especially considering that your issue occurs in two totally different games in the same way it could also mean you have actual tracking dropouts though, which might be a headset/setup issue.
If you use a Rift S, WMR headset or other headset with inside out tracking make sure that there always is enough light. In badly lit environments inside out tracking can occasionally fail with pretty much the symptoms you describe.
If you have a lighthouse based system (Vive/Index), similar issues may occur if the lighthouse setup isn’t ideal. In that case try placing your lighthouse sensors in a different way to make sure your headset can be tracked at any time.
Addendum: Judging from your video your issue looks more like an occasional frame every few seconds being rendered with the original FOV instead of the FOV that gets applied by DirectVR. For New Vegas applying the DirectVR FOV relies on overwriting the FOV memory address as fast and often as possible, which might be hampered e.g. by a camera mod or an AV scanner that monitors memory writes, so disabling your AV scanner’s realtime scanning is worth a shot. If you use anything else than Windows Defender, get rid of it.
You could also set the FOV manually from the game’s console. ‘fov 112’ should be the right command with all vorpX profile settings at default. If you tweaked vorpX settings, the right value might be different. In that case reset the profile to default first to ensure 112 is correct. Just in case.