Forum Replies Created
-
Posts
-
There might be some options for utilizing a second graphics card in the future, but classical SLI probably never will work. Normally the graphics driver outputs the final image to the monitor in SLI mode, vorpX however has to feed the final image to the headset, which makes the whole process *very* different from normal monitor rendering.
Most PCs are not fast enough for Geometry 3D to work with Fallout 4 on Vive. The OpenVR runtime doesn’t handle low frame rates very well, you have to make sure to run games with 45fps+ on Vive. Normally you should see a warning in this regard.
For Fallout 4 that means that Z-Buffer 3D is the right choice. Especially if your are playing with Vive. The Oculus runtime is more forgiving in this regard.
If vorpX allows to scale a game’s HUD, you can find the according options (scale and depth) on the image page of the vorpX ingame menu.
For games without a scalable HUD you can use vorpX’s EdgePeek mode (press the mouse wheel) while playing.
If you are using a Vive, you need to make sure that games run at 45fps+ at all times. The OpenVR runtime does not work well with frame rates below that. You should see a warning about this normally. The Oculus runtime is quite a bit better at this.
All you need to do for full VR mode is disabling Virtual Cinema Mode (shouldn’t be on per default for Borderlands 2) and (important!) set the field of view (FOV) to 120°, which in case of BL2 can be done with the vorpX Game Optimizer in the config app. With the FOV set to 120 you do not need to change the image zoom.
If that is the case you are “inside” the game and can look around just like with native VR apps.
Please check the below settings (should be the default for many first person games)
1. Virtual Cinema Mode is disabled
2. Aspect ratio mode is set to “Pixel 1:1” (image page of the ingame menu)
3. Image Zoom is set too 1.0 (also image page of the ingame menu)With these settings there is no border. Be aware that you have to make sure to set a game’s FOV to 120 with these settings or the image looks zoomed/distorted.
You can try to make copies of existing profiles in the config app and assign other programs to these copies. You should know what graphics engine (or at least API) the game is based on, then you can try a similar profile.
Random example: If you know your game uses the OpenGL API and and is based on the idTech engine, you could try the Quake 3 profile.
There is no guarantee that this will work, but it’s worth a try.
If the FOV still isn’t 100% correct, please either use a slightly higher value in the .ini or compensate for the rest in the vorpX ingame menu by adjusting the ImageZoom value (image page).
3D: Far Cry 4 “only” has Z-Buffer 3D, which provides less depth for foreground objects (not in the distance though), but is a lot faster than Geometry 3D, which renders everything twice.
For better image quality, please choose another resolution. The resolution that utilizes the max. amount of pixels on your headset would be 1920×1440. Just keep an eye on performance ([ALT][F]). You need to maintain 45fps+ at all times for a pleasent experience.
If the FOV is set correctly in a game the image can’t be zoomed in anymore.
Please try this in Doom 4 where you can change the FOV directly in the game options. If set to 120° you have a much wider view and thus the image isn’t zoomed in anymore.
The wrapper version of ENB will not work, but the injector version does. Haven’t tried myself for a while, but there recently was another topic about this and the conclusion was that it still works.
Future release will have more new profiles again. The last vorpX releases all were focused on technical changes forced by frequent runtime changes and new headsets, but from now on there will be greater focus on games again.
If you mean the game HUD depth then you can already place it anywhere from infinity to very close. A value of 0.0 places the HUD a few centimeters away from your eyes, 1.0 places it at infinity.
Please leave the focal offset (convergence) at 0.0. This actually doesn’t do anything useful for VR. It was initially left visible on request of stereo driver users coming from monitor S3D, but it really does more harm than good (actually no good at all) in VR and was removed for good in the latest build.
Changing the focus point/convergence (and thus also the infinity plane) is probably the cause of your HUD depth issue.
This is known bug, which sometimes occures and sometimes doesn’t. Sorry for that. It’s related to the new database based profile system. Probably the database file gets locked sometimes and can’t be written to.
Until a fix is ready you might be able to solve it with a reboot, which would unlock the database file.