Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy.

I should have edited my post, sent a bug report with a project and they confirmed it was a bug, tested and happening on 2017.4, here is the test project that was sent in case you want to check it out.

 

Updated to 2018.1 and the problem is still happening, when is this going to be fixed?

 

Thanks, for now i've decided to stick with 2018.1 and just not call ParticleSystem.Play() on particle collision which was the cause of the error in my case (during a scene change), what i did was call Play() each time the particle collided so that it would restart with a new random start delay, it seems impossible without this trick to spawn a single burst particle at random intervals, like a droplet falling every 1-2 seconds, please let me know when this is fixed.

Bit unrelated but it would be a good idea to add a particle "Loop Delay" option, similar to the Start Delay but for every time the particle system loops.

 

At the end which version is best for developers unity 2017.3.3f1 has many issues.

 

Hey Jack, got the same issue in 2018.1.0f2. Thanks for your help!

 

I am having the same errors still on 2018.1.1f1, but mine doesn't even involve destroying the hierarchy. I get these two errors:

Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.

Assertion failed: Transform has SetIsHierarchyDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.

It happens during our OnPostprocessModel() AssetImporter script, whenever we loop through the child objects and if there is a Renderer component, we try to assign our root Transform to its .probeAnchor value.

With purely just that action, no deletions or manipulation of any sort, those two errors get thrown. It is quite strange.
I submitted a case with an example project you can test with. The Case ID is 1040493.

 

Have the same on 2017.4.2f2f:

Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.
Assertion failed: Transform has SetIsHierarchyDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.

What's weird is I just got it right now. Been working on this version / project for over a month - no issues. All of a sudden this is spammed in my console.

 

Hello @Jack-Unity

I apologize for notifying you now. Unfortunately, the problem still exists. This problem always occurs when I go out of playmode. Unfortunately, we have not found a solution. We would be very grateful for a solution!

Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.

Unity Version 2018.1.1f1

Thank you very much

 

Still got the same error after using 2017.3.1p4 or 2017.4.f1

 

I'm getting this error when calling ReplacePrefab on 2018.1.3f1:

Code (csharp):

1. Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.
2. UnityEditor.PrefabUtility:ReplacePrefab(GameObject, Object, ReplacePrefabOptions)
3. ExScript:SavePrefab() (at Assets/Scripts/ExScript.cs:114)
4. ExEditor:OnInspectorGUI() (at Assets/Scripts/ExScript.cs:23)
5. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
6.  
7. Assertion failed: Transform has SetIsHierarchyDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.
8. UnityEditor.PrefabUtility:ReplacePrefab(GameObject, Object, ReplacePrefabOptions)
9. ExScript:SavePrefab() (at Assets/Scripts/ExScript.cs:114)
10. ExEditor:OnInspectorGUI() (at Assets/Scripts/ExScript.cs:23)
11. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

 

Got it here as well with ReplacePrefab. Could not determine what exactly caused it to start happening.
Closing and opening again made it go away and didn't see it again (yet).

 

In my particular case, I couldn't see any pattern. It seemed random.

One thing that might be relevant is that once it starts happening, it will always happen, for any transform.


I also tried a few things to get a consistent reproduction case but no luck so far.

 

Hi, I am getting this same issue on a day dream build in 2018.2.0b7

It happens when switching scenes. In editor it shows the errors, in build it causes the screen to go black and I have to manually exit.

 

Hey guys, I just wanted to say that I also sometimes see a flood of errors like that when I exit play mode in the editor. It is indeed jarring and less-than-ideal.

I'm sorry I don't have any more information about this: I just upgraded the Ghost of a Tale project from 5.5 to 2017.4 and that's definitely a "new" issue for me (never saw that one before).

All I can say is I believe it is related to having multiple scenes being additively loaded at run time. When the game stops, the editor gets rid of the aforementioned scenes and that seems to cause the issue.

I really hope you can fix it!

Edit:
Yep, I can confirm this is a multi-scene related issue. It happens every time the scenes are unloaded when exiting play mode.

 

Yes, it happens 100% of times on the project. Now problem is I can't just send the project: it's over 50Gb now and my internet connection uploads at 0.85Mbps.

If I can be of any assistance over Skype (screen-sharing) I could show you the error messages of course, and maybe we could try doing some tests if that can help you pinpoint the issue. Anyway, just a thought.

 

Sorry for the delay in my reply. So there are roughly 30 scenes loaded at a time. I don't use OnParticleCollision events much (if at all). The number of errors popping up when exiting game mode seems to match the number of particle emitters that were active (and alive) at the time the game stopped.

I'll send you the log file privately...

 

I got this error when opening an empty project and importing unity's own book of the dead scene in 2018.2

 

Transform has 'gParticleSystemTRSInterest|gParticleSystemScaleInterest' change interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.

I'm getting this issue

 

in Unity 2018.2
and I,m working with unity Tower Defense Template
i gets this error in play mode on completing level

 

Hi, Our projects using 2017.4.13f1(64bit) gets 100% assertion when exit playmode on editor.
I did not keep track of which object is emitting, I will log it for your reference.
The following assertions occur 6 times.
It did not occur in 2017.1 maybe..

