[Unity] Hide or disable hand-tracking logs
Hello, I am seeing thousand of logs like this one in `Android Logcat` window in runtime: 2026-05-05 12:37:37.045 28704 28939 Info InputDevice_Hand HANDTRACKING ADMIRE hand 1: hpm=1 -> shared=0 2026-05-05 12:37:37.045 28704 28939 Info [CT] HandPoseSampler: Filter reset 2026-05-05 12:38:22.126 28704 28939 Info InputDevice_Hand HANDTRACKING ADMIRE hand 1: hpm=1 -> shared=0 2026-05-05 12:38:22.126 28704 28939 Info [CT] HandPoseSampler: Filter reset This appear when using hands and even when using controllers. `Tag Control` can exclude them but then it doesn't show other logs unless I manually add all tags in the list and then deselect these two logs. currently I am using Regex Filter to hide them.
"You can't make this change at the moment" - Noticed using a device you don't usually use
I've been trying to register a Facebook developer account for 2-3 weeks now, waiting 48+ hours in between attempts. I've tried multiple strategies listed online, like adding a payment method, adding 2-factor auth, downloading the business suite, and the ads manager, etc. Im assuming my account is flagged for some sort of security reason. Is there any way to get support from the meta staff with this issue? Im really getting frustrated and have spent countless hours trying to resolve this issue. Please help!
Developer account creation blocked — "device not recognized"
Hi, I've been unable to register as a Facebook Developer for over a week due to this error: "You can't make this change at the moment. This is because we noticed you are using a device you don't usually use." I've been logging in daily from the same device for 7+ days but the restriction hasn't lifted. My account is in good standing and I'm not using a VPN. Could you manually clear this restriction or escalate to the appropriate team? I need access to the Developer portal for a legitimate app project. Thank you. RémyUpdated Meta Horizon Link app to 85.0.0.239.552 and now USB Link breaks within a min or so.
Everything was working fine for months but after updating to 85.0.0.239.552, my USB link is broken. After a min or so, the video craps out. Images below, video attached. This is not while playing games or dev'ing in Unreal or Unity. This is simply connecting my headset and going into PC link via USB-C cable. I simply go into PC link, wait about a min, and it craps out. After this happens, I can exit out of Link. When I disconnect and reconnect the USB cable, the headset registers the connect and pops up the USB debug window. But if I go to Quick Settings, the Link button says no PC is connected. Link functionality is broken. The ONLY way to reset Link is to restart the headset. Then I can go back into PC Link, wait a min or so, and then it craps out again. This has completely stopped all development on my project.Meta Quest AI Stack: What It Actually Means for Unity Developers
Hey everyone, Degly here! I’ve been working with the Meta Quest AI stack for a while now, and I wanted to share a straightforward overview of the real value for Unity developers. There’s a lot of excitement around AI tools in Quest development, but it can be hard to understand how they fit into your workflow. Meta Quest AI Stack: What It Actually Means for Unity Developers AI tooling is showing up everywhere in Quest and Unity development, but a lot of it gets explained in a way that sounds exciting without being very useful. This video is a plain-language overview of the current Meta Quest AI development stack. The goal is not to show a deep coding walkthrough or claim that AI will build your whole app. The goal is simpler: How can these tools reduce friction, speed up iteration, and help Quest developers move through setup, debugging, content changes, and handoff more efficiently? Video / resource link: WHO THIS IS FOR Unity developers building for Meta Quest. XR developers who keep hearing about AI tooling but do not know where to start. Developers who want faster iteration, not AI hype. Anyone who wants a practical mental model before trying MQDH MCP, Unity MCP, AI Building Blocks, or the Immersive Debugger. PRACTICAL TAKEAWAYS A simple explanation of the Quest + Unity AI stack: What MCP means in practical developer terms What MQDH MCP does What the Meta XR Unity MCP Extension is for What AI Building Blocks are Why Agents and Providers matter Where Unity Inference Engine fits Why the Immersive Debugger matters for headset-first debugging The main takeaway: this stack is not one magic tool. It is a practical workflow for reducing friction across the development loop. THE STACK AT A GLANCE The video focuses on four core pieces: MQDH MCP Unity MCP Extension AI Building Blocks Immersive Debugger High-level workflow: MQDH MCP helps you gather Quest development context. Unity MCP Extension helps automate repeated Unity editor tasks. AI Building Blocks help you add practical AI features. Immersive Debugger helps you inspect and validate behavior inside the headset. RELATED LINKS Meta Quest Developer Hub overview: Enable AI tools with MCP for Meta Horizon OS developers: Model Context Protocol introduction: Meta XR Unity MCP Extension docs: Meta XR Unity MCP Extension GitHub repo: AI Building Blocks overview: Agents and Building Blocks: Providers and Inference Types: Unity Inference Engine: Immersive Debugger overview: MR Utility Kit debug and testing: Dilmer Valecillos walkthrough: Meta Quest agentic tools GitHub repo: WHAT TO INCLUDE WHEN ASKING FOR HELP If you try one of these workflows and need help, include: Which part of the stack you are testing Unity version Meta XR SDK version Quest device model Whether the headset is connected and in developer mode Screenshot of the issue Relevant logs or error messages Whether the issue happens in Editor, on device, or both FAQ Should I use all of these tools at once? No. Start with the part that solves the problem you currently have. Is this a replacement for learning Quest development? No. It is a way to reduce friction around the workflow. Is MQDH MCP the same thing as Unity MCP Extension? No. MQDH MCP is more about external Quest context such as docs, logs, screenshots, and device workflows. Unity MCP Extension is more about repeated Unity editor tasks. Are AI Building Blocks only for cloud AI? No. The Agent and Provider model is useful because Providers can represent different inference paths, including cloud, local, or on-device options depending on the feature. Is Immersive Debugger an AI tool? No. It is a runtime debugging tool used inside the headset. It is included here because it helps complete the development loop. BOTTOM LINE This stack is not about AI for the sake of saying AI. It is about tools that help Quest and Unity developers: Move faster Test easier Debug more clearly Keep projects cleaner Reduce repeated setup work Validate behavior inside the headset The practical story is simple: use AI tooling where it reduces friction, and use headset-first debugging where the real XR behavior actually happens. Degly
Exploring Body Tracking via Wi-Fi CSI – A Newbie's Proposal
Hi everyone! I’m new here in the community and I’ve been diving deep into how we can push the boundaries of standalone VR tracking. As a fan of the Quest ecosystem, I’ve been thinking about a challenge we all know: tracking parts of the body that are out of the cameras' line of sight. I’ve been researching Wi-Fi CSI (Channel State Information) and was wondering if we could use the wireless signal already present in the headset to help with body tracking. Since Wi-Fi signals are affected by human movement (even through walls or behind the back), could this data be used to complement the existing IMU and optical tracking? The idea would be to use the CSI amplitude and phase changes as a secondary data layer to "guess" limb positions when the cameras can't see them. I know it’s a technical challenge, but I’d love to hear from more experienced devs here: Does the current Quest hardware allow low-level access to CSI data for this kind of processing? Could this be a viable way to achieve "Full Body Tracking" without external sensors in the future? I'm just starting to develop this concept and would appreciate any feedback or pointers to existing documentation! Best regards, Vinícius (Jurusbango)Proposta: Rastreamento Corporal Total via Wi-Fi
Subject: Proposal: WiFi-based Full Body Tracking using CSI (Channel State Information) Message: Hi Meta Dev Team, I would like to propose a feature that could revolutionize body tracking on Meta Quest headsets without requiring external trackers or extra cameras: WiFi-based Motion Sensing using CSI (Channel State Information). The Concept: Every time a person moves between a WiFi transmitter (router) and a receiver (Quest), the signal undergoes phase and amplitude distortions. By accessing the CSI data from the Quest’s WiFi chipset, we can analyze these signal patterns to identify body posture and movement in real-time. Technical Implementation: Signal Analysis: Utilize the 5GHz/6GHz signal fluctuations to map the user's silhouette and limb positions. Machine Learning Integration: Use a lightweight neural network to translate CSI "shadows" into skeletal data, similar to how researchers have successfully used WiFi for "through-wall" sensing. Hybrid Tracking: Combine this WiFi data with the existing Inside-Out tracking and IMU data to fill in the gaps when the controllers or legs are out of the cameras' field of view. Why this is a game-changer: Zero Cost for the User: No need for Vive trackers or Tundra trackers. Privacy: It doesn't rely on optical images of the room, just radio frequency patterns. Lower Latency: Direct processing of signal data can be extremely fast on modern SOCs. I believe this would make Full Body Tracking accessible to everyone and put the Quest even further ahead in the VR market. Best regards, Vinícius
Business Verification "In Review" for Over 1 Month — Australia
Hi, I'm hoping someone from Meta or the community can help. I submitted my business verification for Loft Learn Business (Business Portfolio ID: 1290741856233149) approximately one month ago and the status has remained "In Review" ever since. I'm based in Australia and all business details are fully completed including legal business name, address, phone number, website (loftlearn.com), and Tax ID. I also recently added our Primary Facebook Page to the portfolio which was previously missing. There has been no request for additional documents, no rejection, and no communication from Meta at all — the application appears to simply be sitting in a queue with no movement. Is there anything that can be done to escalate or progress this review? Are there known delays for Australian businesses at the moment? Any help or guidance would be greatly appreciated. Thank you, Luke
