Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.2.0a8
2020.2.0a13
Issue ID
1258194
Regression
Yes
Crash on RayTracingShader.Dispatch() method call
How to reproduce:
1. Open the attached 'project-1258194.zip' project
2. In the Editor select 'CustomTest' > 'RayTracing'
CRASH/FREEZE
Reproducible with: 2020.2.0a8, 2020.2.0a13, 2020.2.0a16
Not reproducible with: 2020.1.0b14, 2020.2.0a7, 2020.2.0a14, 2020.2.0a15
Could not test with: 2018.4.24f1, 2019.4.2f1 (due to incompatibilities)
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
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
- [HDRP] Volumetric cloud shadows disappear when there is no directional light shadows
- “Selector” column names in the Search window are lowercase when added
- Install List Project Counter Panel can be right clicked through and Install Context Menu can be opened disabling Project Counter Panel's buttons
- [MacOS] Scene is marked/flickering as dirty (with asterisk) when dragging a Material on a GameObject in Scene view
Resolution Note:
After some discussion internally, I'm closing this as a won't-fix because the user case of running a view-size dispatch shader 100000 times in a single script call is not how the ray tracing API is intended to be used. In HDRP, our most fully-featured ray tracing implementation, you get no more than 5-10 RayTracingShader dispatch calls per frame. I think it's reasonable to say that dispatching a ray tracing shader more than 1000 times in a single script callback is not supported.