Forum Replies Created
-
AuthorPosts
-
Nov 13, 2021 at 8:17am in reply to: Combinations of problems preventing my troubleshooting of Deathloop (Z3D) #207272
Ralf
KeymasterThe game’s gamepad mapping is too complex to be replicated with vorpX’s gamepad to mouse/kb mapper. I spent half a day trying, trust me. Hence the according message that is shown when you launch vorpX.
Since the game doesn’t allow gamepad and mouse input simultaneously and the gamepad mapper unfortunately is of no use either in this case, the only way to play it with head tracking is using a mouse. The only viable way for playing with a gamepad is playing in cinema/immersive screen mode without head tracking, which would let you use the gamepad natively.
Nov 13, 2021 at 7:39am in reply to: AMD FSR in ANY VR game . can we get this running with vorpx ? #207271Ralf
KeymasterShort update: after basically overhauling the whole headset syncing over the last 10 days, I think I’ll also make some changes to how you can configure it. Has become way to convoluted over the years for any normal user to understand what actually happens when changing these settings.
Goodbye ‘Headset Sync’, ‘Fluid Sync’, ‘Async Render’… Instead there will be a single overarching setting with four largely self-explanatory presets: ‘Favor FPS’ (typically the current defaults), ‘Favor latency’ (useful for FullVR mode where a low head tracking latency in the end is more important than maximum FPS), ‘Favor judder protection’ (for those who always crank everything up to max no matter what), and ‘Custom’ (for tinkerers who still want to dial in everything themselves). That will make the sync settings much more accessible and useful for a normal person.
If it were for me, I’d rather get rid of this whole set of settings entirely, but since there definitely are scenerios where one might want to prefer either a more FPS oriented or a more latency oriented setup, the presets (plus full configurabilty for those who still want that) look like the best solution.
Ralf
KeymasterSounds like a good thing in general, although the install folder is not the issue as far as vorpX is concerned. Since vorpX normally doesn’t have to install any files to game folders, it already can hook many (probably most) Game Pass games, doesn’t matter if they are installed in the write protected app folders or not.
The problematic ones are games compiled as UWP/Windows Store app, which basically put the executable in some sandbox that shields them from the rest of the system. Luckily the whole UWP model is halfway dead, wasn’t the huge success among developers MS hoped it would be. So with some luck less new releases will use it in the future. Unlikely though that all current UWP games will be converted back to ‘normal’ Windows applications.
Ralf
KeymasterTry to run the game windowed/borderless. That can often help with weird focus issues. If that also doesn’t help, switching from OpenXR to SteamVR (or vice versa) in the vorpX config app might be worth a shot.
Ralf
KeymasterHow odd, never heard of that before or experienced that here on an ultra wide monitor. Just in case: I meant the instructions message in the game window on your monitor.
Anyway, vorpX doesn’t set the resolution automatically in this case, but as always with FullVR games a 4:3 res (e.g. 1920×1440) is what you want.
Whenever vorpX can set the resolution, it displays an according notification in the headset and you have the ‘Resolution Quality’ option on the DirectVR page of the vorpX menu. Otherwise you have to set a res yourself. Rule of thumb: 4:3 for FullVR, 16:9 for immersive screen/cinema.
Ralf
KeymasterPlease check the message in the top/left corner of the game window. It answers both your questions.
Ralf
KeymastervorpX supports DX9-12 and some older OpenGL titles. With an issue like this it might be worth a shot to try another VR runtime. For yor Quest ‘Oculus’ is the preferred mode, but ‘OpenXR’ and ‘SteamVR’ should both work either. You can select the VR runtime in the config app on the ‘General’ page.
Ralf
KeymasterSHouldn’t happen, but whenever you experience an issue like this, running a game windowed or ‘borderless fullscreen’ usually is a good workaround.
Ralf
KeymasterThere is no way to get better FullVR with the preliminary custom profile for F1 2021 than with the newer official profile. See my reply in your other thread.
Ralf
KeymasterUnfortunately the game does not allow to set its camera FOV high enough to still look right without black top/bottom bars in FullVR mode. No way around that.
For the best possible result make sure to follow the instructions in the top left corner of the game window.
Ralf
KeymasterNope, sorry. Using the method described above does the trick though. Caveat: Probably won’t work together with other injectors/mods like Reshade, those (obviously) still can cause conflicts. if you want to do that the desktop viewer is the way to go.
Ralf
KeymasterNo worries, you didn’t upset me in any way. For your own good just read whatever hint vorpX displays in the future. Surprisingly those aren’t just decoration. ;)
Nov 8, 2021 at 5:28pm in reply to: AMD FSR in ANY VR game . can we get this running with vorpx ? #207184 -
AuthorPosts