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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- New Hierarchy visibility and pickability icon behavior differs from documentation
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
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.