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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment