PC Link Passthrough Masking Issues After Meta Link Update
First, I noticed that the 'Beta' menu has disappeared from the Meta Link app. The issue I am encountering involves a masking misalignment between 3D content and the real-world background in Passthrough mode. Specifically, there is an offset where a black silhouette protrudes upwards above the content. I am aware that PC Link Passthrough is primarily intended for debugging purposes. However, this is a critical issue for us because our main content relies heavily on this feature. Is there any solution or workaround for this
DeoVR busted again with new update
I for the longest time thought that DeoVR was to blame, but since the firmware update a few days ago, I realize it's been the Quest firmware updates hysterically tinkering with head tracking the whole time. I'm on Quest 3, but i had the same issue on Quest 2 - suddenly and without warning, the 6ofD head tracking and dome scaling just becomes "wrong" out of nowhere. E.G., tracking your head forwards or backwards will zoom appropriately, but every other dimension will translate WAY too much as a result, making the video you're watching hypersensitive to tiny little micro motions you don't even realize you're making with your head, rendering almost anything with video or passthrough completely useless. Previous firmware it was calibrated better, it almost seems like it goes normal>bad>normal>bad, with each update. You're basically having to choose between things looking wrong in one way, or looking wrong in a different way. From update to update, It's never consistently wrong, and it's not the app. I keep several versions of the app on hand to jump between whenever this happens, even though it usually doesn't fix anything. It makes more sense now that I know it's not DeoVR, because sometimes I'd be on the same exact version and turn the headset on and just feel like everything suddenly looked horrible where it didn't just hours prior. The color grading gets weird, the passthrough feed and the video clash colors forcing me to turn up night mode so everything is an analogous orange, but which totally defeats the purpose of having color passthrough at all. I guess my question is, why are we messing with the head tracking and color grading at all, when clearly we know that we know what looks good and what doesn't since every alternating update gets it right? It's almost like I'm being pranked, or like I'm being manipulated into engaging here on the forums, or being baited into getting upset and doing unwitting advertising by complaining online, or something. Why is the meta for our updates snip snapping between the normal product I paid for and an insane clown world version with no explanation? This most recent update the tracking is so bad I get motion sickness just IN THE MENU without even opening an app or game at all. How much the passthrough feed moves relative to the very slightly translating HUD menu I'm trying to read makes me feel like I need to immediately rip the headset off and find a bowl to puke in, and I've almost never gotten motion sickness in my entire life. Anyway, really hope we can fix it, thanks for your time.v85/v2.1.1034 Passthrough Loop
I put this on Reddit also posting here in case it's a bugged update? Ok so this is my issue after Feb 27th v2.1.1034 Update: 1. The Problem: v85/v2.1 "Passthrough Loop" AI advises: This specific flickering issue (cycling between Home and Passthrough) is a known bug associated with the v85/v2.1 update. It appears to be tied to a conflict between the new "Navigator" UI and the headset's tracking/boundary service. Why it happens: The OS is essentially "crashing" the immersive home environment and falling back to Passthrough as a failsafe, then attempting to reload the environment again. The "Double Tap" Fix: Manually forcing Passthrough works because it tells the OS to stop trying to render the immersive environment, which bypasses the crash loop. 2. Process: Meta Software Update Tool Attempted resolution: I proceeded with the Sideload Update - update successfully loaded but.... Issue persists > Goto 1. LOL. So right now I will perhaps await the next meta update which may fix my problem before attempting a factory reset and linking accounts up etc... > If I manually enable pass through, I can get to quick access menus etc. so could update from there when next update available. > I haven't tried - PC Wired Link yet, so hopefully can get to MSFS SIM I use. > For the moment, standalone usage is a no go. Note: > I do have WhatsApp on the Quest which I know is active and in past updates I've seen this crashing in the background via notifications message things popping up. That has not happend this time but I think the Q2 may be struggling in my case as per above, something is causing it to crash. > I recently starting testing the 3rd party Immersive App on Q2 with it's version of remote desktop and virtual second monitor feature it can use with a laptop, as native Meta RD can't do that.....but I'm assuming nothing is running in BG with that app if it's not being used...... META / Anyone - any thoughts?
Quest 2 Stuck on passthrough on wake-up
I just used my Quest 2 and for some reason it's stuck in passthrough when I turn it on. The controllers won't connect and are at full battery (as is the headset), and the only thing I could do was adjust the volume, where it displayed the volume slider graphic, but turned the entire screen black, which then returned to passthrough when the slider went away. So far I've shut it down and restarted it a number of times, all with the same results. I had used my Quest 2 a couple of days ago and it was working fine, I hadn't done anything too taxing on it graphics-wise, so I'm not sure this how this came about. Does anyone have a fix for this?Request to restore ON / OFF option for “Double Tap to Toggle Passthrough”
It seems that the ON / OFF setting for “Double Tap to Toggle Passthrough,” which existed prior to v81, is no longer available. During gameplay, when adjusting the Quest headset (for example, fixing its position), the double-tap gesture can be triggered unintentionally. This causes the game to switch to passthrough mode, interrupting gameplay and breaking immersion. It would be very helpful if this feature could be configurable again via the settings menu (ON / OFF), as it was before. Restoring this option would greatly improve the experience for users who value immersion, especially during games and interactive applications. Thank you for your consideration. ※Japanese 「ダブルタップでパススルー切り替え」のON / OFF設定を復活してほしい v81以前に存在していたはずの 「ダブルタップでパススルーを切り替える」機能のON / OFF設定が、現在は利用できなくなっていると思います。 ゲームプレイ中にQuest本体を触ったとき（装着位置のズレを直すときなど）、 意図せずダブルタップが認識され、パススルーに切り替わってしまうことがあります。 その結果、ゲームが中断されたり、没入感が大きく損なわれてしまうことがあります。 以前のように、 設定からこの機能をON / OFFできるようにしていただけると非常に助かります。 没入感を重視するゲームやアプリを快適に体験するためにも、 ぜひご検討をお願いします。Quest 3 (v81.1034) randomly cannot access the user profile menu after waking from sleep
I have some sort of random glitch when the Quest3 headset (v81.1034) wakes from sleep. Sometimes it only shows passthrough, and the menu to select which user profile to use does not appear. If I press the sleep button a few times, the profile menu appears for a fraction of a second and then disappears and goes into passthrough mode again. So, when this glitch occurs, I am unable to select my user profile to log in to the Quest 3. If I double-tap the headset to exit passthrough, it tries to load my new Immersive Home but fails to load because I have not been able to select any profile, so it gets stuck in load screen limbo: From here, all I can do is restart the headset, which fixes the problem temporarily. This glitch has happened 3 times in the past 3 days since getting the V81.1034 (non PTC) update on 21 October. I've already reported this glitch to Meta via the headset bug reporting option. UPDATE: the glitch happened again just now. I pulled the headset away from my face slightly and noticed that the user profile menu reappeared. As soon as I put the headset closer to my face, the passthrough came back on and the profile menu disappeared. I was able to hold the headset slightly away from my face and click on my user profile using the controller. Then the headset started up as normal and my Immersive Home loaded. It seems like some sort of glitch in the way v81 uses the proximity sensor when waking from sleep.
Eye Tracking with Meta Quest Link
Hello everyone! I am trying to trigger eye tracking via Unity directly in the Unity Editor with Meta Quest Pro. When I build an apk, eye tracking works. But it doesn't work via Meta Quest Link. I have read repeatedly over the last few weeks that there have been problems with Quest Link. I wanted to ask if anyone has recently been able to implement a project in which eye tracking worked via Meta Quest Link and what tools were used. I have already read that ALVR via SteamVR is an option for transferring eye-tracking data, but I had problems with the packages. (My understanding is that you then need the SteamVR package and XR Interaction Toolkit instead of the Meta All-In-One SDK). As a side topic, another question would be whether it is currently normal for passthrough transmission on the Quest Pro to be very slow with the current Quest Link version, but to work normally with the Quest 3. My preference would actually be to do everything with the Meta Quest Link connection and the Meta Quest All-In-One SDK. However, if passthrough and eye tracking don't work via Quest Link, a solution with SteamVR may be necessary. Thank you for taking the time to read this. I would appreciate any tips.
