Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X
Votes
0
Found in
2017.1.0f1
2017.2.0b1
2017.2.0f3
Issue ID
968591
Regression
Yes
Editor crashes after setting culled objects active/inactive when Animation component Culling Type is set to Based On Renderers
Steps to reproduce:
1. Open attached “CullingCrash.zip” project
2. Enter Play mode
3. Wait a few seconds
Reproduced in: 2018.1.0a4, 2017.3.0b9, 2017.2.0p2, 2017.2.0b1, 2017.1.2p3, 2017.1.0f1, 5.6.4p2, 5.6.2p1
Didn’t reproduce in: 2017.2.0a4, 2017.1.0b10, 5.6.2f1, 5.5.5p1, 5.5.0f1
Regression introduced in: 2017.2.0b1, 2017.1.0f1, 5.6.2p1
Note: Setting Culling Type to Always Animate prevents this issue from happening
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment