Forum Replies Created
-
Posts
-
How that works depends on the game. If the FOV is applied via changing an ini setting, you need to restart the game for an FOV change to be applied. Usually a message prompts you to do so after clicking “OK & Save” if that is the case.
If the “Immersive Screen Mode”, which in principle is what you did with cinema mode before, is not 100% satisfactory in regard to what you have in mind for a game, I would suggest to disable all auto configuration. Then you are free to tweak a game’s FOV/resolution manually again, which is basically how things were before the latest update.
That is how it is supposed to be, The auto-FOV for cinema mode ist not as high as the auto-FOV for full VR mode. You can apply a +/- 20° offset in the vorpX menu. If you want to achieve a different effect for your individal setup, disabling the auto-configuration is the way to go. You can then freely tweak game-FOV, resolution etc. like before.
The auto configuration however will not be changed, it is meant for those who like to just play and thus it changes settings in a way that avoids any need for tweaking at all as much as possible.
Under normal circumstances there shouldn’t be any tweaking involved at all in making the Metro Redux games work. Also no need to download or apply any profiles. Might make sense to restore their profiles to default in the config app before doing anything else.
Head tracking in Metro games is moused based, so it’s not quite as good Direct VR head tracking, but it’s close in these games. Both use Microsofts “Raw Input” and have no mouse acceleration, so there is not too much of a difference compared to Direct VR head tracking. With the default mouse sensitivity in the game head tracking should be 1:1, otherwise you can adjust the tracking sensitivity.
FOV: The FOV is auto adjusted in these games. Unless that fails for some reason on your machine, FOV is pitch perfect with default settings. If for some reason the settings optimizer does not apply the right FOV, you can disable it (Direct VR page in the menu) and instead adjust the FOV manually in the game’s ini:
C:\Users\[User]\AppData\Local\4A Games\Metro 2033\\user.cfg / r_base_fov
C:\Users\[User]\AppData\Local\4A Games\Metro Last Light\\user.cfg / r_base_fovThe FOV value is the vertical FOV. With all vorpX settings at default values, 96 would be the correct value. If it already is at 96, the optimizer worked fine and the FOV is correct for Full VR mode with the default vorpX profile settings.
G3D/Z3D performance: that’s the nature of the beast, as always G3D is the more natural 3D, but costs performance while Z3D doesn’t look as natural but is fast.
I’d also advise against tweaking any graphics settings manually in both games. Provided the optimizer does its work as intended they are auto set to work best with vorpX.
The release blog post and the short video in it answers your questions about the optimizer. Nothing is messed up, settings optimizing is now built into the core app and “just happens” when you start a game with optimizer support. FOV is dynamically adjusted according to the chosen play style, i.e. full VR FOV/resolution is different than the cinema mode FOV/resolution etc.
That is meant for those who prefer things just working. You and all others who like to tweak themselves were not forgotten though, of course. You can disable all auto-configuration either globally in the config app (“Never change any game settings” or on a game per game basis in the vorpX menu (“Direct VR” page).
Two cover cases like this you can get a second key for your second machine. Just keep in mind that both machines have to be yours, you cannot share a license.
Good to know, that might already be the problem.
I can’t check ATM, but if that file is not there, you haven’t played a game yet where vorpX changed any settings and there is nothing to restore. So this might just be a – rather stupid – bug where the config app tries to open a non-existent ini and can’t handle that.
For you that would mean that you can ignore the crash and that it would go away as soon as you played a game where vorpX actually changed settings.
Almost certainly a false virus scanner detection. Please try to disable your visrus scanner and see whether that helps.
From the Oculus SDK:
/// LibOVRRT symbol resolution failure.
ovrError_LibSymbols = -3023,I’m not entirely sure what that means either. If you are using the Rift Core 2.0 beta, please try going back to the latest official release.
Everyone with the “Restore Game Settings” crash: it would be great if you could post the content of a certain ini-file here. That would be a huge help for trying to reproduce the issue.
1. Go to your C:\ProgramData\Animation Labs\vorpX folder
2. Open settingsbackup.ini with a text editior and post its content hereTo see the ProgramData folder “Show Hidden Files” has to be enabled in Windows Explorer.
Until the Rift Core 2.0 is out of beta official recommendation in such a case is going to back to the latest non-beta Oculus software.
The config app issue is almost certainly unrelated to your hooking problem. It doesn’t have to be running for vorpX to hook into games.
You can also report the issue as false positive to MS.
https://www.microsoft.com/en-us/wdsi/filesubmission
Until they fix it, excluding the vorpX program folder is the right thing to do.
I can assure that the latest release did not introduce any stutter or zooming for Skyrim, it’s still one of the regularly checked games.
Please try to exclude the vorpX program folder from your virus scanner, sounds a lot like a false AV scanner detection. Unfortunately that happens on a regular basis with new vorpX versions for various scanners. Apparently this time even Windows Defender, which usually doesn’t cause trouble.