Oculus attempt with Pimax?

[DJSlane]

I tried the PerfKit with the only two games I own that use Oculus runtime, Lone Echo 1 and 2, but it doesn't seem to work (at least the hotkeys don't). I'm still learning about github and have very basic programming skills. Looking at the build I didn't see how it ties in exactly to the Oculus runtime.

[fholger]

Lone Echo 2 uses D3D12, which is not currently supported. Lone Echo 1, however, works fine for me, including hotkeys. Please post your vrperfkit.log file.

[DJSlane]

vrperfkit.log at least I can't get it to show me the debug overlay. The effect itself can be so subtle, am I installing it correctly?

!

[fholger]

Hm, it's loading, but it is not detecting any of the VR APIs. Are you using Virtual Desktop, per chance? If so, can you try a Link variant? It might be that VD with Oculus games just doesn't work.

[DJSlane]

No, as I thought about it more , do you think it is because I use Pimax, such that it doesn't hook properly? Also I tried manually setting the runtime is use to Oculus runtime instead of SteamVR runtime and still no benefit.

[fholger]

Yes, that's probably it. Whatever PiTool is doing to get Oculus games running is apparently not compatible.

[fholger]

Most likely PiTool is intercepting the loading of the Oculus client DLL and replacing it with their own version. If you can run the game with debugMode: true in the config file and post the log, there is a chance I can see what the Pimax replacement is called. If I know that, I might just be able to inject that DLL instead and make it work.

[DJSlane]

vrperfkit.log

It just doesn't reveal itself to me. I'm sure it uses OVR server and oculus runttime - if it's not running Pimax comes up and asks to start it.. It also fails to use FPSVR which would indicate use of steamVR, nor does it seem to use Revive. So it's normal to me in terms of Oculus operation, but I have nothing to compare it to as Pimax has always prided themselves on running Oculus "natively". I also tried it both named as dxgi.dll and d3d11.dll

[fholger]

Ah, damn, I removed the relevant log lines because they ended up being a bit too "spammy" even for debug mode. Could you try to rerun this with an older build, e.g. 0.2 or even 0.1? Still with debugMode enabled, it should spew out a pretty large list of DLLs getting loaded in the process.

[DJSlane]

no problem

---

From: Holger Frydrych @.> Sent: Thursday, January 20, 2022 8:53 AM To: fholger/vrperfkit @.> Cc: DJSlane @.>; Author @.> Subject: Re: [fholger/vrperfkit] Lone Echo 1 or 2? (Issue #14)

Ah, damn, I removed the relevant log lines because they ended up being a bit too "spammy" even for debug mode. Could you try to rerun this with an older build, e.g. 0.2 or even 0.1? Still with debugMode enabled, it should spew out a pretty large list of DLLs getting loaded in the process.

— Reply to this email directly, view it on GitHubhttps://github.com/fholger/vrperfkit/issues/14#issuecomment-1017524915, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXLZBGZ7VI3K3JJDAPJX5N3UXAHUXANCNFSM5MJHV7ZA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>

[DJSlane]

Here's Asgard's Wrath, which I just purchased along with 0.1 PerfKit vrperfkit.log

[fholger]

Hm, still no LoadLibrary lines. Maybe it's only the 0.2 release that had them? I'm not sure right now. You'll notice them when they are there.

[DJSlane]

OK here's 0.2 with the lone echo 1 vrperfkit.log

[DJSlane]

and .1.2 with lone echo 1 vrperfkit.log

[fholger]

Ok, sorry, apparently those debug outputs never made it into a build. I'll have to provide you with a custom build later today.

[DJSlane]

no problem will look for it.

[fholger]

Try this build with debugMode on, please: dxgi.zip

[DJSlane]

vrperfkit.log here ya go

[fholger]

Thanks. I'm having to guess here since I can't test it myself, but try this build and see if it does anything: dxgi.zip

[DJSlane]

vrperfkit.log fails, but perhaps this gives insight

[DJSlane]

vrperfkit.log After I sent the first one I realized I had not officially set the runtime to Oculus, perhaps this will give additional insight.

[fholger]

How exactly does it fail? Both logs show that it now hooks successfully and creates the necessary upscaling resources, but then it appears to shut down in part. If the game crashes, I'm afraid that's going to be next to impossible for me to debug without access to Pimax hardware.

[DJSlane]

Let me try with asgards wrath. Funny that the debug "bugsplat" doesn't even fire.

[DJSlane]

For Asgard's Wrath: vrperfkit.log this one does start the game, but doesn't show the debug circle, respond to hotkeys etc.

[fholger]

Ok, yeah, I'm afraid this isn't going to work. Pimax apparently loads multiple versions of its Oculus replacement DLLs, and while with Asgard's Wrath the mod is correctly hooking the latest version, the functions in there are never called. So it's probably using one of the older versions. I can't make this work properly without actually debugging it myself, which is impossible without Pimax hardware. So unfortunately, this is a no fix for me, sorry.

[DJSlane]

No problem. I appreciate the effort and enjoyed the dive! I will contact Pimax. They love to incorporate various features across their software and add it to their launcher. I'll let them consider it.