Forum Replies Created
-
Posts
-
Not directly related to official/unofficial, but the user override for positional tracking in profiles where it’s off per default doesn’t do anything currently. Fixed already in the current dev build. There will be a maintenance release in a week or two including the fix.
Games have to run in the foreground for vorpX track keyboard input. That’s pretty much the only thing I can imagine to be the issue here. If you run a game fullscreen, it should always be in the foreground. If you run a game windowed, try clicking into its window to ensure it’s the foreground window.
That would require the game devs to implement an OpenXR rendering path to their games. Unlikely to happen for the majority of games that have already been released. Many future VR games however will more likely than not use OpenXR instead of SteamVR since OpenXR is supposed to eventually replace the vendor specific runtimes.
Checked your logfile, no good news unfortunately. The game crashes extremely early without even the exception handler kicking in, quite unusual. The last action in the log is vorpX trying to install the basic D3D hooks. If it wouldn’t work for me, I’d say looks like some anticheat system exiting the game on purpose. That can’t be it though in this case.
Whether the crash is directly related to the hooking process or happens shortly after is difficult to tell given that no exception is thrown. Assuming the first, I’d suggest to try disabling any background process you may have running that may also hook into games/the graphics pipeline.
Also switching between regular/alternative hooking in the config app (General/Misc.) is worth a shot. With some luck that can help to deal with hooking conflicts.
Another option would be to try OpenXR instead of SteamVR. Unlike the Oculus mode that should work while still avoiding the SteamVR detour:
- 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.
Can’t replicate this for the life of me, sorry guys. Would be great if could send me some trouble shoot data that would allow me to check whether your systems maybe have something in common that could potentially cause the problem:
1. Try to launch the game.
2. After it crashed create a trouble shoot data archive in the config app
3. Send the archive to support at vorpx com.As suspected to display its menu the dinput8.dll from the mod hooks into the same D3D functions as vorpX, which causes a conflict. It’s possible to work around the conflict in principle, although that doesn’t guarantee that things will work as expected.
Since these dinpunt hook mods are fairly popular for several games, I’ll add some special treatment in case vorpX finds a dinput8.dll in a game folder. If one is found, the next vorpX will enable the workaround mentioned above, but also display a warning that such a mod may cause unpredictable behavior.
Menu:
Switch to EdgePeek mode for using menus (mouse wheel click, right thumbstick click). In EdgePeek mode vorpX temporarily switches to a cinema like view and also scales the HUD/menu to full size to circumvent any issues that may potentially arise from scaling it down.
Zoom/FOV:
The zoom value is set to the fairly low default value on purpose to make sure the game’s field of view matches your headset’s field of view. DO NOT change it unless you have a way to increase the game’s fiels of view, otherwise the image will look zoomed in/warped.
That’s the way to handle FullVR FOV in games that don’t allow to set their FOV high enough to match your actual headset FOV. You can find more information on the matter in the ‘Essential Hints’ guide, either in the vorpX help or here.
However, for RDR2 you might be able to use a mod that enhaces the field of view. Never tried it myself, but you can find detailed instructions here.
Not a full profile, but you can share and download user settings for official profiles. There are basically two flavors of user profiles: full user profiles for games where no official profile exists and user settings for official profiles. You can’t entirely override an official profile, but you can create/share/download user settings for official profiles.
Sounds as if the installer for some reason can’t access the folder you selected as install location. Please try to install vorpX in the default folder if installing it to a different drive fails.
Official profiles can’t be overwritten, but you can upload your individual settings for the profile to the cloud just like you could with a full custom profile.
Just checked the game a few days ago without encountering any issues (see above), so there isn’t really much more I can suggest than in my last reply.
Only other thing that comes to mind is that maybe WMR may not be set as your OpenXR runtime. Try to open the WMR portal, it will check on start whether WMR is registered as OpenXR runtime and complain if it isn’t. SteamVR shouldn’t be running at all while using OpenXR with a WMR headset. If SteamVR launches with the game although you are sure that WMR is set as OpenXR runtime, please double check whether vorpX is really set to OpenXR in the config app.
As far as I understood your problem was the desktop viewer not working for you. That’s what my reply was about. You don’t need it to use vorpX with games. The desktop viewer is pretty much just a free add-on to vorpX.
If you also have trouble with hooking into actual games, please first and foremost go through the trouble shooting guide on top of this sub-forum. Hooking issues almost always are conflicts with other programs that also hook into games. The guide above has more details on that.
If after going through the guide you still have trouble with hooking into games, please try to launch one or two games, then create a trouble shoot data archive in the vorpX config app and send it to support at vorpx com.
Just a heads-up that there will be an official profile shortly, checked ME1 today. Took me a little while to get rid of an occasional crash related to antialising, but now things are working as they are supposed to. Antialising included.
Provided there aren’t any surprises with ME2+3, I expect to get profiles ready for all three games before the weekend.
Just a heads-up that the feature has to be enabled on a game-to-game basis since it rquires some game specific settings. It doesn’t work automagically. Currently it’s enabled for the following games: Half-Life 2 (+episodes), Portal 2, Black Mesa Source, Titanfall 2, Fallout 4, Crysis, Skyrim Special Edition, Aliens: Colonial Marines.