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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment