My project runs on Quest 2 at 18 FPS (GPU-bound), no matter the scene or XR Rig
Our game's Quest performance has always hovered around 36 fps while in development, which I've come to find out was due to high batch counts and complex lit material shaders on every object. But now that I'm back to testing optimization on Android, I've noticed terrible frame rates (10-18) no matter what I disable in the scene. I've even opened up the DemoScene from XR Interaction Toolkit, and it experiences the same unknown GPU-bound issue. Context about my project: Unity 6.0.59f2 running on a Windows 11 PC. Open XR project targeting a Quest 2 and SteamVR release. I have a ton of packages from the Unity Asset Store that I'm using to build the rig, environment, or mini games. I've kept them up to date, checked that they were Unity 6 compatible, and removed any unused packages. Things I've checked: I've used the What If analysis from the Quest Runtime Optimizer tool to find out that the one blank scene I was testing in had a total GPU Frame Time of 0.342 ms. Maybe you can help identify anything in the Renderdoc. Every little setting in Project Settings to be set up the recommended way. The only warnings left in my Meta Project Validation are about depth and opaque textures being on, which are required for Stylized Water 3 (an asset that supports Quest) to run. Also, one more warning about Screen Space Ambient Occlusion but from checking everywhere, that feature is off or deleted. Memory Profiling. RAM usage in these empty test scenes is at 1.54 GB and I've sat in the scene for 20 minutes before without it crashing or getting slower like a RAM overflow would do. There is no spamming of logs, warnings, or errors during runtime on the quest. I checked by turning on Script Debugging and connecting the editor's console to the headset's output. All I found were some regular logs on startup. Suspicious things I've noticed that only happen in my Quest builds (testing in-editor lacks these issues and runs above 50 fps): Dynamic Resolution falls to 0 for my game. But I'm curious if this is the reason for making foveated rendering glitch out so much so that the screen becomes super pixelated in vertical strips across the screen. Only when building will I be notified of shader errors from packages we've been setting up like GPU Instancer pro, Microsplat, and InfiniCloud. I mostly stop the errors by deleting sample packages that we didn't need or in one case commenting out a line of code with an error about fog in the universal render pipeline asset or something. Please help, I've worked on this for four days, and I'm at the end of what I know to try.Solved41Views0likes4CommentsAccessing system-wide performance metrics (like com.oculus.ovrmonitormetricsservice)
I’m developing an internal Kotlin app for Meta Quest that reports headset performance data to our servers. When running as a regular app, I can’t access the same system-wide metrics that com.oculus.ovrmonitormetricsservice logs every second. From adb shell logcat I can see the data, but from inside the app I get nothing — logcat access and /proc reads are restricted. I’ve also tried reading from Linux system files and running shell commands, but due to Android sandboxing I only get metrics for my own app process. Is there any supported way (API, permission, intent, or service binding) to access those metrics from a normal app, or is it limited to system-signed packages?27Views0likes1CommentSmart & Transparent Offline Messaging System" for Messenger
To: Meta Product Team (Messenger Platform & User Experience) From: Kenjie Lantape Agbu Date: October 14, 2025 Subject: Feature Suggestion: Implementing a "Smart & Transparent Offline Messaging System" for Messenger Dear Meta Product Team, I am writing to propose a new feature that I believe will significantly benefit millions of Messenger users, especially small businesses and individuals who utilize their personal accounts for commercial purposes. My proposal is to develop a "Smart & Transparent Offline Messaging System." This idea aims to upgrade the current "Instant Reply" and "Away Message" functionalities by focusing on two key aspects: Transparency and Intelligent Customization. A. Component 1: Transparency Disclaimer (Building Trust) The Current Problem: When an auto-reply is active, the recipient often cannot tell if the response is from a person or a bot. This leads to confusion, frustration, the common "seen-but-no-reply" annoyance, and a breakdown of trust. The Proposal: * Automatic Notification: Automatically append a small, non-intrusive disclaimer text to every automated message sent. * Suggested Text: "(Auto-Reply): The account owner is currently offline or busy. This is an automatic message." * Benefits: * User Trust: The communication becomes honest and transparent, fostering stronger trust between the sender and the recipient (and with the Meta platform). * Correct Expectation: Customers and friends immediately know when to expect a human response, drastically reducing frustration and miscommunication. B. Component 2: Smart & Contextual Reply Logic (Intelligent Responses) The Current Problem: Current automatic replies are often generic—one message serves all types of inquiries. This is ineffective because a single response cannot adequately address a "business inquiry" and a "personal greeting" simultaneously. The Proposal: * Customizable Response Templates: Provide users with the option to set up different categories of auto-replies (e.g., "Business," "Personal," "Urgent"). * Keyword Detection/Intent Logic: The Messenger system would use simple AI or user-defined keyword logic to categorize the incoming message before sending a reply. * Setup Example (for the User): * If the message contains keywords: "price," "how to order," "available," or "shipping" \rightarrow Use the "Business Reply Template." * If the message contains keywords: "how are you," "let's meet," or "where are you" \rightarrow Use the "Personal Reply Template." * Benefits: * Relevance: The response will always be appropriate to the query. Business queries get formal, informative answers, while personal messages get casual, friendly ones. * Professionalism: It prevents the awkwardness of a casual personal auto-reply being sent to a customer, or a formal business reply being sent to a friend. Summary: The Universal Benefit of this Feature Implementing the "Smart & Transparent Offline Messaging System" will enhance the entire Meta ecosystem: * For Business Users (Small Sellers): It improves their customer service 24/7. Leads receive instant, relevant information, which increases conversion rates and overall business efficiency. * For General Users (Customers/Friends): They experience a more professional and candid interaction on the platform. The speed of the response combined with the transparency of the bot usage enhances the overall user experience. * For the Meta Platform: This feature provides a significant competitive advantage, demonstrating Meta's commitment to providing advanced and user-friendly automation tools that support small businesses and organic communication flows. I sincerely hope you will give this suggestion serious consideration. I am available to provide any further details or clarification needed. Thank you for your time and attention to this matter. Sincerely, [Name Kenjie Lantape Agbu Email kenjieagbu227@gmail.com8Views0likes0CommentsUnity Builds Doesn't Open on V81.1034
Hey guys hope all are doing well, I am a beginner VR developer on Unity and been testing on quest 2 my oculus quest 2 just updated to version 81.1034 , ever since every time i try to build a new apk from unity as a i did before it just loads for a few seconds and then crashes out. I am wondering is this a bug in the new update cause it was working fine before , or is it a problem from my end ? Thank you !92Views0likes2CommentsExtremely poor Meta Support experience – ongoing ad payment issue for months without real resolution
I’ve been facing the same payment issue with one of my ad accounts for a long time. The issue: automatic payments from my card keep failing on one ad account, but the same card works perfectly fine for all my other ad accounts under the same Business Manager. Every time I contact Meta Support, they simply tell me it’s a bank issue. However, I’ve already confirmed multiple times with my bank that there are no restrictions or suspicious flags on my card. In fact, Meta’s backend team can manually process the payment successfully using the same card, which clearly proves the problem is not on the bank’s side. Every agent gives me the same repeated answer and closes the case without identifying the root cause or escalating it properly. I’ve gone through several agents and even the “specialized team,” yet no one provides a valid technical explanation or lasting fix. I spend around 200–300k MYR monthly across my ad accounts, and this repeated experience with Meta Support has been very disappointing. There’s no ownership, no follow-up, and no real investigation — only repeated replies blaming the bank. I’m sharing this here because I’ve exhausted all support options, and I hope this will reach someone who can actually look into the technical side of my issue instead of deflecting responsibility.Solved48Views0likes1Comment