Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.3.X, 2017.4.X
Votes
0
Found in
2017.3.0b3
Issue ID
955674
Regression
Yes
'kValidSceneObjectIdentifier == res' assert after selecting a prefab and its preview window is visible
The bug still occurs in trunk Unity 2018.1.0a1 #3622 8e2bcab90b4e on windows and mac platform
Steps to reproduce:
1. Open attached project
2. Select 'Assets/Props/barrel_pile' prefab
Additional steps:
3. Close preview window
4. Deselect and reselect prefab - assertion is gone
Reproduced with: 2017.3.0b1, 2017.3.0b3
Not reproducible: 2017.2.0f2, 2017.3.0a7
Regression introduced in: 2017.3.0b1
Steps to reproduce the error from scratch:
1) Create a empty GameObject in Hiearchy
2) Create two cubes as a child of empty GameObject
3) Drag the GameObject to Project tab to convert it to a prefab
4) In Project tab, mark the prefab as `Lightmap static`
5) In Hierachy, duplicate the GameObject
6) Drag the duplicated GameObject to Project folder
7) Observe the `Assertion failed: Assertion failed on expression: 'kValidSceneObjectIdentifier == res'` asserts in console
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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
REYCOLAS04
Dec 07, 2019 15:03
The issue is back in the 2020.1.0a14.1541 version
GameDesignDude
Dec 26, 2018 08:20
I am still having the issue in 201830f2 Personal (64 Bit) Mac OS
zwcloud
Jul 31, 2018 12:27
noticed
zwcloud
Jul 31, 2018 12:25
For anyone who ran into this issue when baking lightmap for dynamically created mesh. Make an editor tool and write:
EditorPrefs.SetBool("MeshRendererEditor.Lighting.ShowSettings", false);
This closes the *Lighting* part in the Inspector of the MeshRenderer. I just notified that the error disappeared after I close the *Lighting* part.
MeTx
Mar 29, 2018 11:05
Still here in 5.6.3p2
Assertion failed on expression: 'CompareApproximately(SqrMagnitude(result), 1.0F)'
UnityEngine.Transform:set_eulerAngles(Vector3) NewBoatMovement:Update()
mikelortega
Jan 31, 2018 09:39
Still active in Unity 2018.1.0b4
Desktopdaydreams
Jan 22, 2018 19:35
Hi folks, I just came across this. For me, I had to clear all the flags from each mesh renderer in the prefab and then clear the occlusion culling. That cleared up the errors in the console. Hope it helps.
Vagrant-VX
Nov 21, 2017 22:24
workarounds for this issue
uncheck "Auto Generate" checkbox in Lighting Settings
rcfearn
Nov 17, 2017 07:27
I still have this issue in 2017.3.0b9 Personal (64 Bit) Mac OS
Peter77
Nov 16, 2017 12:40
Related forum thread:
https://forum.unity.com/threads/assertion-failed-assertion-failed-on-expression-kvalidsceneobjectidentifier-res.498303/#post-3289548