Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.3, 2020.1
Fix In Review for 2018.4
Votes
0
Found in
2018.1.1f1
2018.4
2019.3
2019.3.0f6
2020.1
Issue ID
1216216
Regression
Yes
Crash on CreateDirect3D11SurfaceFromDXGISurface when calling DrawRenderer with a Trail Renderer
How to reproduce:
1. Open attached project "Case_1216216"
2. If a Debug.Log "Will Attempt to call DrawRenderer" does not show up in the Console, restart the Editor
3. Load the Scene "TestScene"
4. In the Project window go to "Assets/Prefabs"
5. Drag the "Trail" prefab into the Hierarchy
6. Change focus to Scene View and then refocus the Game View
Reproducible with: 2018.1.1f1, 2018.4.17f1, 2019.3.1f1, 2020.1.0a23
Not reproducible with: 2017.4.37f1, 2018.1.0f2
Full stack trace:
0x00007FFD9102C067 (d3d11) CreateDirect3D11SurfaceFromDXGISurface
0x00007FF6D255B95B (Unity) GfxDeviceD3D11Base::BindBuffersForDraw
0x00007FF6D255F7B5 (Unity) GfxDeviceD3D11Base::DrawBuffers
0x00007FF6D34A1A55 (Unity) GfxDevice::DrawSharedGeometryJobs
0x00007FF6D53ED7DB (Unity) GfxDeviceWorker::RunCommand
0x00007FF6D53F9A5C (Unity) GfxDeviceWorker::RunExt
0x00007FF6D53F9E48 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF6D3392DA0 (Unity) Thread::RunThreadWrapper
0x00007FFD95837974 (KERNEL32) BaseThreadInitThunk
0x00007FFD9803A271 (ntdll) RtlUserThreadStart
Notes:
1. Trail Renderer has to be enabled for the issue to reproduce
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
- New animation clips are not imported correctly when re-importing a fbx file
- Editor freezes when recompiling scrips in Play Mode
- Shuriken particles depth offset is not working(has no affect) when 'Renderer Alignment' is set to 'View'
- [InputSystem] InputSystem is not initialized when run in `-batchmode`
- Assertion failed on expression: 'rs->textureID == realRS->textureID'
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a5
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b8
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.8f1