Search Issue Tracker
Won't Fix
Votes
0
Found in
5.0.0a19
Issue ID
624096
Regression
No
"Destroy may not be called from edit mode!" error spam in the Console when entering play mode
Steps to reproduce :
- import the Top-Down Dungeons https://www.assetstore.unity3d.com/en/#!/content/7853 from the Asset Store
- open the "Scene1"
- change the Lightmapping from Legacy to Iterative (case 624090)
- enter playmode and notice the screen is black and the errors in the console
Destroy may not be called from edit mode! Use DestroyImmediate instead.
Also think twice if you really want to destroy something in edit mode. Since this will destroy objects permanently.
UnityEngine.Object:Destroy(Object)
AntialiasingAsPostEffect:OnDisable() (at Assets/Top-Down Dungeons/Standard Assets/Image Effects (Pro Only)/AntialiasingAsPostEffect.js:102)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- LUT assets are not shown when selecting Spectral Lut with Advanced Object Selector
- GameObjects disappear from Scene view when hidden in Hierarchy and Scene view Eye icon is disabled with GPU Resident Drawer enabled
- [Android] Audio sound is lower in the Player compared to the native music player
- Feet slide and misalign when playing retargeted animations
- IndexOutOfRangeException is thrown in NativePassCompiler when a graphics buffer is used in more than 5 render passes
Add comment