Code (CSharp):

1.  
2. Transform has 'gParticleSystemTRSInterest|gParticleSystemLateTRSInterest|gParticleSystemScaleInterest' change interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
3. 0x00000001412F9736 (Unity) StackWalker::GetCurrentCallstack
4. 0x00000001412FA2AF (Unity) StackWalker::ShowCallstack
5. 0x00000001411B7F60 (Unity) GetStacktrace
6. 0x00000001406DEF73 (Unity) DebugStringToFile
7. 0x00000001406DF751 (Unity) DebugStringToFile
8. 0x00000001408D1420 (Unity) ValidateInterestedSystemsIsEmpty
9. 0x00000001408D631E (Unity) Transform::MainThreadCleanup
10. 0x00000001403B80AE (Unity) delete_object_internal_step1
11. 0x00000001406FC422 (Unity) CommitBatchDelete
12. 0x0000000140717395 (Unity) DestroyGameObjectHierarchy
13. 0x000000014072033A (Unity) DestroyObjectHighLevel
14. 0x00000001407B0721 (Unity) DestroyWorldObjects
15. 0x0000000140C93B91 (Unity) EditorSceneManager::RestoreSceneBackups
16. 0x00000001411EF5CE (Unity) PlayerLoopController::ExitPlayMode
17. 0x00000001411EFD5D (Unity) PlayerLoopController::SetIsPlaying
18. 0x00000001411F0BA6 (Unity) Application::TickTimer
19. 0x0000000141417DCF (Unity) MainMessageLoop
20. 0x000000014141968C (Unity) WinMain
21. 0x0000000141E719A8 (Unity) __tmainCRTStartup
22. 0x00007FFBEFF33034 (KERNEL32) BaseThreadInitThunk
23. 0x00007FFBF03D1461 (ntdll) RtlUserThreadStart
24.  
25. (Filename: C:\buildslave\unity\build\Runtime/Transform/Transform.cpp Line: 1661)
26.  
27. Transform has 'gParticleSystemHierarchyInterest' hierarchy interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
28. 0x00000001412F9736 (Unity) StackWalker::GetCurrentCallstack
29. 0x00000001412FA2AF (Unity) StackWalker::ShowCallstack
30. 0x00000001411B7F60 (Unity) GetStacktrace
31. 0x00000001406DEF73 (Unity) DebugStringToFile
32. 0x00000001406DF751 (Unity) DebugStringToFile
33. 0x00000001408D154B (Unity) ValidateInterestedSystemsIsEmpty
34. 0x00000001408D631E (Unity) Transform::MainThreadCleanup
35. 0x00000001403B80AE (Unity) delete_object_internal_step1
36. 0x00000001406FC422 (Unity) CommitBatchDelete
37. 0x0000000140717395 (Unity) DestroyGameObjectHierarchy
38. 0x000000014072033A (Unity) DestroyObjectHighLevel
39. 0x00000001407B0721 (Unity) DestroyWorldObjects
40. 0x0000000140C93B91 (Unity) EditorSceneManager::RestoreSceneBackups
41. 0x00000001411EF5CE (Unity) PlayerLoopController::ExitPlayMode
42. 0x00000001411EFD5D (Unity) PlayerLoopController::SetIsPlaying
43. 0x00000001411F0BA6 (Unity) Application::TickTimer
44. 0x0000000141417DCF (Unity) MainMessageLoop
45. 0x000000014141968C (Unity) WinMain
46. 0x0000000141E719A8 (Unity) __tmainCRTStartup
47. 0x00007FFBEFF33034 (KERNEL32) BaseThreadInitThunk
48. 0x00007FFBF03D1461 (ntdll) RtlUserThreadStart
49.  
50. (Filename: C:\buildslave\unity\build\Runtime/Transform/Transform.cpp Line: 1662)

 

In my case, the gameobjects that outputs assertions are, it was a particle set in SubEmitters and it was placed in a child.
I have moving to the same level parent particle and the assertion disappeared

 

Disabling the AR Point Cloud Visualizer on the AR Root GameObject removes the error. I use Map Box sdk

 

2018.2.20f1

Using the Tower Defense demo project Unity provides. Whenever a particle was generated by the turrets firing a shot, reloading the scene / gobing to the next scene results in dozens of errors.

I also get a problem that seems to happen at random but when it happens I get hundreds of errors as ti doesn't stop until just as random. I keep getting errors saying the object is too large or too far away from origin. I am assuming this is the particles also since this is what is causing the other errors in the game...

 

Hi, in 2018.4.3f1, i'm getting a similar (but not identical) error, on Play and when I build (standalone, SteamVR), although it seems benign-- plays, completes the builds and runs.

Transform has 'ReflectionProbeAnchorManager::kChangeSystem' change interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
UnityEngine.GUIUtility: ProcessEvent(Int32, IntPtr)

Transform has 'ReflectionProbeAnchorManager::kHierarchyChangeSystem' hierarchy interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
UnityEngine.GUIUtility: ProcessEvent(Int32, IntPtr)