Search Issue Tracker
Fixed
Votes
0
Found in
2019.2.12f1
2020.1.0a1
Issue ID
1199814
Regression
No
Crash on D3D12ImmediateContext::BindTexture when upgrading project with DX12 set as primary Graphics API
Steps to reproduce:
1. Open the attached project ("1199814(1).zip") with one of the reproducible versions
Reproducible with: 2019.2.12f1, 2019.2.17f1, 2020.1.0a1
Not reproducible with: 2019.3.0f4, 2020.1.0a17
Stacktraces:
0x00007FF6C29449E2 (Unity) D3D12ImmediateContext::BindTexture
0x00007FF6C2928543 (Unity) GfxDeviceD3D12Base::SetTextures
0x00007FF6C2125654 (Unity) GpuProgram::ApplyTextureParameters
CheckCopyTextureBaseArguments
GfxDeviceD3D12Base::CopyTexture
GfxDeviceWorker::RunCommand
Workaround: Open the project through command line forcing any other Graphics API as primary.
Notes:
- The project might be registered as upgraded but won't be able to launch on that version due to the crash
- Crash occurs on Packing Textures during the upgrade
Comments (1)
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
EricOpuscope
May 27, 2020 17:04
I have the same issue when I use CreateExternalTexture with D3D12 (it works for D3D11..) with Unity 2019.2.21f1.
In the Unity logs, I found "d3d12: RegisterNativeTexture is not implemented." ..
Is D3D12 fully supported ??