Forum Replies Created
-
Posts
-
Could you please check whether any of that goes away when you scale the HUD and its witdh to 1.0. The scalable HUD is pretty much the only thing I can think of that potentially may introduce odd visual glitches.
Would be great if you could let me know your findings if that helps with your issue.
The video doesn’t play here for some reason, but you have to use the controllers in keyboard/mouse mode for the game with the left stick emulating WASD and the right stick the mouse. That should be the default, no need to change anything here.
What you might want to customize however are the button mappings, those are probably not ideal for the game. Best way to do that is opening the page with the key bindings in the game options and then map the keys to the VR controller buttons in a way that makes most sense for you.
To deal with the weapon glitch use the ‘Camera Height Modifier’ under ‘More 3D Settings’ in the vorpX menu. Fixing the glitch directly breaks other things unfortunately, so the camera height workaround is the best way to deal with it.
For cutscenes and menus switch to EdgePeek mode, that’s what it’s for (mouse wheel or right gamepad thumbstick click).
This is a good tip. I’m still somewhat salty that Oculus introduced ASW without an official way for developers to disable it in their apps/games. It has its merits, but personally I really dislike the artifacts it introduces. vorpX is just better with its own rotation only frame interpolation instead of ASW. Comes without any artifacts and also works with uneven framerate ratios, so you can e.g. run games at 60 or 70fps instead of everything below 90 tanking to 45 like ASW does.
I considered several times to force disable it in the past, but since the registry hack the debug tool uses is a system wide setting, that’s a bit risky. E.g. if a PC crashes before vorpX can restore the original setting, ASW could get stuck being disabled without users being able to tell what happened. However, I should probably at least add an option to toggle ASW on/off with the same registry hack to the vorpX tray icon right click menu.
Per default the forum software does not allow users to hide posts of other users, but I’ll check whether there maybe is a plugin that would allow that.
I have a feeling I know whom you have in mind. I sent the user a warning via mail for the time being, hopefully that will suffice.
@ VRan: probably the key bindings for the VR controllers being different compared to the gamepad bindings. You can adjust them to anything you want in the vorpX menu.
Try to get both Virtual Desktop and SteamVR out of the way. Two extra layers between vorpX and the headset always bear the risk of creating weird issues.
vorpX’s native Oculus runtime mode doesn’t work with DX12 for Steam games due to an incompatibility with the DX12 Steam overlay, but OpenXR, which has been added to vorpX recently, does.
- Close both Virtual Desktop and SteamVR.
- Make Oculus your system’s OpenXR runtime by double clicking the .reg file in the linked zip archive: OculusOpenXR.zip. Oculus doesn’t enable OpenXR per default yet, but ist’s already working quite well from my experience. Caveat: The .reg file assumes that the Oculus software is installed in its default folder.
- Select OpenXR as your headset type in the vorpX config app on the ‘General’ page.
- Use Link/Air Link. DO NOT start SteamVR, it’s not required with OpenXR.
Hooking issues almost always are conflicts with other programs on your PC. The by far most likely candidate would be some invasive third party AV program. If you use anything else than Windows Defender, consider to remove it for testing purposes. Some more annoying third party AV programs are difficult to disable. Windows Defender kicks in automatically, so there is no risk involved.
More details regarding other potential hooking conflicts can be found in the trouble shooting guide in the ‘Technical Support’ forum.
Just do it in the order I posted above and leave the FOV hack running while you play the game.
The controller can be hidden on the VR controller page of the vorpX menu, should be called “Oculus Touch Options” in your case.
You can find a step-by-step guide regarding custom resolutions in the vorpX help. The help can be accessed from the config app.
If you encounter any issues with vorpX while using an additional streaming tool like VD, please first and foremost check whether the issue also occurs when you connect your Quest with an USB cable to your PC using Oculus Link.
If you can’t add that particular resolution as a custom resolution, there is no way.
Assuming that’s the resolution you use for streaming to the headset: the game res in not sent unaltered to the headset anyway, so there is no real point in exactly matching game res and encoding res.
Please check whther the issue also occurs when you use wired Oculus Link via USB to make sure it’s not related to the wireless connection.
The easiest way to play the game is with everything set to default. The default settings are dialed in to just work without any tinkering at all.
I would highly recommend to do just that, you won’t even notice that the image is cut off at the top/bottom after a little while.
If you really can’t live with the bars, you will have to raise the game’s FOV beyond what it allows normally with a mod:
- Download and run the mod: https://www.nexusmods.com/residentevil7/mods/23.
- Set the FOV to 127 in the mod.
- Set the Image Zoom to 1.0 in vorpX.
- For a crisper image raise the ‘Resolution Scaling’ in the game’s graphics options.
Aspect ratio: Only with a 16:9 res the game will ever fully fill the view in the headset, at narrower aspect ratios it displays black bars itself. Also the FOV value for the mod will have to be slightly lower for 1440×900, probably something around 120.
Controllers: Either just move them out of sight or disable them in the vorpX menu. They will also disappear after a while when they go to sleep.
I didn’t check the game, but it was my understanding that the profile is based on the Quake II profile and had the same issue (crash on start). The Quake II start crash has been fixed in the last update.
@ Vran: Please check this thread: https://www.vorpx.com/forums/topic/cant-open-inventory-in-re-village/. vorpX has a similar tool built-in. It’s enabled for the game because it doesn’t allow gamepad and mouse input at the same time.
@ luka: Try without VD via Oculus Link/Air Link and see whether that helps.