Forum Replies Created
-
Posts
-
Sound like a hooking conflict with something alse on your PC that also hooks into games.
If you haven’t done so already, please first try the trouble shooting options that pop up in vorpX’s ‘Attaching To…’ dialog after a minute. The first one (‘Install hook helper’) can often help to resolve hooking issues without having to get to the bottom of the matter.
If that doesn’t help, you have to dig deeper. The pinned trouble shooting post on top of this sub-forum has more details on the matter.
I’ll add aptly named SBS 3D base profiles for the next update (at least if I don’t forget it again…). Currently you can use the MPC-HC (DX9), VLC (DX11) and Shadow of the Tomb Raider (also DX11) profiles as a base. Unfortunately no DX12 SBS profile currently, but that’s not a technical problem, there just happens to be none ATM.
Important caveat: whether or not that works together with another 3D-injector is hit and miss though.
BTW: The other Z3D method doesn’t work better, it just let’s you crank up the 3D so high that it converts half the image into one giant Z3D-typical glitch in the end. ;)
Try a ‘SAFE MODE’ restart of the game and also try to run it windowed. Trying a few times should get you in the game usually.
I also get this here occasionally and am 99% sure that its related to the RockStar overlay fighting with vorpX. When the issue occurs, it alway occurs shortly after the R* start message pops up in the upper right corner of the game window. I have yet to find an entirely reliable solution for this conflict, unfortunately the game refuses to launch when the R* overlay gets removed.
Hooking issues almost always are caused by a conflict with some other program also hooking into games. I understand that you already disabled Afterburner, but there probably is something else if disabling that didn’t help.
If you haven’t done so already, please first try the trouble shooting options that pop up in vorpX’s ‘Attaching To…’ dialog after a minute. The first one (‘Install hook helper’) can often help to resolve hooking issues without having to get to the bottom of the matter.
If that doesn’t help, try to disable everything you have running in the background, really everything. Basically any program that can show overlays in games can potentially cause a problem. Even chat apps like e.g. Discord.
Also check whether maybe switching between the different VR APIs in the vorpX config app helps. Your Quest should work with all three of them (Oculus, OpenXR and SteamVR)
@ DaveSt: You ONLY need SteamVR for WMR headsets when you are using vorpX in SteamVR mode. WMR has native OpenXR support, so when WMR is set as your OpenXR runtime and you have selected OpenXR in the vorpX config app, there is no need to run SteamVR at all.
This confusion is pretty much Valve’s fault, since they try to force SteamVR as OpenXR runtime even for headsets with native OpenXR. Just speculation, but if I had to guess, I’d say that probably was a business decision, so that everyone always gets to see the Steam store in their headset. Somewhat understandable to a degree from their perspective, but annoying as hell for sure.
Probably someone used a profile as a base to create their user profile for the game that just displays this warning. If G3D doesn’t work, it doesn’t work. Unfortunately quite a few user profiles have been uploaded to the cloud where the creator pretty much just copied an existing profile ans then uploaded it without really ensuring that everything works.
Just in case: make sure to close SteamVR when WMR is set as OpenXR runtime. It’s not required at all with WMR’s native OpenXR.
Normally the Mixed Reality app should ask whether you want to set WMR as your default OpenXR runtime when you launch it. Similarly to how SteamVR handles that.
Wishful thinking, but Valve should really just stop trying to force SteamVR as OpenXR runtime for headsets with native OpenXR runtimes. Totally confusing for any normal person.
Probably one of your mods that causes another conflict. Please try an unmodded game first and if that works add your mods back in batches to find the offending one. Quest mods, textures, model replacements and similar things are probably safe, but anything that hooks into the graphics pipeline or the game code may potentially cause trouble. Hottest candidates are graphics enhancement and camera mods.
Don’t set SteamVR as OpenXR runtime for a WMR headset! That’s pretty much pointless, OpenXR calls are just converted to SteamVR that way and then send through the WMR SteamVR plugin to the headset.
Use the native WMR OpenXR runtime instead, SteamVR doesn’t have to be running at all anymore with a WMR headset unless you encounter an issue with native WMR OpenXR.
If yopu have trouble running a game with OpenXR, please switch to SteamVR in the vorpX config app on the ‘General’ page.
Please follow the suggestion in the message and check whether your issue still occurs when you remove the d3d11.dll. It almost certainly hooks into the same D3D functions as vorpX and may cause a conflict by doing so.
Not sure how that would affect vorpX in any way, but if you can resolve the issue by disabling SAM, please leave it off. I’ll check later whether I can replicate the issue. Thanks for the heads-up!