Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
1.11.0
Issue ID
OXRB-352
Regression
No
OpenXR Mock Runtime used D3D11 when Unity Player is configured to use D3D12
The OpenXR Mock Runtime tests tried to use D3D11 instead of D3D12 when the unity player is configured to use D3D12.
According to [XRF-323 [SPIKE] D3D12 OpenXR Mock Runtime support - Part 1|https://jira.unity3d.com/browse/XRF-323], D3D12 now supports OpenXR Mock Runtime. However, when we run the xr.xrautomated graphics test on MockRuntime against D3D12, in the UnityLog.txt, it shows:
{code:java}
Dedicated video D3D11 device creation failed (error: 0x887a0004). This device is used specifically for video decoding, we will use software video decoding instead.{code}
Which I think its trying to use the D3D11 instead of D3D12.
The yamato job can be found at:
[https://unity-ci.cds.internal.unity3d.com/job/37760568/artifacts]
and the full [PlayerLog.txt|https://yamato-api.prd.cds.internal.unity3d.com/gcsArtifact/a4390b82-cee5-49d6-88b1-1ece3c41de8b%2Fbuild-logs%2F.yamato%2Fbuild%2Flogs%2Fplaymode%2FURPGraphicsTests%2FPlayerLog.txt] can be found at: build-logs/.yamato/build/logs/playmode/URPGraphicsTests/[PlayerLog.txt|https://yamato-api.prd.cds.internal.unity3d.com/gcsArtifact/a4390b82-cee5-49d6-88b1-1ece3c41de8b%2Fbuild-logs%2F.yamato%2Fbuild%2Flogs%2Fplaymode%2FURPGraphicsTests%2FPlayerLog.txt]
*Steps to reproduce:*
1. Run the yamato job in the previous link and look for the playerlog
*Actual results:* MockRuntime used D3D11
*Expected results:* MockRuntime used D3D12
*Reproducible with versions:* trunk, 2022.3, 2021.3
*Not reproducible with versions:*
*Can’t test with versions:*
*Tested on (OS):*
*Notes:*
*
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
Mock Runtime was able to run Direct3D 12 in a fresh test run.