Forum Replies Created
-
Posts
-
@ dborosov: One more thing: please also make sure that the “Never change any game settings” checkbox in the config app is unchecked. I somehow have a feeling that’s the issue in your case. This option is only meant for trouble shooting purposes. If you want to prevent vorpX from changing settings for a specific game, please do that in the vorpX ingame menu on a game to game basis.
@ haints: The correct FOV is the one that provides the same camera angle in the headset that your eyes have in reality, there is only one such FOV. That’s also the reason why you do not see an FOV option in any VR game, deviating from this FOV always causes image distortion. I am aware though that some of you guys like to experiment, hence the +/- 20° offset option.
That said, if you disable the Direct VR FOV option in the vorpX menu, it is disabled and you can still use an external tool. If your tool of choice does not work anymore, it’s quite likely that this is caused by a recent GTA V update. Setting FOV via writing into a game’s memory addresses is always prone to break with game updates.
Please first check whether your vorpX version is up-to-date, should be 18.1.3. You can see that in the config app (bottom left corner).
As the next step make sure to use the official Kingdom Come Deliverance profile by doing a full factory reset (config app, trouble shooting page).
If afterwards you still do not see “Field of View: modified game setting” on top of the Direct VR page in the ingame menu, please send me a trouble shoot data archive to support |at| vorpx com. I would consider that next to impossible, but one never knows, of course.
The optimizer is now part of the core app and “just happens” when you start a game, which gives it more options to do things fully automated. Whenever a game is supported by the optimizer and changes any settings you see a notification in the headset.
Check the video in this blog post to see how that works.
For older games the rule is checking the currently available versions, which usually means Steam and GOG. There is no way to keep track of (or often even acquire) every potential CD/DVD version that might have been released in the past.
I’ll check NWN1/2 before the next update to see whether an official profile can improve anything. They’re sitting in my GOG library ‘unopened’ for ages.
There have been no changes in this regard. You can still disable The DirectVR FOV in vorpX and use another method. If that does not work anymore, the external fix may be broken due to a GTA V update.
You can apply a +/-20% offset to the pre-calculated FOV on the DirectVR page of the vorpX menu though if you want.
Just keep in mind that FOV for full VR mode is not a matter of taste, there is only right or wrong in this case. You might want to achieve a special effect with another FOV, hence the option to apply the manual offset, but there is only one correct FOV and that’s the one that is pre-calculated. Everything else will cause image distortion.
BTW: Please post such things in the “Technical Support” sub-forum to help keeping the forum in an at least halfway structured state. Thanks! In the future I will move more posts without further notice.
The FOV is not handled by the scanner but by setting the value in the game’s ini. Whenever that is the case for a game, it says “Field of View: modified game setting” on top of the Direct VR page in the menu.
If you want to check whether that worked, go to: “C:\Users\[User]\Saved Games\kingdomecome\profiles\default” and open “attributes” with a text editor.
There you should find a line with “fov” and the value 96 (with default vorpX settings). If that is the case, the FOV is perfectly correct unless you maybe changed it yourself with another method, e.g. a mod, that might override this setting.
I have read your post and it will be looked into. If your issue can be replicated here and confirmed to be a vorpX issue, it will be addressed.
Without having checked yet it looks more like a Windows 10 issue with Games for Windows Live though.
You can choose a preferred resolution on the DirectVR page of the vorpX menu and also apply an upscale multiplier there (image page).
ENB mods can cause a conflict since they hook into DirectX like vorpX. There is an ENB injector available on the ENB website, that is probably your best bet.
The older the game the better the chance to get an OpenGL title working with stereo 3D. Good base profiles for experiments are Quake, Quake 2, Quake 3, Quake 4, Star Wars Jedi Knight 2 and Amnesia, which all use slightly different stereo approaches or settings. As a last resort try the D2X-XL profile, which still uses the outdated (but most compatible since simplistic) pre 18.1.0 implementation.
I can’t give you any other answers than the ones I gave you in the my previous replies. Sorry. There is no way on earth that camera alignment is not working corectly for you.
Maybe try a factory reset (config app, trouble shooting page) in case you tweaked any settings.
If there even was a remote chance for a bug that may cause what you experience, I’d be more than happy to check that, but there just isn’t.
The HUD elements in Skyrim explitely are not supposed to be centered on the image like when you play mono on your monitor – as already said in my answer above they have stereo depth with vorpX. Creating stereo depth for HUD elements works by shifting the HUD inwards.
That is how it is supposed to be, it’s actually the very basic principle of stereo rendering.