Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a12
2020.1
2020.1.0a18
Issue ID
1209828
Regression
Yes
[Enlighten] "There should be one material data entry per instance" error is thrown on deleting static game object after baking
"There should be one material data entry per instance" error is thrown on deleting static game object after baking the scene.
Steps to repro:
1. Create a new Project.
2. Create a static cube game object.
3. Windows > Rendering > Lighting Settings.
4. Lightmapping Settings > Lightmapper > Enlighten.
5. Delete Cube game object after baking the scene.
Actual Result:
"There should be one material data entry per instance" error in the console window.
Expected Result:
No Errors in the console.
Reproducible in:
2020.1.0a18, 2019.3.0f5(209f7fb30bd5), 2019.3.0a12.
Working Fine in:
2019.3.0a11.
Environment:
Occurring on Windows & Mac.
Stack trace:
There should be one material data entry per instance. Instance data entries: 0, material data entries: 1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment