Forum Replies Created
-
Posts
-
Please first try to switch between the DX9 and DX11 version of the game, maybe one works better for you.
If even the desktop viewer doesn’t work, there might be something more serious going on though, almost certainly a conflict between some other program on your PC and vorpX. Likely candidates besides virus scanners are: any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot is to disable/uninstall every background program that would not be there after a fresh, Microsoft only Windows install.
If you can’t solve the issue this way, please try to start a few games, then create a trouble shoot data archive in the vorpX config app and send me this archive. I will then check whether I can find something that you may have overlooked.
No mail from the mail address that you used to register on the forum in the mailbox, sorry. Please try again using the contact form in the support menu above.
No problem with Bioshock 1, 2, Infinite (Steam) here. Arma 3 also works as expected without BattleEye, normally started through Steam and the Arma 3 launcher.
Please primarily check for possibly conflicting programs on your PC. A lot of other apps also hook into games, not all of them are obvious. This can cause all sorts of issues with vorpX. Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot is to disable/uninstall every background program that would not be there after a fresh, Microsoft only Windows install.
Game support is largely independant from the headset used. vorpX hooks into games reagrdless which headset is selected. If you have issues with multiple games not hooking in a similar manner, please check the trouble shooting guide in the help in regard to possible injection conflicts.
The Game Optimizer is a separate program. Not all supported games have an optimizer entry since not all games have editable config files. The optimizer changes game config files if possible to make a game work better in VR, while a game being supported means that there is a profile for Stereo 3D (Z3D and/or G3D).
vorpX actually works with even more games than those on the supported games list BTW (albeit in 2D for unsupported titles) since it tries to hook into any D3D9/10/11/OpenGL game you launch.
You can set a custom value for fDefault1stPersonFOV in your [Documents]\My Games\Skyrim\Skyrim.ini. Per default the vorpX Game Optimizer sets it to the same value as the world FOV, but you can use a higher value to make the hands/weapons smaller (e.g. 140 or 150).
The tricky part is to apply it after changing the ini: for some odd reason once in the game you have to open the 4-way menu (or “star menu”) and from there go to the map. After closing the map the new value gets applied.
Separated aim/look has to be supported by games themselves (or with mods), that’s not something that can be implemented retroactively on the DirectX/OpenGL level unfortunately.
One such game is Arma III, which is able to do this natively. You will also need an external tool (OpenTrack) to use the separated aim/look with Arma.
A more popular game that allows this with a mod and vorpX is GTA V. The mod can be found here http://grandtheftvr.com. It has alpha Vive support. Oculus only works until runtime 0.8 (DK2) though as far as I’m aware.
In regard to image quality try higher game resolutios. The default suggestion of 1280×1024 is a general compromise between performance and quality. For better quality try 1600×1200 or 1920×1440. The latter provides the same image quality as native apps have, but might be too slow for newer games. So always keep an eye on performance when trying higher resolutions. You can check the current frame rate with ALT+F. 45+ game fps are required for a comfortable experience. In the long run a reasonable framerate is the most important thing.
Menus that are outside your view are best used in EdgePeek mode (press the mousewheel), which temporarily switches to a cinema like view.
Enhancing the FOV is crucial for full VR mode. What can be done in this regard varies from game to game. In many games this is solvable perfectly, in others you may have to live with compromises. The Essential Hints Guide in the vorpX help lists the various options vorpX provides to deal with the matter.
For Far Cry 3 please make sure to disable the Uplay ingame overlay in the Uplay options. Some Ubisoft games don’t hook with it enabled unfortunately. Also try both the DX9 and DX11 version of the game. One might work better for you.
Arma III requires BattleEye to be disabled. Since a BattleEye update some time ago vorpX does not work anymore with it.
You can get it look good on Vive too by following the hints given above. I would really like to understand what doesn’t look good in your opinion, but I honestly can’t. Sorry.
The latest versions won’t work with DK1 anymore since the 1.x Oculus runtime doesn’t support it, but you can contact support |at| vorpx com to get the last vorpX version that does.
Are you using a Vive? If so, flickering means frame rate being too low. The OpenVR runtime is made for 90fps with a 45fps fallback option. Below that things fall apart unfortunately. vorpX can deal with these situations to a degree with its custom async timewarp, but there are limits to that.
While performance will be OK in many areas, you definitely will always encounter areas with a frame rate below 45fps with Geometry 3D in Skyrim unless you severly reduce detail (at least the medium quality preset is required). Either that or switching to Z-Buffer 3D are the only options to get the Vive working reliably with Skyrim under all circumstances unfortunately. No way around one of these.
Works also with Vive, but not as good as with Oculus, which now has driver level timewarp, by a long shot.
With OpenVR vorpX can handle short dips or a few frames below 45fps with its own timewarp, but that’s it. OpenVR doesn’t really take the possibility of low frame rates into account unfortunately.
vorpX works with two distinct render threads to provide its custom async timewarp. The first value is the frame rate that the game runs with, the second value is the frame rate of the thread that does async timewarp and finally pushes the image to the headset.
If you are tweaking game options for performance, Game FPS is the important value. It should reach 45fps for a comfortable experience. If that is the case, direct mode fps in most cases are OK automatically.
For some games you can scale the HUD with vorpX. If this is available for a game, you find HUD Scale and HUD Depth options on the image page of the vorpX ingame menu.
There might be an injection conflict with some other program on your PC. Many programs also hook into games and can cause such an issue. Not all of them are obvious.
Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot is to disable/uninstall every background program that would not be there after a fresh, Microsoft only Windows install.
If you can’t solve the issue this way, please try to start a few games, then create a trouble shoot data archive in the vorpX config app and send me this archive. I will then check whether I can find something that you may have overlooked.