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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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