Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.4.X
Votes
0
Found in
2017.1.1p4
Issue ID
956741
Regression
No
[Direct3D12] Standalone built player crashes when using DestroyImmediate for a Texture2D
How to reproduce:
1. Open users attached project
2. Go to File --> Build settings --> Player settings and note that the Graphics API is set Direct3D12 and Graphics Jobs are enabled
3. Build & Run the project (File --> Build & Run)
4. Press "Load scene" at the left top
Result: Built player crashes on:
If with AMD GPU -
0x00007FFC81F7C1B6 (amdxc64) OpenShimInterface
0x00007FFC81F88056 (amdxc64) OpenShimInterface
0x00007FFC99C6555A (d3d12) D3D12SerializeVersionedRootSignature
If with Nvidia GPU -
0x00007FF8E76A4518 (nvwgf2umx) OpenAdapter12
0x00007FF8E77C90A5 (nvwgf2umx) OpenAdapter12
0x00007FF8C105555A (d3d12) D3D12SerializeVersionedRootSignature
Reproducible with - 2017.3.0b4, 2017.2.0f3, 2017.1.1p4, 5.6.3p4, 5.6.0a1
Notes:
1. Not reproducible with Direct3D11
2. Does not crash when using Destroy instead of DestroyImmediate
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Add comment