Search Issue Tracker
Fixed in 5.1.0
Votes
0
Found in
5.0.1f1
Issue ID
691144
Regression
No
Hiding GameObject throw error (m_IsVisibleInScene && IsInScene()) == m_IsVisibleInScene
Contains game object "Hero" that plays animation "hero_drinking" at the first frame animation sets mesh render off for foot mesh. When you hide game object "Hero" during animation unity throws error "(m_IsVisibleInScene && IsInScene()) == m_IsVisibleInScene"
Project Steps:
1. Play scene "Test".
2. Hide game object (Hero).
3. Show game object (Hero).
4. You should get error "(m_IsVisibleInScene && IsInScene()) == m_IsVisibleInScene".
Reproduced: 5.0.1f1
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
PawleyBoboli
Apr 28, 2017 19:46
I am using v 5.6.0f3 and started getting several of these errors in the console:
"Assertion failed on expression: '!IsVisibleInScene()' " with no easy way to trace the problem. After digging around, ARTAKA's response to change Animator Culling Mode to "Always Animate" fixed the problem.
Azikon_n
Aug 06, 2015 09:29
Unity 5.1.1f1 get error "(m_IsVisibleInScene && IsInScene()) == m_IsVisibleInScene" when you move camera on the scene
artaka
Aug 05, 2015 16:56
I'm also getting this error on 4.6.7p2. It seems to happen when the Animator Culling Mode is set to "Based on Renderers". Changing to "Always Animate" gets rid of the error.
crol
May 13, 2015 21:59
5.0.2f1, still got full log of this errors bacause many of my objects on map are animated and while im disabling them to pool.
mogwhy
May 13, 2015 15:39
pretty cool that you found this error.
confused me for a long time