HorizonOS v81 update broke Passthrough in startup Splash Screens
Hi folks, This is for a project in a C++ UE 5.5.3-0+oculus-5.5.3-release-1.109.0-v77.0 engine from official Oculus Branch. A recent update to Horizon OS, likely v81, seems to have changed the way Splash screens are handled to now send the user to a black void with particles and wisps flying by. This has created a big problem for our MR application in that now NO Passthrough is visible during splash, which is causing us to fail VRC (Functional.14). This was not an issue before this OS update. These are the settings and image (PNG with transparency) we are using: Even forcing bAutoEnabled to True in DefaultEngine.ini does not help: Setting to Black also gives the same result, which is the black void with a very low resolution proxy of the PNG we have: For reference, this was the behavior before the v81 update: We also scouted other MR apps and it seems they face similar situations (?) Any help is appreciated as we'd rather not request any waivers during our QA process. Thank you! -SebastianMQDH Fails to upload to Rift Store
I have been trying for months to upload our PCVR game to the Rift/PCVR store. The MQDH keeps failing. There was a time when it worked but only by giving you an error claiming it didn't... then by chance it seemed to succeed in the background anyway. Now it's not working at all. I have been using MQDH to upload the Quest version just fine for years, so I know what I'm doing. But perhaps there's something undocumented that's different about the PCVR upload process? I have asked about this in numerous places and had no consistent working answer. I'd appreciate someone who knows what they're doing getting on a call with me to for 5 minutes to resolve this. Our launch has already happened on other platforms, and Meta's PCVR store is getting left behind due to this.
[Concept] The Real Life (RPG) – Verified Real-World XP System for Meta Quest & Ray-Ban Glasses
Hello Meta Developers & Reality Labs Team, I’d like to share an independent XR concept called “The Real Life (RPG)” – a system that verifies real-world actions (reading, mindfulness, learning, encounters) as XP points through eye-tracking / voice analysis / AR context awareness. It encourages people to grow through reality – not escape from it – by merging self-development with augmented reality. The project supports Ray-Ban Meta Glasses (no eye-tracking, voice fallback) and Quest Pro (eye-tracking). → Full concept PDF attached by Kontakt Would love to connect with Reality Labs Partnerships or Developer Relations to explore a pilot integration. Best regards, Philipp M.
Smart & 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.comApp Name Violation Issue on already accepted submission
Hello, We have already released Demo of our game on the Meta platform, and we also have a store page for the upcoming full release of the game, currently listed as “Coming Soon.” Recently, I tried to edit some details on the main page (specifically to update the supported devices), but our submission was revoked with the reason: “The app name violates our content guidelines.” This puts us in a difficult position, as we have been using this name across all our channels and already have a growing community of players, fans, and YouTubers following our game. The name was previously approved both for the demo page and the main page when we first published them. Does anybody had similar problem?
MQDH PCVR Fails / CLI PCVR Upload Fails
I'm used to uploading the Quest version of our game via MQDH, and that works. But I'm trying to upload the PCVR build to the Rift store and facing an error. It has been suggested that I try CLI in Powershell, which I'm trying... but I don't think I've quite got it working. At first it was too quick and can't have uploaded 4GB, and now it's not showing progress after about 40 minutes. I'm just looking for a way to upload the game files to the Meta Server. Is there a guide or a video or someone that can help? Conversations on Discord: https://discord.com/channels/516966070448553994/518894436927668244/1423781143244836915 https://discord.com/channels/516966070448553994/516966070448553997/1423820778897412268 Case 00003466
