Search Issue Tracker
Won't Fix
Votes
7
Found in
2022.3.20f1
2023.2.11f1
2023.3.0b8
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-64462
Regression
No
[XR] Low GPU performance with DirectX12 when compared to DirectX11
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/SampleSceneXR.unity” Scene
3. Connect the Quest device with Oculus Link
4. Enter the Play Mode
5. Observe stats
6. Exit the Play Mode
7. In Player settings, switch Graphics API to DirectX11
8. Repeat steps 4 and 5
Expected result: DirectX12 and DirectX11 has similar performance
Actual result: DirectX12 has worse performance than DirectX11
Reproducible with: 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Not reproducible with: 2021.3.35f1
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- DirectX12 and DirectX11 performance is similar without XR
Comments (1)
-
DevDunk
Sep 10, 2025 11:11
Any update?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.