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
- Text cursor remains visible when hovering over Command Line Arguments scrollbar in Unity Hub
- UI Builder’s "Background" icons for Repeat Y/X, Position X/Y and Slice Type are low quality and blurry in the Inspector window
- “X” button in Editor version search filter is difficult to see when Unity Hub theme is set to Dark
- [Android] The y-value of Input.mouseScrollDelta is positive when scrolling in both directions in the Player
- Crash on TexturesD3D11Base::SetTexture when using DirectX11
Add comment