Forum Replies Created
-
Posts
-
Yes, in Fallout 4 the FOV is applied by writing directly into the according memory addresses. Not sure why you would want that, as a wrong FOV causes image distortion, but if you really want to, you can apply a +/-20° offset in the Direct VR menu.
DX11 TESO has Z3D, that what made clear in the changelog and nothing else was ever said anywhere. You should pester Zenimax to bring back DX9 support, the game had good Geometry 3D before they axed that. 😉
Not sure what your issues may be with Prey 2007 and Quake 4, they work perfectly fine normally. If you installed them under C:\Program Files please make sure that you have write access to the game folders to ensure vorpX can change their config files.
Alternatively try to install them somewhere else where Windows does not block write access per default.
Also make sure to use the Steam versions of Quake 4/Prey 2007. Direct VR will probably not work on old CD versions (or versions you can ‘obtain’ on the internet).
For OpenGL games vorpX uses alternate frame rendering for Geometry 3D, which means there is a slight time offset between the left/right eye. While that isn’t really noticable in OpenGL games that can run fast enough, both games are unfortunately capped at 60fps, which translates to 30fps in stereo due to the alternate frame rendering.
While removing this framecap is possible, it breaks animation speed and other timing related things in both games, so that’s not really an option either.
Please note that the above only applies to OpenGL, not DirectX. OpenGL support in vorpX however probably will never reach the same level as DirectX support, there just aren’t enough OpenGL games to justify the amout of work that would be required.
@ mimousewu: That can happen in Witcher 3 when the load on your GPU is too high. Try to reduce the graphics details in the game’s options menu until it goes away. Alternatively you could switch to Z-Buffer 3D, which is faster.
For one performance is better, although you can address that for the most part by setting the graphics detail in the SE to medium, which is similar to the highest setting in the original version.
The second reason are shadows in Geometry 3D mode, which are perfect in the original DX9 Skyrim, but slightly off in the SE.
The most important reason however is that like most newer games the SE uses a rather blurry shader antialising while in the original you can force good old real multisampling AA through you graphics driver, which looks a lot better in VR.
Skyrim SE works, but the original Skyrim is the better choice for vorpX in most cases. Except maybe for installations with very large HD texture packs that exceed the 32bit memory limit.
Not all games support all Direct VR functions. You can see what is available in a game on top of the Direct VR page in the vorpX menu. It lists what is available or not.
Head tracking in Metro should be almost as good as Direct VR head tracking though normally unless you changed the mouse sensitivity in the game. if you did, you can adjust the head tracking sensitivity in the vorpX menu accordingly to get 1:1 tracking.
There is no Direct VR head tracking for this game, only Direct VR FOV like mentioned in the changelog. The FOV is applied fully automatically on first start without you having to do anything. No scanner in Metro Redux.
You can check whether vorpX was able to find the ini file in the vorpX config app. If you see an entry on the “Restore Game Settings” page for Metro Redux, vorpX was able to find the ini and changed the FOV. If not, something went wrong. In that case please first check that you don’t use an ‘unofficial’ version of the game. Those sometimes store settings in other places than official versions. In such a case I cannot help.
If you use an official version and there is no entry on the “Restore Game Settings” page, please let me know what version exactly you use (Steam/GOG etc.) and I’ll look into it.
I’ll make one or two more videos tomorrow that I couldn’t do today and post them so often that everybody will be practically forced to watch whether they want or not. :)
The Direct VR FOV is automatically applied in the config file for Metro Redux, no need to run the scanner. You should have seen a message about that when you started the game for the first and/or second time with vorpX 17.3.0.
Check this short video to learn about the new Direct VR Settings Optimizer:
I’m not sure whether you ever experienced support anywhere that got back to you immediately, but that would certainly be rather unusual.
Thanks again for your patience.
Please allow some time for an answer. Your issue will be taken care of.
Since we are preparing a major update release for tomorrow right now, there won’t be time for individual support until after the weekend. Thanks for your patience and understanding.
Please send a mail to support |at| vorpx com.
Ideally create a trouble shoot data archive in the config app after starting a few games and attach that to the e-mail. Please allow some time for an answer.
Please send a mail to support |at| vorpx com.
Ideally create a trouble shoot data archive in the config app after starting a few games and attach that to the e-mail. Please allow some time for an answer.
Please try to unintall your AV if it’s anything else than Windows Defender. Some particularly invasive AV programs do not allow their users to really disable them. One example would be BitDefender where the so called “Advanced Threat Protection” would still block vorpX besides the scanner being disabled. There might be others behaving similarly obscure.
In addition to that make sure that your monitor and your headset are plugged into the same GPU if you are using a multi-GPU system.