Search Issue Tracker
Fixed in 0.11.0-preview.44
Votes
0
Found in [Package]
0.11.0-preview.4
Issue ID
1328505
Regression
No
[HybridRenderer V2] Ambient light is not applied to a mesh when it was created using RenderMeshUtility.AddComponents
How to reproduce:
1. Open the attached "HybridAmbientTest" project (download from Google drive, link in the edit)
2. Open the Scene "SampleScene"
3. Enter the Play Mode
Expected results: All of the Spheres are the same
Actual results: The third Sphere from the left is darker, does not take ambient light into consideration
Reproducible with: 0.11.0-preview.4 (2020.3.5f1, 2021.1.4f1, 2021.2.0a14)
Could not test with: 0.10.0-preview.21 and earlier because the RenderMeshUtility.AddComponents API was not yet introduced
Note:
- Currently as a workaround you can add the Component manually "entityManager.AddComponentData(entity, new AmbientProbeTag());"
Add comment
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
Resolution Note (fix version 0.11.0-preview.44):
Fixed in Hybrid Renderer 0.11.0-preview.44 available in Unity 2020.1.9f1 and above