Forum Replies Created
-
Posts
-
The menu appears to stutter at 45fps when you move your head because it is fixed to your view. If that is an issue for you, switch to EdgePeek mode while using menus (mouse wheel or right thumbstick click). In EdgePeek mode vorpX temporarily switches to a screen view, which is more comfortable for using menus, watching cutscenes etc. anyway.
During the actual game the headset/camera rotation gets interpolated either by vorpX or SteamVR during the 45>90fps conversion.
If you haven’t done that already, please first try setting the game’s graphics details to low or medium like suggested by the hint shown in the top left corner of the game window. 45fps are perfectly fine though, in that case every other frame gets interpolated either by vorpX or SteamVR, so the headset still displays 90 in the end.
The important resolution with a high impact on performance is the resolution the game runs with, not the SteamVR resolution. SteamVR resolution and game resolution are not the same thing with vorpX. It handles the SteamVR resolution on its own, you don’t have to care about that.
BTW: Currently getting more than 45fps with a WMR headset would require steady 90fps since with SteamVR WMR headsets can’t really handle uneven framerate ratios. Hence vorpX caps the framerate to 45fps unless it’s sure that full 90fps are possible. That will change shortly with the next vorpX version, which gets rid of SteamVR for WMR headsets by supporting the OpenXR VR runtime.
No, obviously better if you can add all of them, but if some fail things will still work. vorpX just won’t be able to select the ones you couldn’t add.
The nVidia driver does a test normally when you add resolutions. Do not add any resolutions where the test fails. Its purpose is to check whether the resolution in question works on your hardware or not. If the test fails, the resolution does not work.
If you happen to have a monitor that supports refresh rates higher than 60Hz, try to add custom resolutions with 60Hz in case they fail with higher refresh rates.
Heavily invasive anticheat software like BattleEye etc. usually prevents vorpX from hooking at all. Games with more lightweight approaches may technically work, but whether or not that potentially violates a game’s license agreement, only the game dev can tell you.
That said, e.g. various Battlefield games, Elder Scrolls Online, Fallout 76, World of Warcraft and other games have been played by users for years. I can’t guarantee anything though.
No, it didn’t. The game is tested very regularly, also 21.1.1 is out since three month and your report is the first one suggesting this.
Please try to reset the profile to default in the config app and check whether you maybe have made other changes to your system that might have caused your issue.
vorpX launches SteamVR automatically if it’s not running when it intializes the headset. Since HL2 for whatever reason activates the SteamVR runtime if SteamVR is running on launch, the only way to play the game with SteamVR is letting vorpX launch it, which should work just fine normally.
If vorpX can’t hook the game, there probably is a conflict with some other program on your PC that also hooks into games. If you happen to use anything else than Windows Defender, your AV program should be your first suspect. If in doubt switch to Defender by uninstalling invasive third party AV programs. Windows Defender will kick in automatically, so there is no ridk involved.
If you already use Windows Defender, there might be some other conflict. The pinned trouble shooting guide on top of this sub-forum has more details on the matter.
Did you by any chance disable automatic settings? vorpX makes some changes to the game’s config file. Without these changes the game renders only in one eye.
Maybe you mean something else than what I had in mind. The only other thing I can recommend is downloading the “Mass Effect: Andromenda [vorpX]” cloud profile in case you didn’t do that already. The profile that currently is included with vorpX has some shadow issues which have been fixed in the cloud profile.
Apart from that there isn’t really anything I can recommend besides switching to Z3D.
The lighting method the game uses can’t be 100% stereoized properly, hence there are some minor blocky artifacts around charcters. Please leave the 3D-Strength at the recommended default value of 1.0. The glitch is barely noticable unless you crank up the 3D-Strength value.
The profile is made for DX11, it doesn’t handle DX12. I can’t really say anything in regard to the benchmark. Never tried that.
Can’t really give any clear recommendation in that regard that would be right for everyone. If you can afford a slightly higher encoding res performance wise, it certainly can’t hurt. May cause judder or other ill side effects though if you overdo it, so be careful.
You can restore any settings changes vorpX may have applied in the config app under ‘Restore Game Settings’. Whenever vorpX changes settings for a game it shows a notification stating that in the headset as well in the top left corner of the game window.
Under normal circumstances vorpX automatically sets the right rendering API for the game. I understand that you like to have full control over your settings, but in case you encounter any issues that you suspect you shouldnât encounter, please as the very first thing always try to let vorpX do what it is supposed to do. Will save you a lot of hassle, the auto settings feature exists to make your life easier by setting things up like they are supposed to be set up.
In general: profiles usually are optimized for/work only with a specific API in games that support multiple APIs. There is no real point in trying other APIs than the one vorpX selects automatically or recommends as best in such a case.
No idea about the benchmark, sorry.