Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.3.X, 2018.1.X
Votes
38
Found in
2017.3.0b9
Issue ID
968882
Regression
Yes
Gameobject Transforms are not being disabled when the Player is Stopped
Gameobject Transform component keeps on being detected post to Disable of the Game object.
Users are running into this without Vuforia, but this project reproduced with Vuforia specifically:
https://forum.unity.com/threads/assertion-failed-transform-has-setisdispatchinterested-present-when-destroying-the-hierarchy.505111/
https://forum.unity.com/threads/problem-with-error-when-scene-transitions.507158/
Pre requisites:
Vuforia component should be installed with Unity Engine.
Steps to Reproduce:
1. Create a new Project.
2. Click on Edit > Project Settings > Player.
3. Enable the "Vuforia Augmented Reality Supported" from the XR Setting Section.
4. Click on GameObject Menu > Vuforia > AR Camera
5. Create an Image Target from the Vuforia Menu
6. Set relevant parameters for the Dataset that was created on Vuforia portal
7. Set the Image Target such that AR Camera views the Image Target.
8. Play The Scene
9. Once the Marker displays the Augmented Game object , Stop the Player.
Error would be displayed
Stack Trace:
1. Assertion failed: Transform has SetIsDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.
2. Assertion failed: Transform has SetIsHierarchyDispatchInterested present when destroying the hierarchy. Systems must deregister themselves in Deactivate.
Reproduced On: 2017.3.0b9
Works Fine On: 2017.2.0f3, 2017.3.0b8, 2017.3.0b7
Regression Introduced On: 2017.3.0.b9
Platforms that Error comes : Mac OS, Windows OS.
License type: Free
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
andrew-rc
Jan 17, 2018 05:27
Same, after upgrading to 2017.3.0f3. Not using vuforia.
Nitrox32
Jan 15, 2018 15:47
Same error with 2017.3.0f3 personal. Not using VUFORIA. Is there a version where this error doesn't occur?
mitcha1221
Jan 11, 2018 21:41
I'm still getting this bug in Unity 2017.3.0f3. I am using Vuforia.
Zullar
Jan 02, 2018 22:13
2017.3.0f3 Getting 22x occurrences of these 2 errors when stopping play in the Editor. I am not using VUFORIA.
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.
lmoro
Dec 29, 2017 11:04
Same here using Vuforia in Unity 2017.3.0f3
rad1c
Dec 28, 2017 18:59
Coks Dec 08, 2017 10:43
I have same error in my project when reload scenes or end of play mode in editor. Seen in versions: 2017.2.0p2 (64-bit), 2017.2.0p3 (64-bit), 2017.2.0p4 (64-bit), 2017.3.0f1 (64-bit).
+1
Zullar
Dec 20, 2017 02:50
I'm getting the same error after upgrading to 2017.2.1f1
Steederino
Dec 18, 2017 21:00
This is happening whenever a collider is disabled on a GameObject which is not currently activeInHierarchy. Here's a simple repro:
var obj = new GameObject();
var collider = obj.AddComponent<BoxCollider>();
// Disable the collider (while the object is inactive)
obj.SetActive(false);
collider.enabled = false;
// Destroying the object will result in "Assertion failed" errors
Destroy(obj);
Coks
Dec 08, 2017 10:43
I have same error in my project when reload scenes or end of play mode in editor. Seen in versions: 2017.2.0p2 (64-bit), 2017.2.0p3 (64-bit), 2017.2.0p4 (64-bit), 2017.3.0f1 (64-bit).
JacobK
Dec 07, 2017 17:39
Still happening in 2017.2.0p4. Getting the assertion faileds 800 or so times!