Forum Replies Created
-
Posts
-
vorpX already provides out-of-the-box automatic FOV setup for Half-Life 2 via the DirectVR memory scanner and more than that. You can actually play the game in (almost)roomscale VR. There isn’t anything useful this update could add.
If nothing works at all there usually is some conflict with another software that also hooks into games. If you see a dialog popping up after a minute or so with some trouble shooting options, please first try to install a hook helper to the game folder (first option in the dialog).
If the dialog doesn’t pop up, or installing a hook helper doesn’t help, you have to dig deeper. First please check wether vorpX works in ‘Generic Headset’ mode (which will display its output on the monitor) to see wether there is a general hooking issue or a problem with sending the image to the headset. If the generic headset mode doesn’t work either please double and triple check for potentially conflicting tools. Ideally disable/remove everything that may get in the way. The trouble shooting guide above has more details.
If generic mode works, but your actual headset doesn’t, please try all three VR APIs you can select in the vorpX config app. Your Quest will work best in native Oculus mode or with OpenXR (if enabled in the Oculus app), but SteamVR should also work. Ideally try with Link first, additional tools like VD just make things more complicated.
You can change most shortcuts vorpX uses in the config app under ‘Ingame key bindings’.
Unless you absolutely need your remapping tool for some reason, it might still be a better idea to not use it. Anything that also hooks into other applications in a similar fashion as vorpX should be avoided whenever possible.
Something is weird with Bioshock 2 DX9. I can’t replicate any crashes anymore here, but if it still doesn’t work for you, the remaster is the way to go. I have spent dozens of hours looking into this issue over the years, nothing left to recommend than using the remaster if the DX9 version still is crashy for you.
Thanks for the FOV hint. Not sure why, but looks like the profile is borked in that respect. ‘Letterbox 1’ is a little bit too much, the ideal settings would be aspect at ‘Pixel 1:1’ and ImageZoom at 0.68. I’ll adjust the defaults for the next update.
I halso have DirectVR tracking working. Needs a bit more testing to make sure it works in more than one spot, but I’m 90% sure that won’t be an issue, that should allow you use G3D without a super higend GPU.
An update with the updated profile will be released early next week.
The hook helper is mandatory. RDR2 does not work without it.
If installing the helper fails for some reason, copy the d3d9.dll from the zip file below to your RDR2 game folder (next to RDR2.exe). That should help. The archive has a password, just in case the hook d3d9.dll triggers some overzealous AV program: ‘vorpx’ (without the quotes)
vorpX can try to force games to a specific monitor in ‘Generic Headset’ mode. The option is more or less an almost forgotten leftover from the Oculus devkit days 8 years ago, but should come in handy for your use case. You can find it on the ‘General’ page of the config app under ‘Display/Monitors’
Doesn’t work for every game, but is definitely worth a shot.
Like said above, please try a full factory reset. Leave everything at default except changing the game resolution for better image quality. Under normal circumstances the profile works perfectly fine at default settings aside from the gamepad not being handled for weapon hide since I wasn’t aware that the game has gamepad support.
Please DO NOT tinker with any FOV altering settings, including Image Zoom, may and probably will break the weapon detection. Just leave everything at default. There is no need to tinker with any vorpX setting at all. Everything is dialed in to work out of the box with default settings.
I’ll take a look at the gamepad config. Wasn’t aware that the game supports gamepads. The weapon hide feature can be configured to also react to gamepad buttons, but since I wasn’t aware of gamepad support in this game, only key actions are configured.
Until I upload an updated profile please stick to mouse and keyboard.
The wapon is supposed to be shown when you press any weapon realated button, in particular in this case: the 1-6 and R keys and the left/right mouse buttons, also using the mouse wheel to change the weapon triggers shwonig it. Works perfectly fine here with the default profile settings.
Don’t know what else to suggest besides maybe a full factory reset.
vorpX does not work natively with PSVR headsets, you need a second application that can make your PSVR look like a SteamVR headset (e.g. iVRy) and then select ‘SteamVR’ as your headset type in vorpX, not the ‘Generic VR Display’.
That way you will also be able to use the desktop viewer BTW.
vorpX should automaticallly install a hook helper for RDR2 on first launch normally, doesn’t work without that.
For Oculus headsets always select Oculus (or OpenXR, which in the future will superseed the vendor specific APIs), SteamVR should only be used for native SteamVR games like Index or Vive.
You shouldn’t have to tinker with any controller mappings, they are supposed to function as gamepad in RDR 2. The control scheme is VR oriented and a bit different than the normal monitor controls. No strafing, which always feels somewhat unnatural in VR, instead you can move and turn with just the left stick.
Since the weapon initially disappears the system in general appears to work. Not re-appearing sounds as if maybe the configuration is borked.
If you already played the game with vorpX before the weapon hide feature was introduced or imported some user settings from the cloud, please reset the profile to default. The feature shows the weapon based on weapon related key presses. Any user settings from before the feature was introduced, regardless whether they are your own or downloaded from the cloud, don’t have the required configuration data. A reset to default will fix that.