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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment