Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b12
Issue ID
645882
Regression
Yes
Getting the material of a mesh renderer causes the mesh to become invisible on standalone
Trying to access the material of a mesh renderer through "renderer.material" or "GetComponent<Renderer>().material" causes the mesh to become invisible on standalone builds.
To reproduce:
1. Import material-bug.unitypackage
2. Build the "MatBugScene" for standalone
3. Notice that there is no cube on the standalone build, while on the editor everything looks fine
4. Commenting out "Material myMaterial = renderer.material;" fixes the issue
Regression since 4.5.5p5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ”Last item reached” warning is thrown when no search results are found in UI Toolkit Layout Debugger
- UI Elements overlap in the Shortcuts window when docked and resized to a smaller window size
- UIBuilder DataSourcePath dropdown fails to show properties when binding to abstract classes
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
Add comment