d0x360

It's reading d3d11.dll or whatever the mod is using to hook direct x and that dll isn't fully compatible.. at least that's often the case. Try renaming the d3dxx.dll in...

If that doesn't work rename the file to kernel32.dll On Thu, Sep 29, 2022, 2:50 AM d0x360 ***@***.***> wrote: > It's reading d3d11.dll or whatever the mod is using to...

11 hours? I posted both of those the same day... That's odd. Hopefully the rename post fixed it for you

Use virtual desktop and it should work. There is 1 more option for oculus users but I forget the name.... It basically just creates a virtual display that's then fed...

That's why I bypass the Oculus runtime by NOT installing oculus home or meta home whatever it's called now and running virtual desktop instead. Then it uses the steam VR...

Or not possible because eac won't whitelist it

Try one of these 2 things... Play the game using the native oculus app called virtual desktop. Then you launch that on the quest and also make sure to install...

> This has already been discused in issue #92 It is not possible to add FSR2 to vrperfkit because FSR2.0 and 2.1 requires motion vectors which the majority of games...

> Go to the way back machine and put the sites URL in it and try to grab it off there if you know about when that version was up....

you sure you're not playing the HD remasters they made from old builds? Funny that they had beta and alpha builds but not the final...should have hired bluepoint. I can...