Forum Replies Created
-
Posts
-
Thanks for the heads-up. I will look into it and if possible fix the issue. As always no promises though.
Regular vorpX licenses are only valid for personal use on your own PC.
If that is not your use case, please contact support |at| vorpx com for commercial licensing options.
There should be default bindings active normally. Might be worth a shot to reset the profile to default in the config app.
You can solve your settings issue the other way around: simply switch to ‘Generic Headset’ or ‘Generic 3D Display’ in the config app temporarily. That way you can make the required changes on your PC without access to the headset.
Uninstalling games does not remove their settings usually.
However, you can restore settings changed by vorpX in the config app on the ‘Restore Game Settings’ page. You should see a message about that in the headset and in the top left corner of the game window whenever vorpX adjusts any game settings.
Some games have the unfortunate habit of checking the desktop res and using that as maximum allowed res instead of evaluating the actually available resolutions. I thought about overriding this a few times already, but such overrides are always a bit dangerous.
Running games windowed if the issue occurs fullscreen (or fullscreen if the issue occurs windowed) *might* also help in such cases.
Can’t really say anything to this currently, but I’ll take a look at rFactor and see whether I can replicate the issue.
Nothing unusual. Just make sure to check any hints that vorpX displays in top left corner of the game window and in the headset. Also – as always – choose a resolution (has to be 4:3 in case of Black Mesa, vorpX warns you if it isn’t) as high as performance allows for the best possible image quality.
Highly recommended to check the “Custom Resolutions” section in the help in this regard. it explains how to add resolution that your PC cannot display normally.
If the FOV is right, it is right. But one other thing you might want to do is raising the game’s resolution for better image quality if you PC is fast enaough.
For Bioshock Infinite you can do that on the DirectVR page of the vorpX menu. Check the “Custom Resolutions” in the vorpX help to take full advantage of this feature. it contains detailed instructions how to add resolutions to your PC that it ccannot display normally.
You can achieve almost the same by using EdgePeek with the added benefit that after leaving EdgePeek the FOV is 100% right again instead of having to guess how many mousewheel notches you need to get back to the correct FOV. The EdgePeek scale can be adjusted in the menu to fit what you have you in mind for your zoomed out size.
Yes, the Image Zoom mousewheel shortcut has been disabled. It was a relic from the very early days of vorpX. Nowadays it mostly caused problems since one could accidentally break a calibrated FullVR FOV way too easy, e.g. when changing weapons with the mousewheel during a hectic firefight.
Please set the FOV slider in the game’s graphics options to max, otherwise vorpX cannot apply the FOV correctly. You should see a message about that in the top left corner of the game window IIRC.
BTW: You might want to change you nickname here on the forum. Using your e-mail address makes it easy for spam bots to grab your mail address. You can edit your profile from the user menu in the top right corner of the page.
Sounds as if vorpX can’t find the depth buffer texture and thus the Z3D algorithm produces garbage. That can be an issue in some Z3D games, but I never heard of it for RDR2.
Please first double check that the game really uses DX12, just in case. If it is, try one of the game’s graphics quality presets. Maybe some unusual graphics option combination makes it difficult for vorpX to figure out the right depth buffer if you customized graphics options manually.
Also reset your GPU driver settings to default if you changed anything in its control panel.
Next reset the profile to default in the vorpX config app and if that doesn’t help do a full factory reset (trouble shooting page).
If that also doesn’t help, please create a trouble shooting data archive in the vorpX config app directly after playing the game and send it to support |at| vorpx com, so I can check whether there is something unusual in your logs/system config. Ideally together whith your RDR2 settings file ([Documents]\Rockstar Games\Red Dead Redemption 2\Settings\system.xml).
OK, thanks for the info, couldn’t really remember. The health bar is probably related, but I’ll check that to be sure. The official profile (ends with ‘[vorpX]’) is the right one.
Should be fixed already in the ‘Monster Hunter World [vorpX]’ profile that you can grab from the cloud. There wasn’t enough time yesterday before releasing the latest vorpX unfortunately, but redefining the Monster Hunter World HUD shaders was the first thing I did this morning.
BTW: Do you remember whether the minimap was scaling correctly before Iceborne? Couldn’t get that 100% right this time.