Add a toggle or remove automatic boundary switching.
I noticed with the most recent firmware updates (yay, they get worse as a new one comes out that keeps breaking my headset), that Meta has literally made my headset unusable for me. Meta, I am disabled. I have issues where I have to take off the headset almost every 10 minutes, and it sucks, really it does. Life is already super hard for me, but what I DON'T need, is for my only source of entertainment, is to come back after a flare up episode of my disability, to find that just because I put my headset down, it switched the boundary from "Roomscale" to "Stationary". Now every single time my disability acts up, I have to take the headset off, deal with my disability, come back, put the headset on, minimize steamlink, go into my settings, turn off stationary and put it back to roomscale (if it lets me because sometimes the stationary boundary gets messed up and only asks me if I want the new stationary circle HERE), then get back into steamlink, only to get motion sick because my boundary changed when I put the headset back on, and once more when switching it back to roomscale, and then have another disability flare up 3 minutes after getting resituated back into VR. You turned my quest pro into a paperweight. I don't know what the hell is going on, but every firmware update after v71 has the quest experience worse an worse, to the point where I can no longer use the headset without it causing an extreme immense of mental anguish. I bought the quest pro to be happy and play games. Not to stress the hell out every time I put it on. Thanks for the $650 paper weight Meta. - A disabled customer
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)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
technical issues
hello i am a game creator and i need help i have the when i try to load into my game it just doesnt let me get in its stuck at the loading part i didint add any loading screens just straight into the game and it just doesnt get in please help this is just killing my motivation i had this in all of my projects
Crash reports
Hi guys, I have a crash report that affects just one user and always occurs in exactly the same place. Other players with the same build, same HMD are playing fine. As far as I have been able to work out the issue is related to UI Widgets but even this i am not certain of. Does anybody have any idea what's going on here and how to debug and fix it? This is the report summary and then the stack trace... oculus:native_crash:SIGSEGV:libUE4.so::FSlateRHIRenderingPolicy::BuildRenderingBuffers(sanitized)::$_21::operator()(sanitized) const Thread 10669\ #00 pc 000000000008c438 /apex/com.android.runtime/lib64/bionic/libc.so (memcpy_aarch64_simd+248) (BreakpadBuildId: 5cc6b9f35ce196db1de51b94b123688b0)\ #01 pc 0000000008abc378 libUE4.so (FSlateRHIRenderingPolicy::BuildRenderingBuffers(FRHICommandListImmediate&, FSlateBatchData&)::$_21::operator()(FRHICommandListImmediate&) const + 0x98) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #02 pc 0000000007829a94 libUE4.so (FRHICommandListExecutor::ExecuteInner_DoExecute(FRHICommandListBase&)+168) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #03 pc 000000000784bba8 libUE4.so (FExecuteRHIThreadTask::DoTask(ENamedThreads::Type, TRefCountPtr<FGraphEvent> const&)+164) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #04 pc 000000000784b980 libUE4.so (TGraphTask<FExecuteRHIThreadTask>::ExecuteTask(TArray<FBaseGraphTask, TSizedDefaultAllocator<32> >&, ENamedThreads::Type)+52) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #05 pc 0000000006e3ca18 libUE4.so (FNamedTaskThread::ProcessTasksNamedThread(int, bool)+244) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #06 pc 0000000006e3c598 libUE4.so (FNamedTaskThread::ProcessTasksUntilQuit(int)+108) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #07 pc 0000000007889144 libUE4.so (FRHIThread::Run()+72) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #08 pc 0000000006eb1a6c libUE4.so (FRunnableThreadPThread::Run()+96) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #09 pc 0000000006e3b0f0 libUE4.so (FRunnableThreadPThread::_ThreadProc(void)+68) (BreakpadBuildId: 3e5160afb0844a0e3b5777981db217330)\ #10 pc 00000000000fd0ec /apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*) [bionic/libc/bionic/pthread_create.cpp:382 + 0x4]) (BreakpadBuildId: 5cc6b9f35ce196db1de51b94b123688b0)\ #11 pc 0000000000094fb0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread [bionic/libc/bionic/clone.cpp:53 + 0x4]) (BreakpadBuildId: 5cc6b9f35ce196db1de51b94b123688b0) 2026 Meta🧠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 shipOS freeze every 60 seconds with hand + body tracking
Not sure if this is the best place or if there's a support place for devs, it is hard to keep track of where best to bring these things up. Anywhoo. Spent that last 2 days tracking this down thinking it was me. But, if you are on the latest OS, in the Meta Home, with hand tracking enabled, and you flail your hands around like a madman, doing "the wave" with your fingers, alternating with making fists and being the worlds fastest drummer, you'll get a little spike, like clockwork, every 60 seconds. May seem a bit much, but my app is a dance game that uses hand and body tracking and makes use of the new fast hand and body tracking that, apart from this issue, is fantastic. It is not a huge spike, but it freezes the entire OS and so in game that translate to a little hitch in the visuals and in the music and the music hiccup is super noticeable. And it is like clockwork every 60 seconds. Though, sometimes it takes 60+ seconds for the first one. It makes my game feel unprofessional :( With hand tracking disabled, the spike does not show up. If you have hand tracking enabled but you don't move your hands much, it does not show up. I did figure out one thing though. I've got a little timer that every 20 seconds requests that fast tracking support be disabled for 10 frames, then turn it back on again. The user won't notice that tracking isn't quite as fast for 10 frames and it seems to reduce the spike about 80%, but even that 20% is noticeable and who knows how long that hack will work, an OS fix would be better. Wondering if anybody else is running into this, any other hacks I could try, and a "we're on it" from Meta or a "file this over here" would be my preferred responses :) Thanks in advance for any and all replies, Damon
The Navigator Identity Crisis: A Call for Design Sovereignty and Customization.
To the Meta Design Team, you are making your device worse by trying to be someone else. Meta was the leader because you were the ones who actually figured out how to make standalone VR functional and accessible in the first place. For you to throw away the very leadership you built just to become a knock-off version of Apple is a total failure of vision. You didn’t need to reinvent the wheel, you just needed to polish it. Instead, you’ve scrapped a great, functional interface for a filtered version of the Vision Pro. By forcing the Navigator into a rigid, head-locked position, you’ve sacrificed user sovereignty for a spatial look that you don't even have the eye-tracking hardware to support on your current mainstream headsets. Even if your next device has that hardware, the millions of people using your hardware right now shouldn't be forced into a "look-to-lock" logic that makes the system feel broken. Taking away the ability to freely grab and park windows, forcing us to re-center our entire world just to move a menu is a massive UI/UX regression that makes the system feel less capable and more restrictive. This interface feels like it was designed by geeks who prioritize clean code and data structures over how a human being actually moves their hands and head in a room. Mark Zuckerberg started with a site that was nothing but white backgrounds and blue text a bland, sterile database and that same nerd logic has now infected the Quest. A nerd designs a menu based on where it’s easy for the code to sit; a designer or a real user needs it where their hand naturally wants to reach. Your current interface is the definition of mayonnaise tech: bland, sterile, and corporate. You finally made the Navigator transparent, but you stopped halfway. Transparency isn't just a style choice; it’s a mechanical need in a spatial environment. Why are the store, the menus, and the sub-folders still stuck in these solid gray and white blocks? Every single window should be transparent by default. This is the obvious direction for the medium, yet you're forcing us into light versus dark folders instead of just providing opacity sliders. Users need the ability to choose if they want to block the world out or let their room shine through. It is 2026, so being stuck with gray and white as our only options is a joke. A simple color wheel for the UI would allow for a green aura, a blue glow, or custom highlights for menus. A transparent green theme should be a simple slider adjustment, not a corporate mandate. You already had a winning format with the original Quest interface. You didn't need to scrap it; you just needed to make it transparent and give us the tools to move it. You need to restore the "grab-to-slide" logic so we can orbit windows 360 degrees and park them to our left or right without the system fighting us. Stop trying to look fashionable through imitation. You built your success on utility and being the original in the standalone space, don't throw that away to be a second rate copy of a competitor. Give us back the original soul of the Quest, enhanced with the transparency and the customization that this technology actually demands.Updated 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.
