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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.