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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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