Search Issue Tracker
By Design
Votes
0
Found in
4.3.0f4
Issue ID
576874
Regression
No
TextMesh mesh is wrong when MeshFilter present on same GameObject
TextMesh mesh is wrong when MeshFilter present on same GameObject.
This is expected behavior.
MeshFilter and TextMesh are both components that rely on a MeshRenderer component to render the mesh. When they are both present, they are conflicting over which one gets to set the mesh that the MeshRenderer should use.
That said, we should not allow a MeshFilter and TextMesh on the same GameObject because it is not supported anyway. We'll file a separate bug bug on that.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment