Search Issue Tracker
By Design
Votes
0
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a20
Issue ID
UUM-40884
Regression
No
No option to change the UV channel when using Fabric shaders
Reproduction steps:
1. Open the attached project “UV_Channel”
2. Open Scene “Assets/VSO/Scenes/Kitchen.unity”
3. In the Project window search for “Silk”
4. Select the “Silk” Material
5. Observe the available options in the Inspector
Expected result: The user is able to choose what UV channel is used for Thread Map
Actual result: Thread Map defaults to the second UV channel with no option to change it
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a20
Reproducible on: Windows 10
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
Resolution Note:
It is possible in the fabric shader to control which channel is used for the thread. By setting a specific channel to 1 and everything else to 0 you should be able to select from which UV channel to read and thus avoid the problem.