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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment