Meta Quest Link's virtual camera causes third-party applications to crash.[windows]
Hello, we've encountered a serious compatibility issue and would appreciate your assistance in resolving it. Problem Description: Meta Quest Link's virtual camera causes third-party applications that use DirectShow to enumerate cameras to crash. Reproduction Steps: 1. Install Meta Quest Link 2. Launch an application that uses DirectShow to enumerate cameras (such as OBS Studio) 3. Delete the camera source in the application 4. The application crashes Affected Scope: 1. Crash Probability: Nearly 100% 2. Affected Applications: All third-party applications that use DirectShow to enumerate cameras 3. A large number of our users use Meta Quest Link and have all experienced this issue. 4. Well-known applications like OBS Studio are also affected. I've seen users report this issue in the OBS repository. 5. This issue severely impacts user experience and product stability. Technical Analysis: The crash occurs when DirectShow enumerates the Meta Quest virtual camera. The IBaseFilter object (the fourth parameter) is obtained through the IMoniker::BindToObject() interface, and the crash occurs when releasing this object. The Meta Quest Link virtual camera may have a flaw in its internal memory management of the IBaseFilter object. We hope the Meta team can fix this issue.
SpaceWarp works in empty project but not main one (Unity 6000.1.6f1, Quest 3)
Hey all, I’m running into something weird with Application SpaceWarp on Quest 3. I set up a clean empty project in Unity 6000.1.6f1 with OpenXR (Meta XR features) and Vulkan only. SpaceWarp works fine there and the performance overlay shows ASW kicking in as expected. But in my main project (same Unity version, same OpenXR/Vulkan settings) , SpaceWarp never activates. Both projects have: Meta XR Space Warp enabled Vulkan as the only graphics API Same Project Settings → OpenXR (Application SpaceWarp checked) Same Player/Quality settings I already checked URP settings, even copied the same and Materials show the XR Motion Vectors Pass still no luck. Any tips for narrowing down what breaks it? Maybe some other package that I have on my main project? Thanks!!!
Large map building&texture help
Hello, I'm new in Horizon Desktop App, started creating few things. I have 2 questions that needs your helps. Is it better to parent+stack everything into a single Asset after I finish building some objects? For performance issues, because my world itemwise only %3 but almost %70 in vertex limits. How can I reduce this vertex usage? I cannot adjust textures. I'm creating one, inserting into my floor, but all the stones on the floor are so big that doesn't look realistic. I want to pattern to repeat itself in a smaller scale. Thank you for your helps
meta quest developer hub issue
First of all, I think I might have posted this in the wrong category… apologies in advance. Best regards, I’m new to this forum and to the community. I want to take my first steps in dev, experiment a bit, and see how far one can get being creative with the features that devices offer. Along the way, I started setting up the Meta Quest Developer Hub. Everything went fine, but I have a question. I switched the Link version to Public Test. My device is now set to Public Test, but I still haven’t received OS v81. My question is: does switching the Link version to Public Test not actually push the device to update its version? I assume it doesn’t and that it just changes the communication channel, but I’d like to confirm to be sure. Another question: is there a way to manually push v81 through ADB?High crash rate of GameActivity onPauseNative
In my app available on the store, data analysis has frequently shown the occurrence of this crash issue: 1. Crash Type: App Not Responsive Crash Reason: oculus:android_anr:com.google.androidgamesdk.GameActivity.onPauseNative 2. Crash Type： App Not Responsive Crash Reason：oculus:android_anr:com.google.androidgamesdk.GameActivity.onSurfaceDestroyedNative I suspect the issue occurs during user IAP (In-App Purchase) because I occasionally experience a crash when canceling a purchase.
Pas de disposition clavier Azerty
Bonjour La disposition azerty est indisponible pour clavier bluetooth logitech MX Keys S. Et ne me redite pas qu il ne fait pas partie de la liste des clavier pris en charge car vous annoncez que seul le Logitech MX Keys universel (graphite). Hors cette dénomination ne correspond à rien. (Je vous laisse vérifier sur le site de logitech) C est quand même pas normal quand 20224 un groupe comme meta ne soit pas capable de permettre la prise en charge de l azerty sur les claviers. Il faut arrêter d emmerder le monde avec le clavier qwerty. Sachant que tous les systèmes d exploitations prennent en charge les autres disposition sans qu on soit obligé de quémander sur un forum. Rembourser ou laisser vos ingenieurs bosser pour la prose en charge des autres dispositions.Rejected Applab Submission
Hello, Meta Quest Developers! I'm reaching out to you because my Applab submission has been rejected due to an issue with the "App Metadata," but I wasn't told specifically what the issue was. I have recently have gotten the game from a friend who told me everything being good, I'm a little confused on what needs to be changed in order to get it released. If you could clarify what I need to change, or how I can resolve this, I would greatly appreciate any feedback given that I have a community of over 60,000 users who are waiting to play the game again! Best regards, Protogen
