Forum Replies Created
-
Posts
-
It is possible, but not as easy and BT400 has nothing to do with it. Save your money!
Read here: https://www.driver4vr.com/forums/topic/2-gear-vr-controllers-w10/#post-15774
BTW, and also important for your money: everyone here is blaming the CSR8510 5 EUR BLE dongle from eBay and recommending the 15 EUR Asus BT-400. They are no different in this case, and I had absolutely no problem with the CSR even from 3 meters away. BTW I discovered this issue above while installing the CSR Harmony stack that recognizes and pairs both GearVR controllers with no issue, but Driver4VR cannot interact with that stack, just with Windows Bluetooth stack. Maybe Greg can help us save money by also integrating with it, and then you don’t need to start from 1809 up.
Hi guys,
I have a solution here, but this demands patience.The problem is from Microsoft and basically from the BLE patch they introduced by fixing the CVE-2019-2102 vulnerability in 1903. The same vulnerability used to impact PSMoveService as well, but reportedly was patched by the developer somehow. Against all odds, I did not manage to also pair 2 PS3 Move controllers to a 2004 Windows 10 (although reportedly fixed).
Coming back to the GearVR controllers, the message you will get in the System Event log would be: “The device (device MAC) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information.” Perhaps Greg cannot solve it unless writing a BLE stack patch or to deactivate .
Basically, what I have done to have 2 Gear VR controllers in Win10 2004 is install 1809, pair all devices, then upgrade to 2004. I know, it sucks, but it works. Of course, when accidentally one of them is unpaired, I will have to reinstall everything. Once again, this happens only during pairing. It was a dick move by MS, but it is as it is.
Same applies to almost any BLE device pair like cheap VRBoxes. What I will be experimenting these days is for example GearVR + Daydream controller. But I think safest is to just go to PS Move controllers, if they are the same price.
IMHO the 6DOF hand tracking of GearVR + Kinect360 is horrible, especially when you have games where wrist moves are important (swords or boxing like Creed). I think PS Move controllers are better.
Look for my answer in this topic: https://www.driver4vr.com/forums/topic/2-gear-vr-controllers-w10/
I wrote to the developer also, it seems like he’s in vacation since no answers.
So, welcome to the paid community support 🙂
I discovered that the problem was coming from AMD Relive VR for native h.265 encoding.
I tried Vridge and ALVR, ALVR was giving so far the only results close to AMD since (reportedly) using AMD hardware codecs. Vridge gave for me pixelated images, huge lags and artefacts. Perhaps my Galaxy S6 is too old for its codecs.
So what I use now: ALVR, Kinect360 placed at least 3 meters away (there is a lens kit on ebay that can make it be used closer), ALVR, the 5 USD “VR controllers” on ebay mapped on Driver4VR. You need this especially for calibrating the play area aka “Chaperone” via one of the buttons, since it seems to be randomly allocated. For tuning SteamVR, try also to get ‘OpenVR Advanced Settings’ free app.
So far I played Beat Saber (works reasonably) and Creed (Kinect 360 cannot follow wrists so well so I think I need 2 PS Move controllers). I will keep searching for guides on that.
Biggest problem by far is the phone overheat in max 10 minutes and also lens fogging. Still looking for solutions.