Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4.10f1
2019.3.0b3
2020.1
2020.1.0a10
Issue ID
1192967
Regression
Yes
Closing one of the Cluster Rendering Nodes Crashes the Cluster
Reproduction steps:
1. Open the attached project named Case_1192967
2. Build the project
3. Launch the build using the attached .bat file named "RunCluster"
4. Close one of the Cluster nodes
Expected result: All of the Cluster's nodes close without throwing crash warnings
Actual result: Two brief crash warnings are thrown after a node is closed
Reproducible with: 2018.4.10f1, 2018.4.12f1, 2019.3.0b3, 2019.3.0b8, 2020.1.0a10
Not reproducible with: 2017.4.33f1, 2018.4.9f1, 2019.1.0a1, 2019.2.10f1, 2019.3.0b2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
A new version of Cluster Display is being developed that doesn't have this issue. The old version is not being maintained anymore.