Unity XR Updates - April 2025

Hi! My name is Matt, and I’m on Unity’s product management team looking after our support for XR development. I’ve been doing this for seven years now, and watching the XR developer community grow and support each other has definitely been a highlight.

Many of you were around when we transitioned from the Unity Forums to Unity Discussions, and you may have felt that navigating information on this platform has been a bit more challenging.

Our goal is to get in the habit of informing the community of key product updates, sharing our latest plans and resources to aid in your development, and adding more structure around our communications in this forum.

So without further ado, here are some exciting updates:

Unity 6.1

Unity 6.1 is now available, and it’s packed with new features that support XR development! Here are the highlights:

Mixed Reality

With platforms continuing to invest in mixed reality, we’ve made a lot of progress expanding support for mixed reality features through AR Foundation and OpenXR so that developers have a consistent way to implement these features across multiple target platforms. In Unity 6.1, we added:

  • AR Foundation (v6.1)
    • Batch operations for persistent anchors
    • Expanded support for Vulkan with ARCore
  • OpenXR: Meta (v2.1)
    • Support for Quest Link when using AR Foundation
    • Stereo occlusion
    • Ability to enable boundaryless experiences
  • OpenXR: Android XR (v0.4)
    • Plane tracking
    • Face tracking
    • Stereo occlusion
    • Anchors
    • Note: This package is experimental
Input & Interactions

We’ve also added a number of enhancements to the XR Interaction Toolkit so that developers have a framework for building interactions that work across multiple target platforms. In Unity 6.1, we added:

  • XR Interaction Toolkit (v3.1)
    • Improved UI for the XR Interactions Simulator
    • Controller manipulation for the Near-Far Interactor
    • Two new ways to add basic jumping and gravity logic
XR Rendering Performance

Graphics rendering innovation to optimize performance is key for XR. With headsets relying on mobile GPUs, memory bandwidth is a huge bottleneck and even more so for headsets because of stereo rendering and high display resolutions. Thankfully, Vulkan was designed around this problem and offers many ways to optimize around this. In Unity 6.1, we added features aimed at helping developers utilize these optimizations to help boost performance for a wider range of features in URP.

  • OpenXR (v1.14)
    • Multiview Render Regions to accelerate rendering to eye textures
    • URP Application SpaceWarp supports RG16f texture format
Build Profiles

Lastly, Unity 6 introduced the concept of build profiles which are a set of configuration settings that you can use to build your project for a particular platform. In Unity 6.1, it’s easier than ever to get started building for XR with two new pre-configured build profiles: one for Meta Quest and one for Android XR. These build profiles bring required and recommended XR packages into your project and start with optimum player and graphics settings for great performance out of the box.

Check out our blog post for even more information on what’s new in Unity 6.1.

Looking Ahead

Our goal is to help you build innovative experiences that shine, through features & optimizations that accelerate your development cycles, expand the path to better graphics performance, and enable support for new devices & features. You can learn more about our roadmap here, where you can also share feedback and/or feature requests.

Unity Discussions

Getting Started

New to XR development? Read more about Unity’s support for XR in our documentation, and get started with one of the XR templates in the Unity Hub.

Posting Topics

Please keep your new topics specific and try to ensure you are not duplicating an existing topic. Here are some topic themes to guide you:

  1. Features and workflows: Are there any workflows that are unclear or missing? Are there any features that you expected to see, but didn’t? Can you share a clever workaround for an issue that you think may help others? To submit a direct feature request to Unity instead of posting a topic, you can [submit your request here].
  2. Performance: Are there performance issues you’re running into, and in what context?
  3. Use cases: What are your use cases? Can you share a video demo of what you’re working on? We understand models, games, and other assets may be proprietary, so please do not share any sensitive intellectual property (IP) publicly.
  4. Bugs: Is there a bug that you reported through the bug reporter that’s worth discussing with the community? (See below for specifics about submitting bugs.)
  5. Documentation: Is any of the documentation unclear? Would you like more documentation for specific items?

Please also use tags when posting new topics to help folks navigate information more seamlessly. This also helps the many members across our Unity teams who actively read through the discussion forums, jump in to support and answer questions for the areas they look after. The XR tags available are:

  • XR
  • XR-OpenXR
  • XR-Meta-Quest
  • XR-Android-XR
  • XR-visionOS
  • XR-PolySpatial
  • XR-AR-Foundation
  • XR-Interaction-Toolkit
  • XR-Input
  • XR-Hands
  • XR-HoloLens
  • XR-Magic-Leap
Reporting Bugs

Before submitting a bug, check if it’s already been reported here, otherwise, your bug may be closed as a duplicate if a similar one exists. Please report bugs via the Unity Bug Reporter in the Unity Editor, and provide as much context as possible so we can rapidly triage the issue. When submitting a bug, please:

  • Link to a hosted image or video that clearly shows or explains the issue, including expected vs. actual results.
  • Attach a (stripped) project so we can easily recreate your issue.
  • Attach Profiler .data and Profile Analyzer .pdata files where possible.
  • After filing your bug, open a Discussions topic if you believe the community would benefit. In the topic name, it helps to use your bug name and issue # to make it easier to identify
Sharing Feedback

Please refer to our roadmap where you can learn about what’s planned moving forward, and tell us more about your experience or share your ideas with us. Your feedback will be carefully reviewed by the team, and provides a significant impact in driving the direction of the product. We look forward to hearing from you!

In Case You Missed It

Here’s a list of our announcements from the past quarter that you may have missed:

5 Likes

Hi, will the compositor layer or the foveated rendering system be compatible with HDRP at some point?
Thank you.

1 Like

So glad to hear from you about XR performance investment from Unity!

We’ve been trying out optimized multiview regions recently on our Quest 3 game. It seems to work as advertised, giving an FPS boost that we appreciate. However, ONE of our group of 8 beta testers who tried the feature found it to be a big problem because he can see the black region that is being excluded from rendering. He only sees it on the left edge of his right eye. Since we are all testing on Quest 3 devices with the same build, I dug into why nobody else was experiencing it, and I now think we are ALL “seeing” it, but it’s only a problem for him. I guess the shape of his face is different and most of us just don’t notice the problem? If I look VERY carefully with my left eye closed, especially if I turn in place quickly, I can see exactly what he is describing. He says it is very distracting for him during gameplay.

So is there any way for us to tune this - maybe to reduce the width of the excluded area slightly? And is there is any reason it’s only visible in the right eye, whereas the left eye is perfect? Seems like maybe a bug?

EDIT: This is from Unity 6000.1.0f1 on Quest 3, OpenXR, foveated rendering enabled (via SRP), space warp NOT enabled.

2 Likes

Not likely. Most of our investments are focused on URP, and getting the best performance across the widest range of platforms.

2 Likes

May I ask how this aligns with the goal of having co-existence of HDRP and URP and/or a more unified renderer architecture in the future? Wouldn’t it be more coherent to build all new features in a way that they work with both render pipelines, and not only for one?

1 Like

@mfuad thanks for the update, I have two questions.

  1. Am I correct that work on HDRP XR is completely stalled? Because that is pretty terrible news. Is “co-existence” an actual goal for Unity, or is HDRP just slowly being phased out behind our backs?

  2. I’ve been stuck with an XR issue for months just trying to set custom single pass stereo matrices in HDRP. What I gather after many discussions is that I have to write a OpenXR provider, that is; write external software that emulates a XR device, just to be able to do the equivalent of the (now obsolete) camera.SetStereoViewMatrices() and camera.SetStereoProjectionMatrices() methods. I finally have a workaround, but it misuses MockHMD and it involves modding both HDRP and SRP Core. Do you agree the correct approach is writing a OpenXR provider?

2 Likes

@mfuad We need some clarifications about this questions. Our company invested heavily into HDRP using XR for PCVR high fidelity software. What’s the way forward? There is no clear communication about what happens with XR in HDRP or even HDRP in general, and how to build high fidelity XR in the future, in the past it was recommended by Unity to use HDRP. URP is not there yet, and probably won’t be in the next two years. HDRP does not get new features, and even obvious bugs with XR won’t get fixed, and that EVEN if I also provide the fixed code, which would taka a dev 5 minutes to validate and integrate.

Could you expand on the controller manipulation for near-far interactor? I am hoping this means that if you pick something up from a distance, you can use the thumbstick to pull and push the object along the ray?

Will there be support for teleportation with hand tracking? At the moment it can be done but you have to jump through hoops and it is tricky. Ideally, it should be easy to use hand poses to trigger teleportation.

Any updates on GPU Occlusion Culling support for Meta Quest?

In 6.0 it produced a bunch of graphical errors, now in 6.1 it says it detects an invalid driver state. Would really help performance on some of my projects and cut out a lot of the overdraw I’m seeing

2 Likes

Met the exact same problem today. I spent the past few weeks testing with Multiview Render Regions enabled on Quest 2 and 3S and there’s no issues. Only Quest 3 has the black area on the right eye.

1 Like