nilpointer

I notice that per this original post the error still exists in the current version of the manual.

same driver. I've had this happen in the past, though I've never quite pinpointed the catalyst. Oddly enough I had already done a clean install of the same driver but that had no effect. DDU (Display Driver Uninstaller) is a very useful utility for these occasions, however it is a shame such a thing needs to exist.

So for some as yet to be explained reason. I stripped the NVIDIA driver from my machine with DDU in Safe mode and reinstalled...... instant fix

yeah I had a try at disabling OpenXR toolkit at first, then resetting to defaults in safe mode. Neither seem to have worked. I recall blindly running the OpenComposite updater in the last week and possibly had not checked since then, now I'm wondering if this has introduced a problem

Having tried the previous version I still have the same issues. Wondering if this is related to something in the most recent OpenComposite update....

I'm currently rolling back to the previous OB to verify but it seems fishy.

I'm also seeing the same problems. Have been running opencomposite on a 3090 at buttery smooth consistency up until installing the last update... now I'm living in a jagged stuttery hell. I've tried all the usual removals and resets with no success.

LOL boom boom ching

OMFG, as someone who works with git on a daily basis I am utterly and totally ashamed to admit what the problem was...... I was downloading from the wrong branch. I was browsing the master branch on the gitlab repo and the link was obviously old... sure enough I switched to the openxr branch and problem solved. I will now go and hang my head in silent shame.

No change, it does not seem to be related to the ini file in this case unfortunately

I'm not using an opencomposite.ini ... unless there is a default one somewhere

No such luck here unfortunately. I have done a complete removal of all OpenXR related tooling and reinstalled and have the same issue. MSFS kicks into OpenXR instantly with no problems... which was exactly how well DCS was working for me prior to the new global install option I have now tried completely removing OpenXR and reinstalling, completely removing DCS and reinstalling, replacing the local openvr_api.dll instead of the global installer option. In all cases DCS simply starts in flat screen mode as though my headset were not even connected. The instant I switch back to SteamVR it works perfectly again

To be clear, this was working fine when I used open composite locally by replacing the bin folder dlls. Only now having converted to the new system wide mechanism am I seeing this failure to connect to WMR

I can clear the environment and run DCS from the desktop tool in WMR but still no connection made

Also a bit stuck after switching to the global install version with not being able to get WMR to connect to DCS. - Ran a clean and repair - Removed Saved Game Directory - Installed Open Composite globally - Selected runtime and confirmed DCS is listed in the Configuration - Deleted D3DCompiler_47.dll DCS starts in VR mode but there is no headset tracking and my G2 remains in the cliff house. If I switch back to steam it works fine. What am I missing?

Hi Mikhail, If you can/will ship to Australia I would like to add myself to the order list. Many thanks, Tom

Wondering what others are doing to work around detents and finger lifts on throttles (if anything)? I have a Virpil Mongoose CM3 which I have configured for the 18C using the finger lifts and a push through AB detent. Using the Virpil software I have the 0% of the axis starting after the drop off from the IDLE detent for the 18C. This works fine with the AH-64 except I loose a little throw at the base of the throttle where I would otherwise have to lift over the detent. So far it's not caused me a problem but I am wondering what others do?