slughead

Don’t use the options in DCS. You just use HTCC and it will emulate a mouse. Take a look at the HTCC wiki again.

They issue it in phases. You’ll get it sooner or later.

On its own no. You’ll need something else to track the hands. This only emulates mouse button clicks. Leapmotion make a device that can track hands.

You should be able to do it manually. I have been able to adjust mine by following the instructions.

That's correct. DCS2TARGET will give you the other lights, e.g. gear. However, it does not control the brightness of the Viper lights as the ability to control them via TARGET is not supported by Thrustmaster at this time.

So you will also understand that it isn't always possible or appropriate to divert team members from other activities to generate patches. Regardless, this question was not directed to you.

I was referring to a hot fix availability.

I guess you don't work in the software industry.

2 weeks.

It’s not enough to rename the folders. You have to create two files to replace the folders you renamed. This blocks the oculus updater from using the staging folders as they’re now files.

Look through your dcs.log. There’s probably a clue in there about which vr api it’s using.

And you are not going through Steam?

You could have it aswell though. n+1 rule

If it has it rolled back automatically then you’re now on the general release and stuck. Switch over to SteamVR while you wait for the fix from ED.

Cool. I have the battery life-time up to over 18 hours. It’s likely to last longer but for sure that’s plenty! I haven’t been able to get the device to read the battery voltage despite going by the book on this. There’s a few discussions on the web that indicate that seeed have used the wrong pin to read the voltage of the battery. So the I currently can’t send the predicted battery status indication over Bluetooth. I’ve modified the design to use a 5-way hat switch and created a cookie hat for it. Next I’m going to try to create a cover for the board which for me won’t be easy as I’ve only just started to learn 3D CAD modelling.

I suspect the restore missed one or more files.

mbucchia put a fix in for this in his QVFR. So that may explain why it doesn't happen all of the time for you. When it does fail, that may be some other fault. And to be sure, his fix was not to rectify a fault in QVFR but how DCS should handle a particular OpenXR message. This is something that ED should do. It's only a couple of lines of code an easily found by reading through the git revision history on his git repository.

Personally, I found a wired connection to be superior to VD. As far as cost goes, people will already have a wired connection so that cost isn't relevant to this issue. However, people shouldn't have to pay out to use a workaround.... and they don't, they can use Steam in the interim. But if they have already got VD, they could use that. Regarding the popularity of Meta headsets, I have to disagree. They have almost 50% market share globally. I wouldn't say that PCVR isn't important to them either. It's one part of the VR ecosystem. MSFS is a PCVR app, and so is everything via Steam. That's a big sector to dismiss. On that note.... does anyone know if MSFS suffering from this change from Meta? null He means that the app, Virtual Desktop, is a wifi only app.

If you have kept up... you'll know that I reported this issue in the first place. So, yeah, I am affected by it, however I have mitigated it. Now I get that many were completely unaware of this, that's why I drew it to ED's attention as soon as it happened as I was on the Meta PTC build. So I am disappointed as you that ED hasn't released a patch already. After all, Steam patched their end very swiftly but then again, Steam have a much bigger user base than ED has to be concerned about. Like it or not, we are operating in a world (VR) that is constantly evolving. HP dropping out of the market, MS dropping support for WMR, and new headset vendors appearing. The technology is evolving all the time and rapidly. If we want to be in it, this is how it is, unfortunately.

You mean "may" not "will". And again only for some, not all Oculus users. Many use VD or Steam only, so it won't affect them. If people are mad enough to wipe their entire systems and reinstall Windows and DCS over this then perhaps they need to rethink their processes... i.e. look around the internet first to see if others are having the problem and what solutions are available. I provided a solution as soon as I reported it when it first happened at the end of February and this site is not hidden from Google searches. This is trivialising the issue. ED have already stated they have a fix. The question is whether they have the resources to place just that fix into a patch or whether it is cost-effective for them to release it together with their next planned build and issue an interim workaround (which they/the community have). Neither of which any of us are privy to and so I have no intention of discussing it as it is pure conjecture (i.e. pointless effort). I say trivialising because we have no idea whether this is a simple fix, or whether a whole new API and library has had to be integrated and therefore we have no idea how much testing they need to do before they can consider releasing it. Not to mention prioritising the testing over other features that are being integrated into the next build from various third parties as well as themselves.

However, Virtual Desktop is not free. So if you haven’t got it already, this change from Meta has come at a cost if you go down this route. Plus it only works on wifi and you need a good fast connection to your router for it to be any good. I’m lucky that I can use my PC wifi as a hotspot (although I am sticking to v62 and cabled). I think people are over reacting a tad here though. To say DCS is “dead” for oculus users is somewhat hysterical. You can use steam with a cable for free. Sure it isn’t ideal, and if, like me, you use various OpenXR layers adding such as HTCC, OpenKneeboard, etc, you will lose those temporarily. But that’s why it’s called a workaround. ED has already said that they have a fix, so you can be reassured that it will be in the next build. Keep calm and carry on flying.

Nothing to do with those tools. Meta made a change, ED has to make a change to be compatible.

There are some instructions further back to show you how to block any updates to the Oculus Link app.

Settings > General > scroll to bottom

No, it can’t be fixed like that. mbucchia has already showed how it can be fixed… in code. It’s how a particular OpenXR message from Oculus needs to be handled.