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!!!
3D model of the room
I started developing for Quest3 but I'm stuck and not making much progress... So far, I've got pass-through working and added collision detection to the scanned room model. Next, I want to bring the scanned 3D model into a Unity scene so I can edit it, but I'm stuck because I don't know how to do it... Any ideas on how to make this work, or even a little advice, would really help.
Detect Ui Changes on my app
Hello im a beginner and not familiar with coding apps for the quest. Im making an app in android studio and looking to figure out how to detect ui changes inside the meta os home interface. Like the windows and these events: Launched. Hidden. Closed. and the window name for each event I've been trying to figure this out but I'm clueless and only managed to detect it for some of the windows: store camera people profile horizon feed browser. But not quick settings notifications settings library. I need overall help on where to begin with this and if it doesn't violate any rules or anything.
Shared Mode - storing app data across sessions
We’re working on integrating a new license system for our VR training app and were hoping to get insights on two related issues we’re facing — particularly in the context of Meta for Work (MHMS). Accessing MHMS Distributed Files We’d like to support large-scale deployments by allowing customers to deploy encrypted license files to headsets via Horizon managed services (there us an option there to deploy files to devices). File distribution itself works fine, but we haven’t found a way to read these files from within the app at runtime, i.e. to have the proper permissions to read those files. Do you have any guidance on how to access these files from the app? Storing License Info Locally We also want to store license data locally on the device after activation (while online, in the case were they do not want to distribute license files), so the app can validate the license even when the device is offline. This is essentially the same encrypted data as the distributed file, just generated online and then downloaded to the device. Is there a supported way to persist such data locally on MHMS-managed devices? We’re aware that local storage is very restricted across sessions, so we’d love to know if there is a way (now or with a future update). A work-around is keeping users in the same session, but that's not really ideal as users always will have the option to end a session. For now we will be requiring MHMS devices to be online, but that's not a solution viable on the long term where you will also see devices being used offline. MHMS itself now supports offline use. If there is a solution (so my first question and maybe to my second) this could also be used for trained led courses where the trainer sets the training options for a training session or even for the organization as a whole (think language and other regional options). Hopefully someone can provide some insights.
New Loading/Splash Screen
Hello, the system splash screen behavior was recently updated. In the past the image supplied by the App would be shown centered on black with the three loading dots below and the size of the logo was pixel perfect so changing the resolution would change the display size. As described here: https://developers.meta.com/ Now after the recent update, the system shows this new fancy animated light rays thing and the image is scaled to fill the entire screen width, i think.. It's very large now and as a result it's very blurry. I was wondering if there is any updated documentation with newer recommendations on what resolution to use now or how the behaviour has changed. I want to avoid submission problems by just guessing, thanks everyone
Where to find footage of in-app PackageInstaller
Hi, I'm making a game where the "hub" area downloads and installs separate SDKs, basically as community-created levels. I understand there's two ways to install APKs The intent way Intent intent = new Intent(Intent.ACTION_VIEW); intent.setDataAndType(apkUri, "application/vnd.android.package-archive"); intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK); intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION); startActivity(intent); The package installer way PackageInstaller.SessionParams params = new PackageInstaller.SessionParams( PackageInstaller.SessionParams.MODE_FULL_INSTALL); int sessionId = packageInstaller.createSession(params); PackageInstaller.Session session = packageInstaller.openSession(sessionId); // write your APK bytes to session.openWrite(...) Intent intent = new Intent(context, YourBroadcastReceiver.class); PendingIntent pendingIntent = PendingIntent.getBroadcast(context, 0, intent, PendingIntent.FLAG_UPDATE_CURRENT); session.commit(pendingIntent.getIntentSender()); Now I currently have things working with the intent method, though the "do you want to install this package" system dialogue that pops up is a big pain point, as it leaves naive users confused (especially with how to close it). I hear the package installer method still does show a prompt, but that it apparently "more tied to the app" ad "more integrated with the session"... though I'm not sure what that means. Does anyone know where I can find footage of the application running inside a Quest3, installing and showing the dialogue via the package installer? I'd really like to see how it looks before dedicating dev time to reworking it all Cheers! FredMQDH Won’t Connect Quest 3 at Final Cable Step Despite USB and ADB Working
Hello everyone, I’m encountering a frustrating issue with Meta Quest Developer Hub (MQDH) v5.7.2 on macOS while trying to set up a Quest 3 running firmware V78. ISSUE DESCRIPTION I enabled Developer Mode on Quest 3 via the mobile app. In the Quest headset, I selected “Always allow USB access.” SideQuest and ADB (adb devices) can successfully detect the Quest 3. However, when I run “Set Up New Device” in MQDH, it stalls at the final step asking me to plug in the cable, even after doing exactly that. No prompt appears inside the headset; MQDH hangs without progressing. I tried reinstalling MQDH and rebooting both Mac and headset—problem persists. WHAT I’VE TRIED Verified Developer Mode is enabled, and USB Connection Dialog permission is granted. Confirmed USB‑C cable works (SideQuest and ADB both connect). Rebooted Quest and Mac multiple times. Uninstalled and reinstalled MQDH, cleared caches/settings. Used both bundled Quest cable and a known good USB‑C data cable (I tested USB 3.2 cable / Thunderbolt cable with Mac mini USB‑C Thunderbolt port). adb works fine. REQUESTED HELP Could someone please advise on potential causes why MQDH stalls even though ADB and SideQuest work? Has anyone else experienced this on Quest 3 running firmware V78 with MQDH 5.7.2? Are there any logs or advanced diagnostics I can capture to pinpoint the blockage? If anyone has successfully connected MQDH after the V78 update, what steps resolved it? FULL ENVIRONMENT INFO Headset Firmware: Quest 3 V78 MQDH Version: 5.7.2 (macOS) OS: macOS (latest version) USB cable: Verified data-capable USB‑C ADB Output: adb devices correctly lists the headset (adb cmd / MacDroid) MQDH Behavior: stuck at final prompt, no progress NEXT STEPS I’m considering doing a factory reset and strictly following the community-suggested flow (skip Air Link until first USB prompt), but not sure if firmware V78 changed behavior. Thank you in advance!