Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
964858
Regression
No
CanvasRenderer.SetMesh() does not seem to support more than one UV set
Two objects with same material/shader/mesh, one displayed through MeshRenderer and the other through CanvasRenderer.SetMesh(), render differently. MeshRenderer is correct. The apparent symptom is CanvasRenderer.SetMesh() using TEXCOORD0 in the place of TEXCOORD1-3.
Repro steps:
1. Open attached project
2. Open scene.unity
3. Press Play and notice the discrepancy between the grids of numbers on top and on bottom. (Each grid of 8 is one mesh object)
4. Check used shader to see what's going on
Reproducible in:
Version 2018.1.0a3 (ef91384ea984)
Version 2017.2.0f3
Version 5.6.0f1
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
yangjm2015
Jan 17, 2019 10:17
https://forum.unity.com/threads/ugui-unity5-6-canvasrenderer-vertex-define-has-no-uv1.494790/
Set in Canvas - Additional Shader Channels - TexCoord1 - TexCoord3. Also support Normal