Forum Replies Created
-
Posts
-
Official stance on this is that you do it on your risk.
vorpX has been used by many to play multiplayer games and mmorpgs over the years without problems. But since this is no guarantee for the future you have to decide yourself what to make of this information.
That your workaround does the trick is pretty much in line with my above guess (locked database file), thanks for that. No solution yet, but at least I’m almost sure now where the issue may be located.
There are a few minor issues with the advanced authoring hence authoring keys are on hold currently. Will hopefully be fixed in the next vorpX version.
You need to make sure that your headset and the main monitor, which games are running on, are connected to the same card (your dedicated graphics card).
vorpX needs to copy rendered images between the game window and the headset. This cannot work when both aren’t connected to the same graphics card.
The current vorpX version requires the Oculus runtime 1.3.
In regard to Arma III please make sure to disable BattleEye. The BattleEye dev some time ago decided that the way vorpX hooks into games is not the right way in his opinion. An attempt to discuss the matter with him to get back to the previous state, where vorpX worked fine with BattleEye, led nowhere.
Works fine here. Maybe it’s a more general hooking issue. Please try to create a vorpX desktop shortcut to your wow.exe or wow-64.exe (not the launcher!). These shortcuts in some cases are more reliable than the auto detection.
To create a shortcut right click the vorpX tray icon, choose “Create Desktop Shortcut”, navigate to your WOW folder and lastly select the .exe you want the shortcut to be created for.
Please try to run the game windowed. That makes things easier for vorpX in regard to how Oculus Home works.
Cloud settings are automatically imported into the settings database. There is nothing you have to besides importing them from the cloud.
This shouldn’t be necessary if you start SteamVR before playing games with vorpX. Still thanks for this solution!
For FSX please try to switch between DX9 and DX10. DX9 is preferred due to Geometry 3D support, but maybe Dx10 works better for you.
Arma III only works in single player mode or on non BattleEye servers. The BattleEye dev some time ago decided that the way vorpX hooks into games is not the right way in his opinion. An attempt to discuss the matter with him to get back to the previous state, where vorpX worked fine with BattleEye, led nowhere.
I can’t really say whether one of the new functions may or may not be of any use for vorpX yet. In general I’m sceptical though. It’s quite likely that these things only make sense when being used directly in a game engine’s rendering code.
In Fallout 4 you have all options that vorpX provides in regard to HUD handling. You can scale it to fit your needs (image page of the ingame menu) and/or use the EdgePeek function (press the mouswheel). This is also mapped to one of the thumbsticks when using the gamepad emulation IIRC.
If you have a really fast PC you can also try higher resolutions than the recommended one (e.g. 1600×1200). For Fallout 4 I wouldn’t really recommend that though. It’s a highly demanding game.
From your description (black game window plus sound through the headset) it sounds as if vorpX would hook correctly, so without additional information I can’t recommend anything, sorry.
If you can’t make it work, please try to start a few games, create a trouble shoot data archive in the vorpX config app and send that to support |at| vorpx com. I will check whether you might have overlooked something in regard to possible conflicts with other programs and get back to you.
That is all that has to be done. Please try without your controller software and any other background processes running and see whether that makes a difference.
This seems to be a rather unique issue, I can’t remember a single report of something even remotely similar so far. Hence my guess that it may be linked to your software.