Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.58f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-100108
Regression
No
Material preview shape button does not work with material modified through script at runtime
How to reproduce:
1. Open the attached “IN-96536“ project
2. Open the “SampleScene“
3. Select the “Cube“ GameObject in the Hierarchy window and make sure that it has “MapPreviewTest“ component attached in the Inspector Window
4. Go into Play mode, in the Inspector window go to “New Material (Instance)” Preview window
5. Press the material preview shape button
6. Observe the results
Expected result: The material preview shape changes to the shape illustrated on the material preview shape button
Actual result: The material preview shape stays a sphere
Reproducible with: 2022.3.58f, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Reproducible on: MacOS 15.3 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested
Note:
- During Play mode, In the material Inspector window (opened by double-clicking on “New Material (Instance)“ in the Mesh Renderer component, in the “Cube“ Inspector window) the preview shape button works
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
- Terrain Tree cast Realtime and Baked shadows simultaneously when "Mixed" Light mode and "Subtractive" Baked Illumination is used in Edit mode
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
Resolution Note:
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.