Quest Pro controllers constantly fail to track
my Quest Pro controllers just will not track reliably, theyll be backwards and upside down more often than not, and trying to turn them off and back on again doesnt even work because they either go right back to just being as useless as before, or they just wont turn back on again. At this point my Quest Pro may as well be a paper weight it useless
Quest Pro Controller Connection Issue (Quest 3)
Hello. I have owned Quest Pro controllers for several months now with my Quest 3 and have experienced minor issues having to do with connection and tracking. I have been able to solve those issues fairly easily. However, I am now experiencing an issue that I haven't found a solution for after much research. My quest pro controllers are fully charged and turn on just fine. I am able to connect them to my headset, but they don't turn on past that. The meta horizon app shows them as connected, but in my headset neither controllers are on and functional. I have restarted the controllers, headset, and even went as far as factory resetting the controllers, where I had to use my old quest 3 controllers in order to set up the headset (because the pros still have the issue). I have been looking online for people with similar issues and it seems like none of them can figure it out themselves which makes me regret buying these controllers in the first place. Does anyone know how to reach a solution to this issue?
When I Use the 【GetDevicesType】 Blueprint in Unreal Engine 5.2.1, I got a mistake
I want to get the device type of my Meta Quest In Unreal Engine, I found the doc to use "Get Device Type" node. But I got the "Oculus Quest 2" Output in Quest3 and Quest pro. So How Can I get the correct device Type. MetaXR Plugin 57.0
v63 - The wireless ADB debugging prompt shows a black screen.
Hi, Two tickets were opened here : https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-The-wireless-debugging-prompt-does-not-appear-and-shows/m-p/1171644 and here https://communityforums.atmeta.com/t5/Get-Help/PTC-v62-The-USB-debugging-prompt-does-not-appear-when-the/m-p/1171979 But I was asked to post this here. To resume : On Q2, Qpro and Q3 (v62, v63) when the authorize WiFi debugging through adb prompt shows up, the Quest will first enter a black screen state. Then, we must click the home button on the right controller to make this window show. If I do not click the home button, it will remain in a black screen state. USB debugging prompt had same problem on v62 but it has been fixed on v63 thank to the new look/UI of the prompt. But the wireless debugging prompt have not been updated and still run into this problem. To fix the problem, Meta developers should update the wireless debugging prompt to the new look/UI.
