My reports
Submit feedback

VR

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers
0
Incorrect Percentage Values in Performance Analyzer
Investigating
Issue
1 report
Created about a day ago
The Performance Analyzer in Meta Quest Developer Hub displays incorrect percentage values for GPU and CPU utilization metrics. Specifically, GPU Utilization shows 9,754% instead of 97.54%, and CPU Utilization shows 10,000% instead of 100.00%. This suggests a decimal point or scaling factor error in the display logic. Notably, the OVR Metrics Tool overlay displays the correct percentage values for the same metrics, indicating that the underlying data collection is accurate but the Performance Analyzer graph rendering applies incorrect formatting or multiplies values by 100 erroneously.
Add your report
Subscribe
Suggest an edit
Copy link
0
Expand Preset Avatar Options for NPCs in MR Applications
Investigating
Issue
1 report
Created about a day ago
Developers require additional preset avatar options for Non-Player Character (NPC) use in Mixed Reality (MR) applications. Currently, preset avatars are tied to player accounts, limiting the number of available options for NPC characters. This restriction hinders the development of immersive storytelling experiences. A requested feature is to enable the creation of preset avatars not associated with player accounts, allowing for more varied and extensive NPC character design.
Add your report
Subscribe
Suggest an edit
Copy link
0
User Reporting Fails with "Error performing query" on Meta Quest 2
Investigating
Issue
1 report
Created 3 days ago
The issue occurs when attempting to report another user in a multiplayer session on Meta Quest 2, Horizon OS v207, Meta XR Platform SDK 205.0.0, and Unity 6000.5.6f1. The Meta reporting panel opens and displays the target user correctly, but submission fails and the panel closes without invoking the completion callback, resulting in no success, error, or cancellation result being returned. The issue is reproducible bidirectionally between accounts, persists after device restarts, and is also observed in Meta's native system menu Report function. System logs indicate a "Class not found when unmarshalling" and "Failed to parse item platform_result_receiver, returning null" error during the affected flow. Additionally, the people search within the reporting flow cannot find users in the same multiplayer session.
Add your report
Subscribe
Suggest an edit
Copy link
0
Meta Quest Link App Crash Loop
Investigating
Issue
1 report
Created 4 days ago
The Meta Quest Link app crashes immediately on launch and enters a crash-restart loop, failing to stay open. The issue persists despite standard troubleshooting steps, including repair, uninstall/reinstall, and system reboots. The crash occurs consistently on every launch attempt, indicating a potential issue with the application's stability or compatibility.
Add your report
Subscribe
Suggest an edit
Copy link
0
WebXR Immersive VR Session Startup Delay on Meta Horizon Link 207
Investigating
Issue
1 report
Created 6 days ago
The startup of a WebXR immersive VR session in Chrome on Meta Horizon Link 207.0.0.133.434 is delayed by approximately 55 seconds due to repeated failures in creating named pipes by Meta RuntimeIPC. The failures occur because the pipe names lack the LOCAL namespace prefix required for AppContainer compatibility. This issue arises when Chrome's Isolated XR Device Service runs in an AppContainer sandbox, triggering 11-second retry cycles before xrCreateSession completes. The problem is observed with Chrome version 153.0.8010.36 and flags --force-webxr-runtime=openxr --enable-features=WebXRIncubations enabled. Disabling the sandbox with --no-sandbox allows IPC initialization to complete successfully in about 1 second without retry failures. The issue is specific to running on a Quest 3 with a Windows PC and is not resolved by flags --disable-features=XRSandbox, --disable-gpu-sandbox, --disable-utility-sandbox.
Add your report
Subscribe
Suggest an edit
Copy link
1
MQDH Connection Issue with Quest 3 on NVIDIA RTX 5090 GPU
Investigating
Issue
1 report
Created 7 days ago
The Meta Quest Developer Hub (MQDH) is unable to connect to a Quest 3 headset, resulting in a permission error despite granted permissions on the device. Additionally, Horizon Link fails to establish a connection. This issue occurs on a PC equipped with an NVIDIA RTX 5090 GPU, suggesting a potential compatibility problem with newer graphics hardware affecting USB or display link connectivity between the headset and PC.
Add your report
Subscribe
Suggest an edit
Copy link
0
MCPBridge TestRunnerTools Performance Degradation in Unity Test Runs
Investigating
Issue
2 similar reports
Created 7 days ago
The MCPBridge TestRunnerTools in com.meta.xr.sdk.core version 205.0.0 causes severe performance degradation in Unity test runs due to two defects: (1) OnTestFinished re-serializes the entire accumulated result list to EditorPrefs on every test completion, creating O(n²) overhead on the main thread; (2) _cachedResults is never cleared between runs except when using the MCP tool entry point, causing unbounded accumulation. This results in significantly increased test run duration, with one test suite growing from 10s to over 3 hours, and EditorPrefs reaching 26MB and 103,800 records, with 99.8% of wall-clock time spent on callback overhead. This issue affects both EditMode and PlayMode tests run from the Test Runner window or batchmode, and is observed in Unity version 6000.6.0f1 on Windows 11.
Add your report
Subscribe
Suggest an edit
Copy link
0
Controller Orientation Flip with Meta SDK Core in Unity OpenXR
Investigating
Issue
1 report
Created 8 days ago
When using Meta SDK Core for Application SpaceWarp (AppSW) functionality on Quest 3 in Unity 6.2 with OpenXR 1.16.0 (or 1.15.1 with Meta SDK v85), the controller tracking orientation is flipped 180 degrees on the Y-axis. This issue occurs after adding Meta SDK Core to enable SpaceWarp, despite SpaceWarp itself working correctly. The problem persists across multiple configuration attempts and has been attributed to Meta SDK by Unity, which has declined to fix it.
Add your report
Subscribe
Suggest an edit
Copy link
0
Rift/PCVR Apps Missing from Meta Horizon Desktop Store Search
Investigating
Issue
1 report
Created 8 days ago
Recently published Rift/PCVR apps are not appearing in Meta Horizon desktop app store search results, despite having live, publicly accessible Product Detail Pages. This issue affects apps published around late 2024, while older Rift titles from 2022 are searchable normally. The problem seems to be correlated with the publication date rather than metadata configuration. Notably, recently published PCVR Product Detail Pages (PDPs) use a `/pcvr/`-scoped canonical URL path, whereas older Rift listings use the unified `/experiences/` path. This suggests that recent Rift SKUs may exist in a legacy index that the desktop client's search does not query, causing the apps to not appear in their assigned store categories or in search results, even with exact title searches or keyword variants.
Add your report
Subscribe
Suggest an edit
Copy link
0
Arabic Language Support Request for Meta Quest and Horizon OS
Investigating
Suggestion
1 report
Created 8 days ago
The request is for full Arabic language support in Meta Quest and Horizon OS, including complete Arabic localization of system interfaces, RTL UI support with mirrored layouts, Arabic virtual keyboard, bidirectional text rendering and input, Arabic search and text entry in the Meta Horizon Store, Arabic support for Meta AI including text and voice interaction, Arabic voice recognition and speech services, and localization of notifications, accessibility features, and help content. The request specifies Modern Standard Arabic as the primary system language with regional Arabic speech varieties for voice/AI services.
Add your report
Subscribe
Suggest an edit
Copy link
Load more
Reset to default

Sort

Type

Platform

Category

Status

Nav Logo
English (US)
© 2026 Meta