Forum Replies Created
-
Posts
-
No hooking problem here with Arma 3 and the latest vorpX.
Hooking issues that suddenly occur after a vorpX update may be related to some overzealous AV software disliking the new version.
If you use anything else than Windows Defender, try to disable your AV software for testing. Note that some third AV programs are notoriously hard to disable, you may have to disable several modules. If that helps, try to add an exclusion for the vorpX program (typically C:\Program Files (x86)\Animation Labs\vorpX) and the game install folder.
Alternatively consider switching to Windows Defender, which is less likely to cause problems. On Windows 10 Windows Defender kicks in automatically when you uninstall third party AV programs.
Please enter the same e-mail address into the download form that you used to register vorpX. The request will be ignored otherwise. The address you posted above is not in our license database, so you probably used another one originally.
If you don’t have your installer anymore, you can get one here: https://www.vorpx.com/request-new-download/
Sounds as if you may have selected the wrong display type in the config app accidentally.
Go to the ‘General’ page in the config app and make sure that ‘SteamVR’ is selected as headset type for a SteamVR compatible headset.
Fully filling the view vertically in FullVR mode requires a camera field of view above what is normally possible. You can find detailed instructions in this regard in the stickied RDR2 thread on top of this sub-forum.
Just a guess: If by any chance you have raised the 3D-Strength above the default value, please change it back to default (1.0). That’s generally good advice whenever you encounter lighting issues in a G3D game.
Two things you could try are running the game windowed (if it has such an option, can’t remember currently) and trying the alternative hooking method in the vorpX config app. Both can sometimes help with startup issues.
Caveat: Alternative hooking is not better than default hooking, just different. Even if it solves an issue with one particular game for you, always remember to switch back to default hooking. You will encounter issues with games that need the default method otherwise.
Apart from that please check your PC for potential hooking conflicts. These are not always obvious, e.g. some chat programs may hook into games and cause a problem. More detailed info about this can be found in the trouble shooting guide in the help (also stickied on top of this forum for convenience).
If you have a gamepad connected to your PC, please disable it in the Fallout 3 options menu. The game only allows either mouse/keyboard or gamepad input. Not both at the same time.
vorpX overrides the gamepad before running the DirectVR scan since in that case it emulates a mouse for head tracking. After the scan that isn’t necessary anymore, so the gamepad override the gets disabled. When that happens while you have the gampad enabled in the Fallout 3 options, the game disables the mouse like it would without vorpX.
TLDR: After running the DirectVR scan Fallout 3 behaves like it would without vorpX, so you have to disable the gamepad in the game options if you want to play with mouse and keyboard.
Not really sure what you expect me to reply to that. I don’t curate user profiles, I don’t even know them usually.
If the Immersive Screen mode is not your thing, you can always try to build a FullVR profile yourself following the guide I mentioned above. Others apparently are happy with the user profile as it is since it allows them to play a game with a VR headset that can’t be played in VR at all otherwise. Can’t see anything wrong with that.
Glad you like it. There are a few quirks left with the Generic 3D Display mode that I’ll iron out for the next release, namely the camera height modifier not working as intended and HUD-depth doing nothing although available for a profile.
Happy New Year!
Thanks for the feedback. I more or less rebuilt the whole profile, using some features that weren’t available when the original profile was done six years ago. Good to know that it works better for cutscenes this way, I’ll probably do the same for ME2+3 then.
Happy New Year to you too.
Has to be something on your end, I’m afraid. I checked the game literally minutes before the last vorpX update was released with the Black Mesa version that was released on Christmas Eve. It was also reported working well by another user in the 20.1.0 release thread.
Please reset the profile to default or try a full factory reset (config app/trouble shooting). You don’t need any cloud profile, the default profile works out of the box.
I see, that’s set on purpose then by vorpX’s DirectVR because the game’s FOV can’t be set high enough to allow more. In games with automated FOV adjustment vorpX can cap the max allowed ImageZoom to match the max possible game FOV. Sometimes vorpX is smarter than you may think. Didn’t recall that the Hunter was such a case.
That doesn’t automatically mean that any developer can do it too. Oculus can do it, of course. Whether they allow app developers to do it is a different question. May or may not be the case.
Not really sure what to recommend aside from the the above.
One more thing you could try is disabling head tracking in the vorpX config app. not really a solution, but at least that way you could see whether the issue is related to head tracking.
if you have some utility running in the background that is related to mouse or gamepad input, please also try to exit that.