Forum Replies Created
-
Posts
-
When you see the message vorpX was able to hook into the game, but I can’t really say much ybout these games. There is no guarantee that vorpX can hook into any game.
You could check whether this is a general issue by trying games from the ‘Local Profiles’ list in the config app. Those are known to work and come with a preloaded profile.
Not 100% sure, but I don’t think that is possible. As far as I’m aware the nVidia driver applies these filters in the driver. vorpX grabs the game image before it reaches the graphics driver.
I’ll take a look at that before the next update. For the time being I just have a potential workaround unfortunately:
With the ‘Play Style’ option set to ‘Cinema’ you can choose a manual aspect ratio for the screen under ‘More Cinema Settings’. That might help with the squished image, but probably won’t with the cursor problem unfortunately. Worth a shot though. For your display res you would have to set the ‘Screen Aspect Ratio’ to 16:9 instead of Auto.
‘Cinema’ mode can be set up to look pretty similar to immersive mode by changing the Scene to Ambience or None.
First please try to reset the graphics settings to default in the game options.
Also try the recently added OpenXR headset type in the config app. Will also work with Oculus headsets after making Oculus your OpenXR runtime in the Oculus PC app (Settings > General > OpenXR-runtime)
If that does not help, there probably is another program on your PC that also hooking into the game, causing a conflict. E.g. some GPU tool, streaming app, FPS counter, chat app. etc. The best way to trouble shoot that is disabling everything you have running in the backround.
The trouble shooting guide on top of this sub forum has more details on the matter.
Currently the only way to do that is disablig the dedicated RDR2 mod portion entirely, which will also disable the DirectVR Geometry 3D and all other extra features the mod provides. I’ll make the mod part honor the sensitivity for the next release. That was an oversight.
If you want to disable the mod entirely browse to the vorpX program folder (C:\Program Files (x86)\Animation Labs\vorpX) and in the Plugins folder rename vpxRDR2.dll e.g. to vpxRDR2.dll.off
You can just run the latest installer, it overwrites any previous install.
Just in case: the motion controller steering isn’t released yet. Will come Friday or Saturday with the next update.
One more reason to use your motion controllers instead of a gamepad: VR controllers as steering wheel and bike handlebar. Coming later this week.
That isn’t the case when the game is running windowed, which vorpX ensures automatically under normal circumstances.
If you still have issues with the aspect ratio after changing bFull Screen to 0 in the custom.ini, try a fresh install without any mods (and without ModOrganizer). Then add your mods back in batches to find the offending one.
Must have been something else that changed with your setup. There have been no changes that affect how sync works, just the gameplay related changes (and the fixed notification) mentioned above.
Doesn’t really make much sense for vorpX. Rendering in vorpX is a two step process. First games are rendered at their own resolution, then in a second step the game image is processed and sent to the headset. Any VR replacement DLL would only affect the second step, which isn‘t really much of a concern performance wise anyway.
Looks interesting, but always keep in mind that vorpX already has FSR upscaling built into its pipeline. None of these algorithms, AI or not, is some kind of magic that (figuratively speaking) can create a poster out of a stamp by stacking multiple upscale layers on top of each other.
Thanks for the feedback!
There will be one more change to how ADS is handled in a day or two. That will address the occasional camera yaw difference between non-ADS and ADS caused by the decoupled look/walk. If I understood you correctly earlier, that should make ADS completely work like you’d like it to work for run and gun gameplay.
Got that, just thought you wanted to change the setting to 1. I‘ll consider the falloutcustom.ini in the future when applying the automatic setting.
If you encounter something similar again in the future with a modded game, best try with a clean install. Impossible to always consider every undocumented thing like this custom.ini.