Recently active
Hello! I've got strange issue yesterday. My oculus link works well in the shell. I can see the gray background and dashboard panel. But any apps failed to start. Even Oculus Dreamdeck with the dino doesnt'work. In my app i can see failed messages like that:29/08 13:12:57.099 {INFO} [RuntimeIPCClient [RUNTIMEIPC]] ReleaseRef: Remaining refs: 2, Client: WindowsPackage:WindowsProcess:22148, Server: WindowsPackage:WindowsProcess:0 (RuntimeServiceServer)ipcLoader [RUNTIMEIPC]RuntimeIPC: Loaded library from C:\Program Files\Oculus\Support\oculus-runtime\RuntimeIPCServiceClient_64.dllREFLECT [RUNTIMEIPC] WARN@ arvr\projects\xrruntime\mobile\1stParty\RuntimeIPC\RuntimeIPCHelpers\Include\Private\RuntimeReflectIPC.h(2694): ipc_GetServerState FAILED: PerformanceManagerStateREFLECT [RUNTIMEIPC] WARN@ arvr\projects\xrruntime\mobile\1stParty\RuntimeIPC\RuntimeIPCHelpers\Include\Private\RuntimeReflectIPC.h(2694): ipc_GetServerState FAILED: KPIFeatureMeasurementsStateREFLECT [RUNTIMEIPC] WARN@ arvr\pr
Bonjour, j’ai un problème mon casque il est tombé et une lentilles est sortie j’ai remis la lentille et depuie lecrant n est plus stable sa coupe et sa revient sa s arrete pas
La página web de soporte me tiene en un bucle infinito. Cada que intento abrir un ticket me dice que no hay ningún dispositivo vinculado a mi cuenta, y si pongo el número de serie de forma manual me bloquea diciendo que "no hay servicio de ayuda disponible", por lo que me es imposible acceder al chat en vivo o al formulario.Resido en méxico, compré unos meta quest 3 en noviembre del año pasado a través de amazon mexico, vendidos y enviados por amazon méxico.La pantalla del ojo derecho del visor tiene varios píxeles atascados en color blanco justo en el centro de la visión que distraen en su uso, 5 de ellos resaltan siempre, y se notan mucho más en la pantalla de carga cuando recién se enciende el dispositivo, conté al menos 10 en el centro y hay otros pocos muy tenues en los bordes.Después de notarlos seguí usando mi dispositivo porque leí que podrían ser "pixeles atascados" pero lamentablemente estos nunca se resolvieron.En el apartado de mi cuenta me aparece claramente que mi garantí
Hello Meta Support Team,I am completely locked out of my Meta account and cannot use my Meta Quest 3 headset.The account requires Two-Factor Authentication via SMS, but the verification code is being routed to an old, disconnected mobile number. There are no alternative recovery methods or backup codes configured on the account.Here is my current situation:I have full, verified access to the registered account email address and have completed password resets via email.I am in physical possession of my Meta Quest 3 hardware.Attempting to use the web support portal redirects me in automated loops requiring a device login or sending codes to the disconnected number.Direct messaging to the support handle on this forum is currently not submitting on my end.Could an official Meta Community Moderator please send me a Private Message so I can share my account email, headset serial, and complete identity verification privately?Thank you,Christopher
Folks: Several weeks ago, I noticed my Meta Quest 3's "charging" light was orange instead of its usual green. When I turned it on, it was only 73% charged. My research into the problem mentioned that Meta had pushed a "buggy" firmware update that was causing the incomplete charging. I tried all of the "fixes" mentioned in my research, but nothing worked.Has anyone else experienced this problem and, if so, what did you do to resolve it?Thanks for your help!
The latest Quest 3 system has a backlight flickering issue when charging with the original charger while the device is powered off. This issue was first reported on forums after the v74 system update. After investigation, it was found that first, the issue does not occur when using non-original chargers. Second, the flickering frequency decreases as the battery level increases: it flickers about every 30 seconds when the battery is around 20-40%, increases to about every minute when the battery is 60-70%, and most likely stops completely when the battery is above 90%. It is preliminarily judged that this issue may be a system-level bug where the charging protocol negotiation with the original charger accidentally triggers the screen backlight controller. The temporary solution provided by customer service is to charge the device in sleep mode by short-pressing the power button, which has been tested and indeed no longer causes the issue. They explained that the system has more sta
Hi! New version of firmvare (v81) doesn't exists option like "Passthrough->Enable passthrough double tap on quest" And now, if I double tap on my quest, it enable passthrough. How can I fix that? Maybe some adb command or smth else or only wait new update?
Hi Everyone, I am facing a critical issue with Meta Muse. My account was automatically locked out due to a false suspicious activity flag while I was actively working on a time-sensitive project. I have completely cleared my Meta Security Checkup (updated password, passkeys, and verified devices), and my master Facebook and Instagram profiles are 100% active and healthy. However, the Muse application remains stuck on the screen: We disconnected Muse to protect your information. Because the main ticket button is broken, I successfully submitted a developer report with full logs attached. Bug ID: *** Current Status: Stuck in login loop/Production completely halted
I have an Insta 360 camera and a bunch of photos and videos from it downloaded onto my laptop. I converted them into jpg and mp4 files. I would like to upload them onto my Quest 3 to see them as an immersive experience. (ChatGPT told me that this is the correct format for use on a VR headset).ChatGPT is giving me instructions (plug the headset into my Macbook Air laptop's USB-C port, use the OpenMTP application). But I can't get it to work. On the Quest headset, I don't see an option for uploading files.Can somebody help me with this? Aside from using the Quest headset for games, I would like to view my photos and videos in a 360 degree environment. Thanks!
I'm transferring my Insta360 photos and videos to my Quest 3 headset for immersive viewing. I've only done a couple so far as a test. Before I do the rest, where is the best place to put these on my Quest? Right now, I just have them in the Quest FILES folder. Would it be better to put them in the Photos and Videos folders, respectively, instead?My 360 photos and videos are on my laptop, divided into folders by date and place (most are from vacations). If I move entire folders onto the Quest, will the file names and file structures stay intact so I can find specific photos easily? TIA for your help!
I hate this new loft. You can’t customize it except for the sky box. Seems like a huge step backwards. Does anybody know if there’s any plans to do the old environments?
Meta uses an AI chatbot on their support page because they want to be "up with tech trends" or whatever, but the AI bot is looping me in circles. When I ask it to connect with an agent, it gives me a link that leads me right back to the support page. I cannot get in contact with a human agent and the AI is unable to help me start a warranty claim. This is genuinely just horrific. I can't start a warranty claim unless I can contact a human. Do better.
I am having problems with various Quest 3 headsets. All the headsets are showing the same issue. The controllers battery is draining super quickly.The pattern is always the same. I put new batteries and use them once for 1-2 hour session. Then I switch everything off and the next time I switch them on again (the same day in the afternoon, or after one week, or after 1 month) the controllers batteries are dead and I need to replace them again. Is there anyone else that is having this issue?Has meta investigated this? Can you please look into this issue and see if it is a software problem? How could I solve this?
when i load virtual desktop up the picture is like rainbow affect not a mirror image of my desktop please help thankyou
My original personal Meta account has been compromised. An unauthorized person added/changed the email address and enabled authenticator-based 2FA that I do not control.I still control the original phone number associated with the account. Meta successfully verifies my phone number during recovery, but immediately afterward requires a code from the unauthorized authenticator. This makes recovery impossible.Accounts Center also shows an unauthorized Windows PC session in a location I do not recognize. I have never used a Windows PC for this Meta account.I still have access to my connected Facebook account and can see the compromised Meta account in Accounts Center, but I cannot remove the unauthorized email, remove the unknown session, reset the Meta password, or change 2FA because each action requires authentication controlled by the attacker.I have already exhausted the standard Meta recovery options, including password recovery, phone verification, device recognition and 2FA recovery
I have a problem with my Quest 2 when I am trying to record a video. When the video capture is turned on, the view lags and stutters as I move my head around. The lag is very noticeable and makes whatever app I am in unplayable. The problem stops once I stop recording. What is strange is the lag and stutter does not show up when I playback the recording. This problem occurs whether the headset is standalone or cabled to my PC. I am at a loss on how to resolve this issue.
Rift S unusable on Windows 11 — Meta Horizon Link Setup instantly crashes in clr.dll, old runtime sees headset but no tracking/black screenI’m trying to get my old Oculus Rift S working again and I’ve now spent about 8 hours troubleshooting this.My PC is:Intel i9-14900KRTX 308032 GB DDR5Windows 11, build 10.0.26200.9457MSI Z790 GAMING PLUS WIFIThe main problem is that the current official Meta Horizon Link / Oculus Setup installer will not launch at all. It flashes briefly and immediately crashes before the installer UI opens.Reliability Monitor shows:Application: Setup.exe_Oculus Setup Version: 1.115.0.0 Fault Module: clr.dll CLR Version: 4.8.9345.0 Exception Code: c0000005 Exception Offset: 0001ccf0An unrelated program, LGMonitorAppManager, has also crashed in the same clr.dll with the same c0000005/offset, although the rest of my PC works normally. Games, launchers, Windows, etc. are generally stable.Things I have already tried:Fresh official Meta installerRun as administratorRunnin
In prior iterations of Link, if you double tap to get passthrough, the options presented were quit and resume. Now it is just quit. I tried raising this before and you cannot record video of the popup menu when in passthrough to show it, which led to nothing further.There are times I am not using controllers, and it would be nice to be able to quit out of link back to the OS without needing a controller.I could not find the suggestions section of the forum.
I'm a pro gorilla tag player getting affected by this a lot and really need an update to switch this. In my settings in Controllers-Vibration-Intensity, The slider is all the way to the lowest to the left. I go to my game and I feel a vibration it is still happening. This is for everyone because of the dang update and it's annoying me and other people as well. If any developers or any high level people could update and change this gladly. More clarification needed?
Dear Meta Quest Support, I would like to request assistance with recovering my Meta Quest 3. Device: Meta Quest 3 Serial number: **** Product identifier: **** The headset was working in the evening, but the following morning it would only boot into the USB Update Mode menu. It was not connected to a charger overnight. The exact cause of the issue is unknown. Symptoms: Selecting normal boot, Factory Reset, or Sideload Update causes the headset to restart almost immediately and return to the same menu. Sideload mode does not start, and the LED does not turn purple, so I cannot transfer an update. The Device Info screen remains stable. With USB disconnected, powering off works. Connecting a charger automatically turns the headset on, and the menu reappears with an orange LED. Charging behavior: An inline USB meter initially showed approximately 5 V / 1.5 A, which subsequently dropped to around 5 V / 0.5 A. I observed similar behavior with several chargers. On one occasion, the USB input r
Hello,We have encountered an issue with the keyboard overlay since updating to version 2.7.Our application is published on the Meta Horizon Store.The exact same application build works correctly on another headset that is still running version 2.6: when the user selects an input field, the keyboard overlay appears normally.However, on the headset updated to version 2.7, the keyboard overlay no longer appears, so users cannot enter text.Has anyone else experienced this issue since the update?Meta team, could you please confirm whether this is a known bug introduced in version 2.7 and keep us informed about a possible fix or workaround?Thank you.
Hello,I am assisting the owner of a Meta Quest 2 that is stuck in a USB Update Mode boot loop.Selecting Boot Device, Factory Reset, or Sideload Update immediately returns the headset to USB Update Mode. We installed the official Oculus ADB driver, and Windows detects the headset as “Oculus Bootloader Interface” in USB Update Mode. However, it is never detected as an ADB device.When “Sideload Update” is selected, the headset disconnects briefly and then returns directly as Oculus Bootloader Interface instead of entering ADB sideload mode. It has also appeared in Windows as QUSB_BULK_CID:0412, indicating Qualcomm EDL emergency recovery mode.I have attempted the official Meta Quest Software Update Tool, but it cannot connect because the headset never enters ADB sideload mode.I do not know the exact purchase date, but the device is most likely outside the warranty period. Before involving the owner’s account details, could you please confirm whether Meta offers an out-of-warranty repair, r
Add this version mismatch before. I believe the only way I could solve it was just letting the app roll out the next update to match my headset because I don't think I could rollback my device. My headset. To match the app. Are there any solutions?Copilot said:The important message is the yellow "Version mismatch" warning.The tooltip is telling you:"For best performance, match your versions on headset (v207) and PC (v208)."This means:Your Meta Quest 3 headset is currently running firmware/software version 207.Your Meta Quest Developer Hub (or Meta Link software on the PC) is running version 208.The versions do not match, so Meta is warning that some developer features may not work correctly until both are on the same version.
Hi, My recorded videos from Thief VR are way too dark, much darker than what I see on the gameplay. This issue started after my Quest 3 updated to the v2.7 version! Before that the video quality was great, and it was usually lighter than my gameplay!
I needed to reinstall the meta link to try and fix a problem, but now it's refusing to install, it gets almost all the way through the installation process, the shortcut even appears, but it then vanishes and says an error occurred, and no matter how many times I restart, the problem persists, can someone help me please?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.