Search Issue Tracker
Fixed in 8.0.0
Votes
0
Found in [Package]
5.16.1, 7.0.1
Issue ID
1182017
Regression
No
Destroy may not be called from edit mode errors thown when changing Planar Reflection Probe Clip Planes to 0
Repro steps:
1. Open user attached project
2. In the Hierarchy, select "Planar Reflection Probe" object and add a Planar Reflection Probe component
3. In the Capture Settings, change Clip Planes Near or Far value to 0
Expected result: No errors are thrown
Actual result: Destroy may not be called from edit mode errors thrown multiple times
Reproducible with: 2019.2.5f1, 2019.3.0b3, 2020.1.0a4
Could not test with: 2017.4.32f1 (No Package Manager), 2018.4.9f1 (Clip Planes not implemented)
Reproducible with package versions: 5.16.1, 6.9.1, 7.0.1
Could not test with package versions: 4.10.0 (Clip Planes not implemented)
Error thrown:
Destroy may not be called from edit mode! Use DestroyImmediate instead.
Destroying an object in edit mode destroys it permanently
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Add comment