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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment