Bluetooth VR controllers not talking to software - need workaround for USB adapter?

So I’ve got a very specific problem going on, but it’s apparently one that a lot of users are having.

Basically, there’s this project to help get VR devices running under Linux, right? But apparently, a lot of people with WMR headsets are having trouble getting their controllers to work, even though they’re connected to Bluetooth. Last night, I helped confirm that the software doesn’t even realize the controllers are connected.

According to another user, this appears to be an issue with Arch-based distros using Bluetooth via a USB adapter. Something about the controllers showing up as virtual devices, and getting orphaned because they return a wrong number to a function call or two.

I’m tech savvy enough to know roughly what that means, but not how to fix it. :sweat_smile: I hear there’s a workaround, but searches such as “arch app can’t detect connected bluetooth device” and “arch app doesn’t talk to bluetooth device” and “arch bluetooth device orphaned” are mostly pulling up posts about devices not showing up in the pairing menu - nothing relevant.

Anyone have any idea how to tackle this? A LOT of VR users will appreciate if something working can be found. :sweat_smile:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.