Forum Widgets
Recent Discussions
Quest Runtime Optimizer cannot analyze frame capture on Quest Pro v79.1029
I'm getting errors analyzing captures, and after a day spent debugging, it seems to have started with the latest headset update. An untouched project that previously had no problems has the error now after the headset update. There seems to be an error caused by format incompatibility with the trace_processor_shell version (v46.0) and the Core SDK 70+ which causes the python script to crash? (Don't ask me the details, I'm just a tech artist trying to get frames benchmarks here). I'm running the following: Unity 6.1 and 6.2 on Windows 11 Quest Pro (updated to v79.1029 on Aug 25, the date the error started appearing) Here is the error text: MetricAPI: 68AE8CCB.json execode: 0 single positional indexer is out-of-bounds Traceback (most recent call last): File "C:\open\fbsource\arvr\projects\integrations\Unity\RuntimeOptimizer\Editor\PerformanceInsight\MetricAPI.py", line 1118, in main File "pandas\core\indexing.py", line 1191, in __getitem__ File "pandas\core\indexing.py", line 1752, in _getitem_axis File "pandas\core\indexing.py", line 1685, in _validate_integer IndexError: single positional indexer is out-of-bounds UnityEngine.Debug:LogError (object) Meta.XR.RuntimeOptimizer.Core.Util:DebugLogError (object) (at ./Library/PackageCache/com.meta.xr.runtimeoptimizer@e44a64bf5ef6/Core/LogUtils.cs:19) Meta.XR.RuntimeOptimizer.Editor.PerformanceInsight.MetricAPI:GetCaptureMetric (string,string) (at ./Library/PackageCache/com.meta.xr.runtimeoptimizer@e44a64bf5ef6/Editor/PerformanceInsight/MetricAPI.cs:68) Meta.XR.RuntimeOptimizer.Editor.PerformanceInsight.CaptureTool:ProcessCaptureToJsonObjFunc (object) (at ./Library/PackageCache/com.meta.xr.runtimeoptimizer@e44a64bf5ef6/Editor/PerformanceInsight/CaptureTool.cs:787) System.Threading._ThreadPoolWaitCallback:PerformWaitCallback ()
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 everyoneFIX YOUR LINK SOFTWARE
PCVR with Link is the absolute worst software I have ever used almost daily I will be in iRacing and the Link glitches out, the entire community knows it's trash and always suggest using Virtual Desktop. I Have recently purchased a Bigscreen Beyond 2 headset and will never use Quest again constant software updates and glitches. learn how to code software that doesn't suck.
FIX THE ISSUE THAT RESULTS IN CONTROLLERS FAILING ON REGULAR BASIS
Why is meta unable to address the serious problem with controllers failing or bricking, or purple lights of death? Replaced mine 3x in month and keep getting refurbished junk. what is meta doing about this? It's costing me time, money, and a ton of frustration with terrible support & constant down time. I paid $500 for this thing but have maybe 3 full months of play time over 10 months. How is this OK?
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! FredS2S REST request not working on some users
So I have a backend for my game and I want to call some S2S requests to get user's data, purchaes and verify purchases. I am using the end point https://graph.oculus.com/${APP_ID}/viewer_purchases to get user's purchases. I provide access_token, user_id, and fields. Just like it mentions in the documention for IAP here https://developers.meta.com/horizon/documentation/native/ps-iap-s2s. The requests are working just fine with some users, but sometimes i enter a user id and get this error: here is an example of it working: if i just enter a random user id: (translation: it says thats an invalid user id) This is not just for this user, it happens for many users. Also it is happing for other requests like https://graph.oculus.com/${USER_ID} to get verified org_id and in consuming and verifying requests. I know that some of these requests dont work for meta test users (users that meta itself uses to test the game) but these users are real players. If anyone has any idea why this is happening please let me know. Side note: the consume_entitlement request also doesn't work sometimes where it throws a 500 is_transient error with code 2 but it still consumes the purchase correctly. weird...MQDH 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!
Consume entitlement on the server error
I'm trying create servers side logic to consume entitlement, like in this documentation: https://developers.meta.com/horizon/documentation/unreal/ps-iap-s2s#consume-an-iap-item I test calls on my computer first, using cmd. And when I try to consume - it returns an error. But consumable item is consumed in the end. Full log is shown on the screenshot Verify that user has this item - true All user purchases Consume - error Verify that user has this item - falseLobby Tutorial
Hi, I've just been through the lobby tutorial (Meta Developers) and found the following invalid snippet: (this.props.matchSpawnPoint as any).as(hz.SpawnPointGizmo).teleportPlayer(enteredBy); It should be: (this.props.matchSpawnPoint as any).as(hz.SpawnPointGizmo).teleportPlayer(player); Also on the same page there is a step to add a single property however in the screenshot you add both properties this could be a little confusing for someone new when they only add the property like asked.
