Search Issue Tracker
Fixed
Fixed in 2022.3.20f1, 2023.2.9f1, 2023.3.0b5
Votes
1
Found in
2022.3.17f1
2023.2.4f1
2023.3.0b1
Issue ID
UUM-59617
Regression
No
Locked material properties aren't updated when they hide an override in a variant
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/MaterialVariantBug/MaterialVariantBug.unity“ Scene
3. Select the “Assets/MaterialVariantBug/MirrorRed.mat“ Material
4. Change the “Smoothness” value to “0.5” in the Inspector
5. Select the “Assets/MaterialVariantBug/Mirror.mat“ Material
6. Lock the “Smoothness” value by right-clicking on it and selecting “Lock in children“ in Inspector
7. Observe the spheres in the Game View
8. Change the “Smoothness” value to “1” in the Inspector
9. Observe the spheres in the Game View
Expected result: Both spheres reflect the new smoothness value of the Mirror Material
Actual result: Only the blue sphere follows the smoothness of the Mirror Material
Reproducible with: 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Couldn’t test with: 2021.3.34f1 (Required functionality isn’t present)
Reproducible on: M1 MacOS 14.2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment