Forum Replies Created
-
Posts
-
Changing the camera height may have unwanted side effects. IIRC there is a warning shown in the menu whenever it is set to anything else than 0. I’ll check whether that is the case and add one in case it is missing.
I’ll make an updated profile available for download from the cloud within the next few days. It’s already basically working, finalizing it takes a bit of time though since it has to be tested in a few start areas to catch as many shader glitches as possible
For Rise of the Tomb Raider please make sure that it’s set to DirectX 11, vorpX does not support DX12. Same for Dragon Age Inquisition which you might have set to use AMDs Mantle in case you use an AMD card.
If you are sure the games are set to DX11 mode and happen to have the Windows system restore functionality enabled, try to go back to a system restore point from before the issue started to occur.
@ steph: There is no Z3D support for OpenGL and G3D doesn’t work correctly anymore with newer NMS versions due to the reasons outlined in the other thread. There really is no way at this point.
Adding full support for newer, shader based OpenGL games is not likely to happen anytime soon. Doing so would require a lot of time which is better spent elsewhere considering the small amount of games that use OpenGL.
FOV doesn’t have to (and should not) be tweaked manually. The FOV is calculated and set automatically by vorpX.
As usual with hooking issues please first and foremost check for conflicts with other programs on your PC that also hook into gamnes. That is the almost cerainly the cause of such an issue, even more so if something worked before and now doesn’t anymore.
Typical candidates are: virus scanners, CPU/GPU utilites, chat programs, video recording/streaming programs and generally every program that can show notifications in games.
The best way to trouble shoot this is to exit/uninstall programs running in the background. If you use any other antivirus program than Windows Defender, chances are quite high that your AV software is the culprit.
Further trouble shooting hints can be found in the vorpX help or alternatively in the trouble shooting sticky post.
Normally vorpX is supposed to display its own cursor in Space Engineers since the game’s cursor can’t be duplicated for the left/right eye.
If you can’t see the vorpX cursor, try to press ALT+C just in case the cursor visiblity didn’t get tracked currectly.
The FOV is handled automatically for Battlefront 2. vorpX sets it to a value that is perfectly calculated. Setting the FOV manually in games where vorpX can do that automatically can cause comfort issues for more sensitive people rather than avoiding them since even small deviations from the correct FOV may be irritating for them.
Caveat: the game is a bit special, FOV adjustment is only possible in multiplayer. If you want to play the campaign, it’s better to play in immersive screen mode like dellrifter (and the vorpX startup message for the game) suggests.
Image quality: you can run games at any resolution with vorpX. Check the “Custom Resolutions” section in the vorpX help, it explains how to add resolutions to your PC that it normally cannot display. Afterwards you can select a preferred quality on the DirectVR page of the vorpX ingame menu in Battlefront 2.
There is an extra software layer involved to translate SteamVR calls into WMR calls for the Odyssey, but performance should be largely the same.
If you have problems with vorpX hooking into games please first and foremost check for conflicts with other programs on your PC that also hook into gamnes. That is the most likely cause of such an issue.
Typical candidates are: virus scanners, CPU/GPU utilites, chat programs, video recording/streaming programs and generally every program that can show notifications in games.
The best way to trouble shoot this is to exit/uninstall programs running in the background. If you use any other antivirus program than Windows Defender, chances are quite high that your AV software is the culprit.
Further trouble shooting hints can be found in the vorpX help or alternatively in the trouble shooting sticky post.
When motion controllers are active in keyboard/mouse emulation mode, the gamepad also is set to kb/mouse emulation mode regardless of how you set it up. That is necessary since some games do not work correctly with concurrent kb/mouse and gamepad input.
However, thanks to your hint VR controllers can only be considered active now after pressing a button or using a trackpad/thumbstick once which makes it far less likely that this override gets activated unwanted.
There is no way to get stereo 3D for newer No Man’s Sky versions, can’t be changed with a different profile. Newer NMS versions partially use a way to transform geometry that vorpX’s OpenGL pipeline does not handle.
The game still has DirectVR FOV calculation though, so at least it’s easily playable in 2D Full VR – provided you can live that.
Regarding the more general question: official profiles cannot be removed by design. This may look like an unnecessary restriction, but it ensures that beginners or uncareful users cannot erase profiles by accident, which had to be ranked higher in this case than total freedom for power users.
Provided you didn’t disable automatic settings in the vorpX config app, Far Cry 3 has fully automated Direct VR field of view since quite a while which is adjusted perfectly to fit your headset. The same is true for Far Cry 1, 2, 4 and Primal, also Battlefield 3, 4 and 1.
For games that do not have that please check the “Essential Game Hints” guide in the vorpX help. It explains which options you have to either solve or circumvent FOV related issues in cases that vorpX cannot handle automatically.
Make sure to run Portal 2 with a 4:3 resolution (e.g. 1280×960 or 1600×1200).
That fixes the screen flicker in Portal 2 and is better for vorpX anyway since it avoids rendering pixels that aren’t visible in the headset. If that isn’t the case, You should see a message explaining it when you launch the game.
Good news: a profile update will suffice to get it working again.
Will be uploaded to the cloud sometime next week. Unfortunately not only the basic 3D has to be fixed, but also many shader definitions (sky, HUD, shadows etc.) must be redone which takes quite a bit of time since they have to be tested in multiple start areas to catch everything.