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 ()
S2S 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!
Advanced GPU OVR metrics not working
I've been using OVR Metrics HUD with the advanced GPU metrics since it was made available, and for the most part it has worked very well. Lately though it just stopped working and is giving me garbage values, and I've tried factory resetting, downloading older versions of it, enabling different settings in different orders and nothing is working for me! It's something that I really need to be able to work efficiently so if anyone could help out it'd be amazing!
Add Chinese input method for Chinese players
Can you add Chinese input method for Chinese players? Now more and more Chinese players have purchased quest3 and quest3s. Although a series of troublesome operations such as VPN are required, the quest equipment is very good, and more and more players are joining the quest. However, more and more Chinese players have reported that the system does not have a Chinese input method, which has a great impact on social aspects, such as Bilibili, the largest video platform in China. I found that YouTube VR has a Chinese input method, so this should not be difficult for developers. I hope developers can add a Chinese input method for Chinese playersWindows Volumetric Apps on Meta Quest announced for Developers
Microsoft announced Volumetric Windows apps are coming to Meta Quest at Build today. If i'm understanding it correctly, it looks like Developers that currently have mixed reality Windows apps or 3D objects can extend interaction to the Meta Quest from their Windows machine or Windows 365 via a new volumetric API. The screenshots show several virtual application windows open, with a 3D Xbox controller model being handled by the user and dismantled virtually. This is the sign up for the developer preview: https://aka.ms/VolumetricApps Video demo: https://x.com/SadlyItsBradley/status/1792974464424317307 Meta & Microsoft: The Future of Mixed Reality and Productivity - Developer session at Microsoft Build 2024 https://www.youtube.com/watch?v=ev3vsv5fdrE Creating Immersive 3D Solutions with Microsoft Mesh - Developer session at Microsoft Build 2024 https://www.youtube.com/watch?v=Q5LUtwjobgA Build Day 1 : https://www.youtube.com/live/2bnayWpTpW8 Build Day 2: https://www.youtube.com/live/FwJ1Zz_DntY Build Day 3: https://www.youtube.com/live/8Zy9QtZ6czE Bring Your Mobile Apps to Meta Horizon OS Developer Sign up https://developers.facebook.com/m/spatial-app-framework/ Sources and further details https://blogs.windows.com/windowsdeveloper/2024/05/21/unlock-a-new-era-of-innovation-with-windows-copilot-runtime-and-copilot-pcs/ https://www.meta.com/en-gb/blog/quest/meta-horizon-os-open-hardware-ecosystem-asus-republic-gamers-lenovo-xbox/ https://www.roadtovr.com/microsoft-meta-windows-3d-apps-quest/ https://www.uploadvr.com/microsoft-windows-volumetric-apps-quest/ https://www.techopedia.com/news/microsoft-extends-windows-apps-in-3d-on-metas-quest-headset https://www.digitaltrends.com/computing/microsoft-windows-volumetric-apps-coming-to-meta-quest-3 https://techcrunch.com/2024/05/21/microsofts-new-volumetric-apps-for-quest-headsets-extend-windows-apps-into-the-3d-space https://www.theverge.com/2024/5/21/24161817/microsoft-windows-volumetric-apps-meta-quest-apiYou need to use a Theme.AppCompat theme (or descendant) with this activity.
App crashs on start with this error "You need to use a Theme.AppCompat theme (or descendant) with this activity." I have Oculus auto-generated manifest: <?xml version="1.0" encoding="utf-8" standalone="no"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" android:installLocation="auto"> <application android:label="@string/app_name" android:icon="@mipmap/app_icon" android:allowBackup="false"> <activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:configChanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:launchMode="singleTask" android:name="com.unity3d.player.UnityPlayerGameActivity" android:excludeFromRecents="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> <category android:name="com.oculus.intent.category.VR" /> </intent-filter> <meta-data android:name="com.oculus.vr.focusaware" android:value="true" /> </activity> <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" /> <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only" /> <meta-data android:name="com.oculus.ossplash.background" android:value="black" /> <meta-data android:name="com.oculus.supportedDevices" android:value="quest2|questpro" tools:replace="android:value" /> </application> <uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" /> <uses-feature android:name="com.oculus.feature.PASSTHROUGH" android:required="true" /> </manifest> My specs: Unity 2023.2.6 Quest 3 Plugins: Meta XR Core SDK 64.0.0 Meta XR Haptics SDK 64.0.0 Meta XR Platform SDK 64.0.0 Mera Avatars SDK 24.1.1 OpenXR Plugin 1.9.1
The system incorrectly closes background programs, video, and sound.
I will use it for work 我會用它來工作 I need to switch between multiple apps frequently 我需要經常在多個應用程式之間切換 Need to hear all software sounds at the same time 需要同時聽到所有軟體的聲音 The new version of the system will automatically turn off background program sounds 新版本系統會自動關閉背景程式聲音 The background program did not crash and you can see that the program is still running.後台程式沒有崩潰，可以看到程式還在運作 I need to be able to hear the sound in the next version so I can do my job 我需要能夠在下一個版本中聽到聲音，這樣我才能完成我的工作 Maybe you could set a switch to choose which sounds are heard at the same time 也許你可以設定一個開關來選擇同時聽到哪些聲音 QUEST 3, to me, is not a toy, but a working tool QUEST 3 對我來說不是玩具，而是工作工具 Thanks[Noob Question] Is Native deprecated
I was reading this tutorial https://developer.oculus.com/documentation/native/xrsim-native/ It seems like the setup progress has changed quite a bit from when the documentation is written. I try to find more resources on it but on youtube it really only have tutorials for the unity setup. I managed to install the Meta XR Simulator, but can't find resources on how to launch it or any resources that I can read up on will be appreciated
