Search Issue Tracker
Active
Under Consideration for 6000.6.X
In Progress in 6000.3.X, 6000.4.X, 6000.5.X
Won't Fix in 6000.0.X
Votes
4
Found in
6000.0.69f1
6000.3.9f1
6000.4.0b9
6000.5.0a8
6000.6.0a1
Issue ID
UUM-139909
Regression
Yes
Floating Material Preview window does not update when material properties are changed in the Inspector
Reproduction steps:
1. Open the attached "IN-139024_MaterialPreviewBug.zip" project
2. In the Project window, select the "Material.mat" asset located in the "Assets" folder
3. In the Inspector, click the 3 dots located at the top right of the material preview window > "Convert to Floating Window"
4. Change the "Base Map" of the material to any noticeable color of your choice
5. Observe the floating Material preview window
Actual result: Material doesn't change its color
Expected result: Material changes its color
Reproducible with: 2023.2.0a19, 6000.0.72f1, 6000.3.13f1, 6000.4.2f1, 6000.5.0b3, 6000.6.0a2
Not reproducible with: 2023.2.0a18
Reproducible environment: Windows 11
Not reproducible environment: No other environments tested
Workaround: Hover over the floating preview window with the mouse to update the preview
Note: Issue reproduces in HDRP, URP, and SRP with their default materials respectively
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
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
This issue will be fixed in Unity 6.3 and later