Forum Replies Created
-
Posts
-
I don’t own a Quest 2 but it sounds like you don’t have your client set to SteamVR in the vorpx config app. VD is the only component capable of streaming; there is no such a thing as a Vorpx stream. The output from Vorpx to SteamVR will captured by VD and sent to your headset.
At least that’s my understanding of how it works, not being a Quest 2 owner.
Well, despite what is says on Steam, the game is dx11 and works with existing UE4 profiles, including the split screen feature. If you want G3D the Conarium profile may be a good starting point, but it has some shadow issues. I may put together a profile at some point, but no guarantees – I usually prefer Z3D mode anyway.
There are two versions of Quake 3, not counting the gazillion modified versions out there. One uses opengl and the other, I believe, is IdTech3. I think the profile is for the opengl version but I could be wrong, hence my question.
Anyway, glad you got it working.
I couldn’t get it to work with rdr2 or any of the profiles, including the one checked in by Paradise Decay. I have the GOG version whereas Paradise Decay has the Epic Store version. Not sure if that’s the difference but I just get a black screen in the headset and on the monitor. I know the games running because I can hear the audio.
What led you to believe that the quake 3 profile would work? I’m pretty sure that’s an opengl profile, but the game’s website says it uses dx11.
I don’t have a Quest2 so I can’t comment on that, but Rift-S is selling for $300 right now (while supplies last since it has been discontinued). Might be a good time to pick up one.
Steam says it requires direct12 so you only have four profiles to choose from. Don’t know what the split screen feature is exactly but it doesn’t sound like it would work.
That error indicates a problem with your gpu and/or its drivers. You need to update them, stop overclocking, turn off GSync, turn off FPS limits, remove reshade, or whatever else is necessary to fix your gpu.
I think the only supported game that uses that engine is Prey. CryEngineV is too broad a classification though – it could mean opengl, directx 11, 12, or vulkan. Vulkan doesn’t count since vorpx doesn’t support it, but vorpx profiles have to be specific to the graphics api, not the game engine.
I stand corrected. I don’t know what that sbs stuff in the profile notes is all about, but I assigned the profile to a random game and can see from the vorpx log that it’s trying to hook dx12, so I guess it probably works.
“No dispone de 3DGeometrico.”
As far as I can tell, the profile expects an sbs source, so unless gears 5 can do
that natively, the profile is flat.Very much like the legnaVR “detroit become human” profile – a vulkan game not compatible with vorpx – don’t know the purpose of those profiles, other than to confuse people.
I’ve been playing through it again – absolutely fantastic game for 3D. I have to take frequent breaks in the tombs and crypts because the climbing makes me dizzy as hell – I know I ain’t gonna fall but it sure feels like I am.
Got a decent performance boost from disabling SMT – game was optimized for intel/amd or so I’ve heard, but I’m running on ryzen/nvidia. I really wish the profile allowed dx12 because it runs substantially faster on my system.
Anyway the game supports sbs natively so vorpx is just a viewer and headtracking add-on for the most part. Thank the game devs.
I don’t know how you managed to get hitman3 running because it crashes on startup for me, regardless of which client I use, and I’ve tried them all, including the generic 3d display, as well as all of the dx12 profiles. The vorpx log indicates a failure in directML command queuing when I use the rdr2 profile.
Nothing in your “essential” guide about that I think, but it was tld watch.