Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.2.X
Votes
2
Found in
2017.4.0f1
Issue ID
1018539
Regression
Yes
"Transform has SetIsHierarchyDispatchInterested present when destroying the hierarchy.." assertion thrown on particle collisions
How to reproduce:
1. Open the attached "AssertionFailed2" project and "1" scene
2. Enter playmode and observe the console
Expected result: No assertions are thrown in the console
Actual result: "Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate" and "Assertion failed: Transform has SetIsHierarchyDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate" assertions are thrown
Regression introduced with - 2017.2.0b7
Reproducible with - 2018.2.0a7, 2018.1.0b13, 2017.4.1f1, 2017.2.2p2, 2017.2.0b7
Not reproducible with - 2017.2.0b6, 2017.1.3p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Add comment