Meta Quest AI Stack: What It Actually Means for Unity Developers
Hey everyone, Degly here! I’ve been working with the Meta Quest AI stack for a while now, and I wanted to share a straightforward overview of the real value for Unity developers. There’s a lot of excitement around AI tools in Quest development, but it can be hard to understand how they fit into your workflow. Meta Quest AI Stack: What It Actually Means for Unity Developers AI tooling is showing up everywhere in Quest and Unity development, but a lot of it gets explained in a way that sounds exciting without being very useful. This video is a plain-language overview of the current Meta Quest AI development stack. The goal is not to show a deep coding walkthrough or claim that AI will build your whole app. The goal is simpler: How can these tools reduce friction, speed up iteration, and help Quest developers move through setup, debugging, content changes, and handoff more efficiently? Video / resource link: WHO THIS IS FOR Unity developers building for Meta Quest. XR developers who keep hearing about AI tooling but do not know where to start. Developers who want faster iteration, not AI hype. Anyone who wants a practical mental model before trying MQDH MCP, Unity MCP, AI Building Blocks, or the Immersive Debugger. PRACTICAL TAKEAWAYS A simple explanation of the Quest + Unity AI stack: What MCP means in practical developer terms What MQDH MCP does What the Meta XR Unity MCP Extension is for What AI Building Blocks are Why Agents and Providers matter Where Unity Inference Engine fits Why the Immersive Debugger matters for headset-first debugging The main takeaway: this stack is not one magic tool. It is a practical workflow for reducing friction across the development loop. THE STACK AT A GLANCE The video focuses on four core pieces: MQDH MCP Unity MCP Extension AI Building Blocks Immersive Debugger High-level workflow: MQDH MCP helps you gather Quest development context. Unity MCP Extension helps automate repeated Unity editor tasks. AI Building Blocks help you add practical AI features. Immersive Debugger helps you inspect and validate behavior inside the headset. RELATED LINKS Meta Quest Developer Hub overview: Enable AI tools with MCP for Meta Horizon OS developers: Model Context Protocol introduction: Meta XR Unity MCP Extension docs: Meta XR Unity MCP Extension GitHub repo: AI Building Blocks overview: Agents and Building Blocks: Providers and Inference Types: Unity Inference Engine: Immersive Debugger overview: MR Utility Kit debug and testing: Dilmer Valecillos walkthrough: Meta Quest agentic tools GitHub repo: WHAT TO INCLUDE WHEN ASKING FOR HELP If you try one of these workflows and need help, include: Which part of the stack you are testing Unity version Meta XR SDK version Quest device model Whether the headset is connected and in developer mode Screenshot of the issue Relevant logs or error messages Whether the issue happens in Editor, on device, or both FAQ Should I use all of these tools at once? No. Start with the part that solves the problem you currently have. Is this a replacement for learning Quest development? No. It is a way to reduce friction around the workflow. Is MQDH MCP the same thing as Unity MCP Extension? No. MQDH MCP is more about external Quest context such as docs, logs, screenshots, and device workflows. Unity MCP Extension is more about repeated Unity editor tasks. Are AI Building Blocks only for cloud AI? No. The Agent and Provider model is useful because Providers can represent different inference paths, including cloud, local, or on-device options depending on the feature. Is Immersive Debugger an AI tool? No. It is a runtime debugging tool used inside the headset. It is included here because it helps complete the development loop. BOTTOM LINE This stack is not about AI for the sake of saying AI. It is about tools that help Quest and Unity developers: Move faster Test easier Debug more clearly Keep projects cleaner Reduce repeated setup work Validate behavior inside the headset The practical story is simple: use AI tooling where it reduces friction, and use headset-first debugging where the real XR behavior actually happens. Degly
Intro to Meta Quest Runtime Optimizer | Horizon Start Mentor Workshop
In this video, Start Mentor Sidney provides a comprehensive introduction to the Meta Quest Runtime Optimizer, a diagnostic tool designed to help developers identify and address performance bottlenecks in VR, AR, and MR applications. The talk covers everything from initial setup and system requirements to advanced analysis modes like “What If” testing, offering practical advice on how to integrate these tools into regular development workflows. This session was recorded in March 2026 as part of the Meta Horizon Start program. 🎬 CHAPTERS 0:00 - Introduction 1:18 - Installation and System Requirements 2:00 - Core Features: Bottleneck Analysis 2:52 - Advanced Testing: What If Analysis 4:29 - Optimization Principles and Diagnostic Work 5:33 - Workflow Integration: Level Development 6:43 - Workflow Integration: Feature Development 7:49 - Workflow Integration: Main Project Integration 🎮 FEATURED IN THIS SESSION ➡️ Meta Quest Runtime Optimizer 📚 RESOURCES ➡️ Meta Horizon Developer Forum: https://communityforums.atmeta.com/category/horizon-developer-forum ➡️ Developers Blog: https://developers.meta.com/resources/blog/ ➡️ Meta Quest Developer Hub: https://developers.meta.com/horizon/documentation/unity/ts-mqdh/ 🔗 CONNECT WITH US Sign up to get the latest news from Meta Horizon: https://developers.meta.com/horizon/newsletter 💡 LEARN ABOUT THE META HORIZON START PROGRAM The Meta Horizon Start program provides intermediate and advanced developers with hands-on support and expert guidance to accelerate app development. Join a thriving community to access the tools and go-to-market resources you need to successfully deploy and grow your app on Meta Horizon OS. Apply to Start today: https://developers.meta.com/horizon/discover/programs/start
Design with a Retention-First Mindset | Growth Series, Part 4
In this final session of the growth series, Meta Horizon Start Mentor Tevfik discusses how to transition from simply gaining views and installs to building a lasting player base through a retention-first design mindset. The presentation highlights the unique nature of VR as a social space where players return not just for gameplay, but for belonging and self-expression. This session was recorded in March 2026 as part of the Meta Horizon Start program. 🎬 CHAPTERS 00:00 - Introduction to growth series part 4: Retention-first design 00:43 - Defining the problem: Why growth without retention is just “churn.” 02:44 - VR as a “place”: Understanding why players return to socialize and show off 03:28 - The Retention Triangle: Direction, Identity, and Return 03:48 - Part 1: Direction—Implementing social daily challenges 04:30 - Part 2: Identity—The power of avatars, cosmetics, and visibility 05:41 - Case study: The success of the indie social VR game Blob Town 06:26 - Part 3: Return—Creating habits through weekly resets and update rewards 07:13 - The importance of “Social Moments” and the 3-second reaction rule 08:36 - Practical systems: Using "Drop Codes" to drive returns and community growth 10:55 - The Full Loop: Social moments as the engine for the player journey 12:34 - Action Items: Homework for implementing retention systems in 7 days 📚 RESOURCES ➡️ Meta Horizon Developer Forum: https://communityforums.atmeta.com/category/horizon-developer-forum ➡️ Developers Blog: https://developers.meta.com/resources/blog/ ➡️ Meta Quest Developer Hub: https://developers.meta.com/horizon/documentation/unity/ts-mqdh/ 🔗 CONNECT WITH US Sign up to get the latest news from Meta Horizon: https://developers.meta.com/horizon/newsletter 💡 LEARN ABOUT THE META HORIZON START PROGRAM The Meta Horizon Start program provides intermediate and advanced developers with hands-on support and expert guidance to accelerate app development. Join a thriving community to access the tools and go-to-market resources you need to successfully deploy and grow your app on Meta Horizon OS. Apply to Start today: https://developers.meta.com/horizon/discover/programs/start
Oakley Meta Glasses - 16:4 - Landscape
Tried searching for topics relating to this but unable to find anything. Dearly hoping that there are plans afoot for a firmware release from Meta that facilitates these great glasses with the ability to film in landscape mode. I am worried that this has been a massive oversight, a what could have been potentially the most revolutionary piece kit, might end up falling short at the last hurdle. If this is the case I might just have to offload them and switch back to my other action camera. Come on Meta, please shed some light on what may or may not be on the way... at least a little hint please.Turn Social Views Into a Lasting Community | Growth Series, Part 3
Are you struggling to turn viral VR views into an active, lasting community? In this session of the Meta Horizon Start program’s Growth Series, Meta Horizon Start Mentor and experienced VR developer Tevfik dives deep into the shift from simple visibility to true player retention in social VR games. Learn why most VR games fail not because they are bad, but because they disappear after the first impression. Tevfik shares a comprehensive five-step system to build a dedicated player base, covering everything from creating roles and moderator grinding to leveraging live streams, content creator programs, and consistent community events. Discover how to transform your VR game from just an experience into a thriving social system. This session was recorded in March 2026 as part of the Meta Horizon Start program. 🎬 CHAPTERS 00:00 - Introduction and Background in Social VR 01:02 - The Retention Problem in VR Development 01:44 - Shifting Focus to Human Progression and Community 02:27 - Step 1: Creating Identity and “Original Gangster” (OG) Roles 03:55 - Utilizing Early Access and Founders Bundles 04:32 - Step 2: Progression through Moderator Grinding 06:27 - Step 3: Establishing Presence via Live Streaming 07:36 - Step 4: Implementing a Content Creator Program 09:11 - Step 5: Hosting Consistent Community Events 10:01 - Case Study: Breaking CCU Records with a DJ Event 11:07 - Summary: Building Your VR Game as a Social System 📚 RESOURCES ➡️ Meta Horizon Developer Forum: https://communityforums.atmeta.com/category/horizon-developer-forum ➡️ Developers Blog: https://developers.meta.com/resources/blog/ ➡️ Meta Quest Developer Hub: https://developers.meta.com/horizon/documentation/unity/ts-mqdh/ 🔗 CONNECT WITH US Sign up to get the latest news from Meta Horizon: https://developers.meta.com/horizon/newsletter 💡 LEARN ABOUT THE META HORIZON START PROGRAM The Meta Horizon Start program provides intermediate and advanced developers with hands-on support and expert guidance to accelerate app development. Join a thriving community to access the tools and go-to-market resources you need to successfully deploy and grow your app on Meta Horizon OS. Apply to Start today: https://developers.meta.com/horizon/discover/programs/start
Live Events: Why, When, & How (Start Workshop)
Hosted by Gabe Heiland • March 2026 • Meta Horizon Start Overview In-game live events are a focused set of activities and rewards intended to drive engagement—specifically targeting acquisition, retention, or monetization. While many developers think of massive holiday updates when they hear “live event,” there are actually several low-cost, high-impact ways to run events. In this session, Meta Growth Consultant Gabe Heiland breaks down the six core event types, the best practices for designing them, and how to measure their success. Watch this part: 00:00 The 6 Event Types (Minor and Major) Minor Events (Low implementation cost, habit-forming) Server Booster Event: Data-driven tuning levers like “Double XP Weekend” or boosted crafting rarities. These are very lightweight to set up and are a great first event for a game. They should be rotated weekly at most so players don't become accustomed to the boost. Daily Goal Event: Layering a server-wide goal on top of your existing daily quest system to focus players on a specific mode or activity for a small reward. Leaderboard Event: Injecting competition into your game over a short period. Once the infrastructure is built, these can be reused weekly to drive engagement and monetization, even in single-player games. Major Events (High effort, high return on investment) Community Event: Collective objectives that require social cohesion (e.g., the entire player base must complete 10,000 matches to unlock a reward). These are viewed as very fair but usually require an out-of-game communication channel like Discord. Progression Event: Players fill a progress bar with active play and are rewarded at specific milestones. These ask a lot of players, so they require a cooldown period between runs. Seasonal Event: Massive, highly themed events aligned with real-world holidays. These drive the highest impact but are expensive to produce and carry the risk of only happening once a year. Watch this part: 02:15 Best Practices for Live Events Scheduling and Cadence In VR, a two-week cadence targeting weekend play sessions (aiming for about 4 hours of play per week) has proven highly effective. You want to build predictability to establish trust (players know an event will happen) while using the specific content of the event to provide surprise and delight. A good update rubric to aim for is: Daily: Progress to be made Weekly: Something new to see Monthly: Something new to do Quarterly: Something that changes how they engage Define KPI Goals First Before designing an event, decide if you are targeting acquisition (requires strong theming and key art for social media), retention (requires frequent, focused play sessions), or monetization (often features a competitive element where few players get all rewards). Set clear goals, like “100% of spenders and 20% of non-spenders should finish the event,” to guide your tuning. Lower the Barrier to Entry Players should be able to enter the event immediately after onboarding. The event should be front-and-center upon login, and the first reward moment should happen within minutes of playing. Always end events with a clear wrap-up, paying out any unused event currency. Expand the Player’s Comfort Zone Use events to incentivize trying new characters, modes, or underutilized content. However, avoid “anti-social mandates”—don’t force players to use a character that only one person per match can select, as it prevents friends from playing together. Watch for Exhaustion Player exhaustion happens when high-engagement events run too frequently without breaks. Team exhaustion happens when developers are constantly building bespoke content. To combat both, rotate your event types (alternating high and low effort) and templatize your events so they require minimal changes between reruns. Monetization Should Be an Accelerator, Not a Paywall Paradoxically, ensuring that non-spenders can earn all event rewards through heavy engagement actually improves monetization. When an event feels fair and skill-based, players are more willing to spend money to accelerate their progress. Avoid over-rewarding standard game currencies, and consider offering items that complete a set over multiple events. Watch this part: 08:50 Measuring Success To know if your event worked, you need to track specific KPIs. If you don't have your own in-game telemetry, you can use the pre- and post-event data available in the developer portal. Key benchmarks to watch for: Monthly Active Users (MAU): Strong live events can drive 3× or more MAU compared to surrounding months. Session Duration and Logins per Day: Both should increase during an active event. Day 7/Week 1 Retention: Should spike from your baseline during the event and settle back to normal afterward. Daily Revenue: Can see anywhere from a 1.5× bump for a minor weekend leaderboard up to a 600× increase for a massive holiday event. Content Consumption: The percentage of players who reach the end of the event and claim all rewards. This is your primary guide for tuning future events. Watch this part: 18:50
Overdraw Best Practices
Overdraw is a silent performance killer in VR development. In this workshop, Meta Horizon Start Mentor Sidney breaks down what overdraw is, why it drains GPU resources, and how to fix it in Unity. Learn why relying on Unity’s default settings (like a 1KM draw distance) or the SRP batcher isn’t enough to prevent overdraw. Sidney walks through practical, simple solutions including smart level design, utilizing occlusion culling (especially for indoor scenes), and leveraging the Unity Frame Debugger to catch pixel fill issues early in the greybox phase. The session also covers the specific challenges of overdraw in procedurally generated levels. This session was recorded in March 2026 as part of the Meta Horizon Start program. 🎬 CHAPTERS 00:00 - Welcome & Introduction to Overdraw 00:15 - Speaker Intro: Sidney (Angelsin) 01:14 - Defining Overdraw and the Rendering Pipeline 02:08 - The Performance Impact of Overdraw 02:50 - Unity's Role and Limitations in Handling Overdraw 03:19 - Risks of Mesh Combining and Dynamic Objects 04:03 - Demonstrating Overdraw with Scene and Debug Tools 06:15 - Reducing Overdraw: Adjusting Draw Distance 07:55 - Reducing Overdraw: Occlusion Culling 08:21 - Overdraw Challenges in Procedural Generation 09:10 - Using the Frame Debugger for Optimization 10:10 - Conclusion and Summary of Best Practices 🎮 FEATURED IN THIS SESSION ➡️ Unity Frame Debugger: https://docs.unity3d.com/Manual/FrameDebugger.html ➡️ Unity Occlusion Culling: https://docs.unity3d.com/Manual/OcclusionCulling.html 📚 RESOURCES ➡️ Meta Horizon Developer Forum: https://communityforums.atmeta.com/category/horizon-developer-forum ➡️ Developers Blog: https://developers.meta.com/resources/blog/ ➡️ Meta Quest Developer Hub: https://developers.meta.com/horizon/documentation/unity/ts-mqdh/ 🔗 CONNECT WITH US Sign up to get the latest news from Meta Horizon: https://developers.meta.com/horizon/newsletter 💡 LEARN ABOUT THE META HORIZON START PROGRAM The Meta Horizon Start program provides intermediate and advanced developers with hands-on support and expert guidance to accelerate app development. Join a thriving community to access the tools and go-to-market resources you need to successfully deploy and grow your app on Meta Horizon OS. Apply to Start today: https://developers.meta.com/horizon/discover/programs/start
The Data-Driven Advantage: A Practical Guide to Optimizing VR Games with Analytics
Discover how a strategic approach to analytics can move beyond “macro KPIs” and unlock actionable, game-specific insights that improve retention and overall product health. In this Meta Horizon Start session, Chong Ahn (Head of Games Growth & Monetization, Meta Reality Labs) explains how to: Build metrics that map directly to your game design (not just DAU/retention averages) Use player segmentation to understand different cohorts (new vs. veteran, spender vs. free, etc.) Identify “why” behind player outcomes by asking the right questions (success/failure rate, matchmaking balance, map routing, causes of death, and more) Turn findings into concrete gameplay adjustments that measurably shift outcomes The session includes a case study from the VR extraction shooter Contractors, showing how focusing on early-match success (and diagnosing bot difficulty + map routing issues) can significantly improve new player outcomes and long-term retention. This session was recorded in March 2026 as part of the Meta Horizon Start program. 🎬 CHAPTERS 👋 INTRODUCTION 00:00 - Introduction: Leveraging VR Games with Analytics 00:13 - The Importance of a Robust Analytics Pipeline 01:00 - Moving Beyond Standard KPIs to Tailored Metrics 01:43 - Foundations for Understanding Player Segments 02:44 - Case Study: New Player Segments in Extraction Games 04:25 - Aligning Data with Game Design and Business Health 06:00 - Case Study: Analyzing Retention in Contractors 08:03 - Identifying Issues in the New Player Funnel 09:22 - Investigating Player Causes 10:18 - Impact of Optimizing Bot Lethality and Map Routing 11:51 - Combining Adjustments for Significant Extraction Rate Increases 13:06 - Net Impact Summary: Increased Matches, Minutes, and Retention 14:02 - Building a Robust Data Pipeline Infrastructure 15:47 - Cost vs. Customization in Analytics Services 📚 RESOURCES ➡️ Meta Horizon Developer Forum: https://communityforums.atmeta.com/category/horizon-developer-forum ➡️ Developers Blog: https://developers.meta.com/resources/blog/ ➡️ Meta Quest Developer Hub: https://developers.meta.com/horizon/documentation/unity/ts-mqdh/ 🔗 CONNECT WITH US Sign up to get the latest news from Meta Horizon: https://developers.meta.com/horizon/newsletter 💡 LEARN ABOUT THE META HORIZON START PROGRAM The Meta Horizon Start program provides intermediate and advanced developers with hands-on support and expert guidance to accelerate app development. Join a thriving community to access the tools and go-to-market resources you need to successfully deploy and grow your app on Meta Horizon OS. Apply to Start today: https://developers.meta.com/horizon/discover/programs/start
Crafting Social Content Players Want to Watch (Growth Series Part 2)
Hosted by Tevfik • March 2026 • Meta Horizon Start Overview As developers, we often assume that posting game updates or announcing new features will naturally excite our community and attract new players. The reality is that standard development content rarely travels far online. To achieve true organic growth, your game needs to be more than just fun to play—it needs to be fun to watch. In this session, VR developer Tevfik explains the core principles of “watchability” and how to design mechanics that naturally encourage players to create and share clips of your game. Watch this part: 00:00 The Problem with Traditional Updates When you push an update, the real question isn’t “What feature did we add?” but rather, “Would someone send a clip of this update to a friend?” If the answer is no, your game will struggle to spread on social media. Successful social VR games recognize that their community is their most powerful marketing engine, and they design their gameplay to fuel that engine. Watch this part: 01:00 What is Watchability? Watchability is the secret sauce that turns gameplay into shareable content. Watchable gameplay consistently creates moments that are: Surprising Emotional Funny Chaotic When these four elements combine, players naturally want to hit record. Watch this part: 01:45 Designing for Clips: Three Key Elements 1. Social Chaos Unpredictable player interactions create the best content. Mechanics that lead to physics accidents, unexpected teamwork, hilarious betrayals, or genuine panic (like monsters that kill you instantly) result in players screaming and laughing. These moments are incredibly entertaining for viewers, not just the players experiencing them. 2. Emotional Reactions VR is a uniquely powerful medium for content creation because player reactions are highly visible through avatar body language. When a player experiences panic, laughter, or surprise, viewers instantly understand the emotion of the moment. Strong avatar expressiveness amplifies this effect. 3. The Stage Effect Great social VR environments function like performance stages. By providing the right tools and spaces, players will naturally perform stunts, tell jokes, complete challenges, and create memorable social moments. They transition from simply being players to becoming content creators inside your game. Watch this part: 04:00 Building the Viral Loop and The Watchability Test When you successfully implement watchable mechanics, you create a powerful viral loop: A unique gameplay moment occurs -> A player records a clip -> The clip spreads online -> New players discover the game -> The community becomes your marketing engine. Before you spend time developing and shipping a new mechanic, run it through the Watchability Test: “Would someone clip this? Or would someone send this moment to a friend?” If the answer is yes, that mechanic has strong viral potential and is worth your time. Remember, your game isn’t just competing with other VR titles—it’s competing with everything else on the internet for a viewer’s attention. Watch this part: 06:15
