Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.1.13f1
2020.2
2021.1
2021.2
Issue ID
1298307
Regression
No
Setting properties via MaterialPropertyBlock does not work, when a Tree component is attached to the object
Reproduction steps:
1. Open user's attached project "TreePropertyBlockTest.zip" and scene "TestScene"
2. Enter Play Mode
3. In Scene View, observe and compare "TreeComponent" and "NoTreeComponent" GameObjects
Expected result: Both GameObjects change color
Actual result: "TreeComponent" GameObject does not change its color
Reproducible with: 2019.4.18f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a1
Could not test with: 2018.4.30f1 (compilation errors)
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:
We won't fix this issue. It takes quite a lot of code to make sure properties are added and removed by Tree components cleanly. The change would have performance implications especially for a big amount of trees. Also the behaviour has been like that since a very early version of Unity (at least 5.6, most probably earlier).