Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2022.2.7f1
2023.1.0b5
2023.2.0a3
Issue ID
UUM-29085
Regression
No
Prefab Instance with MaterialPropertyBlock has different Colour compared to the original material
How to reproduce:
1. Open the project "IN_31506"
2. Open the "SampleScene" Scene in the Asset
3. Enter the Play Mode
4. Observe the two cubes in the Game view
Expected result: cubes' colours are the same
Actual result: cubes' colours are different
Reproducible with: 2022.1.0a10, 2022.2.7f1, 2023.1.0b5, 2023.2.0a3
Couldn't test with: 2020.3.45f1, 2021.3.19f1, 2022.1.0a9 (due to compiler errors)
Reproducible on: Windows 10 Pro
Note: also reproducible in Player
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:
Renderer.SetPropertyBlock with or without an index doesn't store data in the same location (without index affect all render materials)
So GetPropertyBlock(prop) won't retreive the data previously stored by SetPropertyBlock(prop, 0);
Resolution Note (2023.2.X):
Renderer.SetPropertyBlock with or without an index doesn't store data in the same location (without index affect all render materials)
So GetPropertyBlock(prop) won't retreive the data previously stored by SetPropertyBlock(prop, 0);