🧠Profiling and Memory Deep Dive
Good VR performance starts with knowing where the bottlenecks are, and profiling is more approachable than you'd think. In this session, Meta Horizon Start Mentor Sidney walks through general profiling techniques with a focus on Unity's profiler and memory profiler, Unreal Insights, and automated performance testing frameworks. This session gives you the foundational tools to find performance issues and build profiling into your regular workflow. What you'll walk away with: A practical intro to profiling and how to think about performance in your projects Unity-specific tools including the profiler and memory profiler Unreal Insights and how to use it to identify bottlenecks Automated performance testing so you can catch regressions before they ship
Sudden Loss of Body Tracking & Crashes with Unity Movement SDK (Quest 3) since version 2.3 update
Hi everyone, I am experiencing a critical issue with the Unity Movement SDK on the Meta Quest 3, and I've noticed a few other developers mentioning the exact same problem recently. My project relies heavily on the Movement SDK, and it was working perfectly fine up until recently (around April 29th/30th). Suddenly, body tracking has completely stopped working. Here are the specific symptoms and the troubleshooting steps I've already taken: Persistent Crashes: The project now crashes consistently when hitting Play in the Unity Editor. It also crashes when I build and run it directly on the Quest 3. Older Builds Failing: I initially thought I broke something during a project update, but when I tested older, previously stable builds that had perfectly working body tracking, they also failed. My Setup: Device: Meta Quest 3 (Version 2.3.1034) Software: Meta Horizon Link (Version 201.0.0.73.547) Because older, untouched builds are now failing, this strongly suggests a bug or breaking change introduced in a recent Meta Horizon Link or Quest OS update rather than an issue within Unity itself. Is this a known issue currently being looked into by the Meta team? If anyone has found a temporary fix or workaround, please let me know. Any help is appreciated. Many thanks!!
Unable to receive SMS verification code required to create Meta for Developers account.
I am attempting to register for a Meta for Developers account at developers.facebook.com to build an Instagram Graph API integration. The registration flow requires phone number verification via SMS, but no verification code is ever delivered to my phone. Environment: - Country: South Korea - Phone: regular carrier-issued mobile number (not VoIP, not virtual) - The same number receives SMS from all other services (banks, Google, Apple, etc.) without issue - Personal Facebook account is active and in good standing; this phone number is already linked to it - No existing Meta for Developers account associated with this number Symptoms: - The verification screen displays "Code sent" but no SMS arrives - Waited well beyond the stated delivery window on each attempt - After repeated requests, the system rate-limits further attempts - Issue persists across multiple browsers (Chrome, Safari, Firefox), incognito mode, and different network connections (home Wi-Fi, mobile data, different IP) Troubleshooting already attempted: 1. Re-added phone number to Accounts Center two-factor authentication (SMS option) — no SMS received 2. Attempted WhatsApp verification path via Accounts Center — failed 3. Waited 24+ hours between attempt batches to avoid rate-limit lockouts 4. Tried different devices (desktop and mobile) 5. Verified phone number is correctly entered with +82 country code 6. Confirmed carrier (Korean major carrier) is not blocking short-code SMS 7. Checked spam/blocked-sender settings on the phone — clear Data loss / abuse: None. This is a pre-account-creation issue. I have not lost data or experienced abuse; I am blocked from creating the account in the first place. Impact: I cannot proceed with building the planned Instagram Graph API integration until phone verification is resolved. Request: Please manually verify my phone number on Meta's side, or provide an alternative verification path (email-based, ID document, etc.).
Horizon Central
I understand that Meta has its own economic reasons and market dynamics for shutting down some parts of Worlds and making it mainly available as a mobile app, while leaving only old worlds accessible on the VR platform. What I do not understand, however, is how they are managing Horizon Central these days. For some time now, Horizon Central has no longer been functioning properly and is already showing signs of its upcoming closure to the public. In Central, in fact, it is no longer possible to talk with other people because everyone is muted. Instead of preventing the many people who still visit Horizon Central every day from talking to each other, Meta could simply place a notice explaining that, in a few days, Worlds will mainly be accessible from mobile devices, that only some worlds will remain available in VR, and that Horizon Central itself will no longer be available. It would be a respectful gesture toward the many users who are attached to this platform and who will genuinely miss it.🎥 Fast Essentials: Turn Your Game Into a Content Machine
Without the right capture strategies, your gameplay footage might not be showing your app in the best light. Join Start Mentor Tevfik as he breaks down how to use the LIV Camera Mod to capture cinematic angles and social-ready footage. Stop struggling with raw headset crops and start generating the high-quality content you need for TikTok and YouTube. Join on Zoom
​next gen full body tracking using native wifi drivers
i want to propose a hybrid tracking system using sensor fusion instead of wifi working alone it would complement the quest cameras the cameras track the upper body while the wifi csi data fills the blind spots for the lower body and legs this solves the messy data problem because the system already has the headset and controllers as a base meta could add a toggle for full body tracking or upper body only to save battery it would be an optional feature powered by a low level system driver what do you think about this integration with the current movement sdkExploring 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)Accept Button Stuck on Loading
Hey everyone! For 3 days now, I’ve been trying to accept an invite to an organisation, but the accept button is stuck on loading. I’ve tried switching devices, refreshing the page, restarting the device, declining the invite and getting sent a new one, and anything that came to mind. But nothing has worked. I tried accepting the exact same invite on my sister’s account, and it let her accept it straight away. Has anyone got any advice on how to fix this?
The position of the Vignette in OVRVignette is off-center from the field of view.
When using OVRVignette, the position where the field of view is narrowed is off-center from the field of view. Besides being off-center, different areas are obscured by each eye, making it very difficult to see. _OpaqueMaterial.SetVectorArray(_ShaderScaleAndOffset0Property, _OpaqueScaleAndOffset0); I think the above process probably changes a shader variable to determine the Vignette's position, but I don't know anything beyond that... Does anyone else have the same symptoms or know of a solution? Unity 6000.2.15f1 Meta XR Core SDK 85.0.0 Using Meta Quest 3 Meta Quest Link 85.0.0.239.552Model Everything, I Guess?
Alright, Meta AI, hear me out. A little background: I'm a small-scale web developer, videographer, and photographer with about 10 years of experience. Over the past year, I took something of a gap year to dive into AI and research the technology. This led me to a project that's in line with my expertise: real estate and architectural photography, which is basically about capturing spaces. My idea is to train a model using a combination of Instagram & Facebook images (with their tagged locations, of course) and 3D terrain models from multi-date satellite images (In the future: add property listing images). By combining these, we could create a virtual, living, breathing digital twin of the entire real world. This model would map both the outside world and most public indoor spaces, likely requiring a staggered rollout. I know this would require a metric ton of servers. I'm currently tinkering with a small-scale prototype, but I don't have the resources to scale this monster. The biggest limiting factor is being from South Africa (born in '98). Our government isn't exactly tech-friendly; instead of encouraging new tech, they create roadblocks and regulations that stifle innovation, all to protect corrupt, archaic monopolies. It's infuriating. Meta already has all the data needed for this model. So, if anyone at Meta AI sees this, please build this thing. And hey, maybe hook a man up with a tiny royalty? 😉 P.S. I would love to build this with you. Seriously, hit me up. Kind Regards, T South Africa
