Forum Replies Created
-
Posts
-
Seems to work again for me in a brief test. I don’t recall to have done anything about it, so I guess Oculus, nVidia or whoever might have been responsible has fixed the underlying problem in the meantime.
20/02/14
vorpX 20.1.1.2 has been released.vorpX 20.1.1.2 much faster than expected restores the ability to play the Steam version of Red Dead Redemption II with vorpX that was an unfortunate victim of yesterday’s fix addressing the general incompatibility with the latest Steam release. All back to normal.
Did you read the post linked above? Yesterday’s hotfix does not help since it reverts a change from a few weeks ago that made the Steam version of RDR2 work in the first place. Was necessary since without doing that the latest Steam version could get caught in an infinite update loop.
Help is on its way though. Much faster than expected I found a way to make the Steam version of the game work again without the earlier method to block the Steam overlay. A fix will be released either later today or tomorrow. Caveat: if you use an Oculus headset, you will have to switch vorpX to SteamVR mode for RDR2/Steam. Apart from that little inconvenience all will be back to normal in less than 24hrs.
Steam version I guess? Check the release notes for yesterday’s hotfix.
If you want/need someone to blame, the correct addressee is located in Bellevue, WS, United States, which incidentally is the location of Valve’s HQ. ;)
20/02/13
vorpX 20.1.1.1 has been released.This is just a band aid for an issue introduced by today’s Steam release, which could get stuck in an infinite update loop when launching any game with vorpX running. Apparently Steam now dislikes the recently introduced more rigorous overlay blocking.
No other changes.
The hotfix disables the rigorous overlay blocking, basically going back to how things were before vorpX 20.1.0. Unfortunately doing so doesn’t come without side effects, most prominently it prevents vorpX from hooking the Steam version of Red Dead Redemption II again for now, which was the main reason for the new blocking method in the first place.
A new solution for the Red Dead Redemption II overlay conflict that works with the latest Steam version will be looked into. At this point I can’t promise anything though. For the time being your best option is to get Red Dead Redemption II directly from Rockstar.
@ forlaunchcast: That’s an issue with the most recent Steam version that was released today. They might not have liked how vorpX disables the Steam-Overlay since the last version.
I’ll release a hotfix ASAP, for now please uncheck the ‘Try to block kwown game overlays’ checlbox in the vorpX config app. That should mitigate the issue.
Unless your AV software/firewall blocks vorpX from accessing the internet you should receive updates automatically. If that doesn’t work for some reason, you can always use your web installer to fetch the latest version. If you didn’t keep it, you just have to request a new one once.
Might make most sense to check your firewall/AV settings though to ensure auto updates work as intended.
Quest works fine either wired via Oculus Link with any decent USB 3 cable or wireless with an additional streaming app.
My personal recommendation would be doing it via Oculus link as that has less latency, but if you prefer to stay wireless, you can do so if you want.
It has its own profile, should work well enough already without the changes I made over the last days.
You can just launch the game without having to care about anything except for a game restart when vorpX prompts you to do so after the resolution has been adjusted. As always with games that have DirectVR resolution support, you can select a preferred quality on the DirectVr page of the vorpX menu.
The improvements affect any OpenGL game, but I haven’t tried an Unreal engine title with the changes yet. IIRC the original Unreal was already working at some point, but I’m not 100% sure.
BTW: The OpenGL support is more of a personal pet project than anything else. It is still limited to fairly old (‘fixed function’) OpenGL games. I’m two or three steps closer now to a point where tackling G3D for newer, shader based OpenGL might make sense, but that may or may not happen, so don’t hold your breath. There are always more important things…
Please send an e-mail to the register mail address shown in the license dialog or use the contact form under support if sending an e-mail does not work for some reason.
The forum is not the right place for this. Thanks.
Two more good old ID3 games I can fully recommend are Return to Castle Wolfenstein (from 2001, available on Steam/GoG) and Star Trek Voyager Elite Force (not purchasable anymore I think, but worth it if you happen to have an old CD version). Both have full DirecVR support.
BTW: I incidentally spent the last few days adding some (semi-minor) improvements to the OpenGL path after not touching it at all for a long time. You probably noticed the odd graphical glitches in the Quake III menu screen, most prominently the Q3 logo only showing in one eye. Annoying stuff like that will be gone with the next vorpX version, at least for the most part. Also ID3 and other OpenGL games won’t crash anymore when you change their resolution with vorpX active.
There is a ‘Generic 3D Display’ device since vorpX 20.1.0 that outputs a side by side image to ease your life in that regard. The next build will address a few remaining issues, most importantly OpenGL not working yet. Be aware though that the ‘Generic 3D Display’ mode is not officially supported. vorpX is built for VR, consider SBS an unsupported freebie.