Search Issue Tracker
Fixed
Fixed in 6000.0.7f1, future release
Votes
8
Found in
2021.3.30f1
2022.3.10f1
2023.1.15f1
2023.2.0b11
2023.3.0a7
6000.0.0b11
Issue ID
UUM-52199
Regression
No
The “Serialized material properties” texture does not copy to a “Non-serialized runtime properties in the shaders” texture when using "CopyMatchingPropertiesFromMaterial"
Reproduction steps:
1. Open project “CopyMatchingPropertiesFromMaterial 2.zip”
2. Open “SampleScene”
3. Select the “CopyBug” GameObject through the Hierarchy
4. Enable the “Copy Bug” script through the Inspector
5. Observe the Game view
Expected result: both “CopyMatchingPropertiesFromMaterial” and “CopyPropertiesFromMaterial” GameObjects materials change
Actual result: only “CopyPropertiesFromMaterial” GameObjects material changes
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a7
Reproducible on: macOS Ventura 13.2.1 (Intel)
Not reproducible on: no other environment tested
Note: Also reproducible in Standalone Player
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