zildac

No, I have the same setup albeit 10 and 2 o'clock, V2 base stations on tripods and they track perfectly.

As I recall, this was also the case when I had my G2 and ran OpenXRToolkit and OpenComposite. 90-45-30 which was one of the major benefits.

Thankyou!

Agreed, and well put[emoji1303]

Good spot, yup that'll be why [emoji849]

Have you tried a long clean and repair?

What are the extra files you have in the Varjo Base OpenXR directory? Here is mine: null Hmm I copied the string straight from the BN post after the hotfix. TBH as I have my DCS settings to enable VR by default I don't need the first parm anyway. @dburne Oops my cock up...have edited the first post!

Goto tanker

[emoji1303] Good newsy

Fixing the mouse is one of the benefits, yes.

Excellent [emoji1303]

It does work, so I'd suggest a ful /slow repair then try the method outlined in this post :

See here: https://r.tapatalk.com/shareLink/topic?url=/topic/318268-varjo-aero-dcs-native-oxr-oxrtk-and-offset-cockpit-cursor-issues-fixed/&share_tid=318268&share_fid=74365&share_type=t&link_source=app

For those with a Varjo AERO who wish to use DCS native OXR please see here:

No, was just a mate and I on a locally hosted MP server, "real" MP is too scary for me

So, @mbucchiahas worked his magic yet again, and released a wrapper for Varjo Base that effectively stops the advertisement of the headset as supporting QUAD. The upshot of this is that you can now use the new DCS native OXR, OXRTK (if you so wish), and the offset cursor in the cockpit that has plagued us for a long time is fixed. Turbo mode now appears to work if you are running OXRTK 1.2.4 so give it a try and see (YMMV). The wrapper can be found here: https://github.com/mbucchia/OpenXR-InstanceExtensionsWrapper/releases Follow the instructions exactly! And don't forget to start DCS.EXE --force_enable_VR --force_OpenXR and disable OpenComposite if you were using it previously Based on my limited testing, I am actually seeing a 2FPS increase in performance over using Open Composite. And remember, a Varjo Base update will very likely overwrite these changes, so you'll have to redo them, or preferably use a Mod Manager to apply and remove them. Enjoy, and thanks to @mbucchiafor getting this sorted in less than 48 hours!

If you're trying to use OpenComposite then I'd recommend grabbing the latest DLL from here : https://znix.xyz/OpenComposite/download.php?arch=x64&branch=openxr

Sure, PM sent

@BIGNEWY Many thanks.

@BIGNEWY This is good news, but the Varjo Aero issue where the headset is enumerated as being quad display is still present. Is this issue on the backlog for a fix as it breaks OXRTK but furthermore appears to render all 4 displays, even though it only shows two, causing a performance hit and there is still the issue with the misaligned cursor in cockpit.

I've just tried setting SteamVR as the default OpenXR "handler" and I get nothing display wise in my Aero HMD. I'll stick with OC for the time being I think.

No, I understand it's not a "hack", but I'm assuming you lose the ability to use VB to cap at 45FPS for example via Vsync and set PPD?. And Steam VR just always felt clunky to me. I guess I can give it a quick try and see.

Isn't it juat easier and more efficient to use OpenComposite?

Just to update here, the performance drop using native DCS OXR (all other issues aside) versus using the "old" OpenComposite method appears to be the fact that DCS is still recognising the Aero as having four displays, it's rendering all four but displaying only two, therefore more work=less performance.

It appears to be exactly that Exactly as @mbucchiaasked. Cmd line switch or similar