Ogrescar

[Ogrescar]

I don’t know where you got the idea that vorpx wouldn’t hook the game – it’s a directx9 game, so the odds are very likely that vorpx will hook it. HelixVision and whether it’s displaying in anaglyph on your monitor is irrelevant.

So, if you had assigned a profile from another dx9 game, Dragon’s Dogma for example, to the game’s executable, you’re likely to get at least Z3D, maybe even G3D if you find the right profile. Dragon’s Dogma is just an example – some profiles will work better than others, some will hook but not reconstruct the 3d, some won’t even hook.

[Ogrescar]

Its a DX12 game if I’m not mistaken, so if Horizon Zero Dawn and Death Stranding don’t work, you can try Red Dead Redemption II. I don’t think there are any other DX12 profiles. I’m kind of surprised that the Borderlands 3 profile will hook it.

[Ogrescar]

DX12 games require a hook helper. I believe that I copied one (dxgi.dll) from another game folder (I think it was Horizon Zero Dawn) because vorpx wouldn’t install it.

[Ogrescar]

I said it breaks G3D. I didn’t say it broke Z3D.

[Ogrescar]

Turning on DLSS breaks many, if not all, G3D profiles where such an option exists anyway.

[Ogrescar]

Never mind. I was trying to use a mapped network drive, which doesn’t work; fully qualified names work okay.

[Ogrescar]

It can be done if you really want to, but you’d have to start the headset service – for me that’s the oculus client. Then you would then have to start vorpx because the desktop viewer won’t run without it. Finally, you would have to start the desktop viewer. In between those steps you’d have to insert delays to wait for each of the apps to initialize. If you want to start vorpx as admin you’d have to setup a user account to do so and store the password in the task scheduler or whatever you decide to use.

tldr – It would be a lot of work.

[Ogrescar]

Vorpx resizes your screen resolution to about 2000X2000 depending on the game. You’re going to get diminishing value going beyond that. 4K is around the equivalent of a 2.0 supersampling rate which will kill your performance.

I usually shoot for 2560×1440 – the resolution is good and I can play most G3D games at 40fps. If the game has built-in supersampling, I’ll set it to 1.25 to 1.5 and lower my resolution to 1920×1080.

tldr; lower your resolution to a reasonable level.

[Ogrescar]

According to oculus support I should have plugged my second monitor into the primary gpu before I ran the setup/repair. Multiple monitors attached to multiple gpu’s is not supported.

So it was never a hooking problem and I apologize for taking up your time.

[Ogrescar]

Just fyi, this started happening again shortly after I re-installed the Oculus software (for unrelated reasons), but I realized that it only occurred if I had my headset set to Oculus. If set to SteamVR, Generic HMD, or Generic Display the correct gpu was being used. Interestingly, I only had to toggle it to SteamVR and launch a game one time to fix it – I toggled it back to Rift and it was working okay again.

[Ogrescar]

Just fyi, Shadow of War is not a supported game and the cloud profile is 2D.

[Ogrescar]

The head tracking sensitivity is the base number that the multiplier uses. It is on the head tracking tab, not the main settings tab. You can bump it up and look behind you with a glance if you’re so inclined.

[Ogrescar]

I think you just need to adjust the head tracking sensitivity. No need to edit the profile.

[Ogrescar]

I’ve never tried to play the game with vorpx, but I just tried – it looks pretty flat, and I couldn’t turn off G3D or switch modes without vorpx freezing up. So I’m guessing a game patch may have broken things.

[Ogrescar]

I had to reduce my resolution to a ridiculous level and force anti-aliasing on in nvidia control panel to get to 40 fps with a tolerable image, but I think the game looks much better with Z3D, so that’s the route I’ll be taking.

[Author]

Posts