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
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
Add comment