Search Issue Tracker
By Design
Votes
0
Found in [Package]
5.13.0
Issue ID
1152720
Regression
No
[ShaderGraph] UV node cannot access UVs from UV4 to UV7
How to reproduce:
1. Open the attached "case_1152720-ShaderGraphUV.zip" project
2. In the Project window, open "Test.shadergraph"
3. Inspect the Channel property in the UV node
Expected results: The selection ranges from UV0 to UV7
Actual results: The selection ranges from UV0 to UV3
Reproducible with:
ShaderGraph 4.10.0 (using 2018.4.0f1)
ShaderGraph 5.13.0 (using 2019.1.2f1, 2019.2.0b1)
ShaderGraph 6.5.3 (using 2019.2.0b1, 2019.3.0a2)
Note: The UV node can only access 4 UV channels, but the Mesh class has properties for 8 UV channels
Comments (1)
-
andybak
Mar 11, 2020 09:46
Can you clarify what the platform limit issues are? For those of us designing for high-end this is a real pain.
Surely this belongs as a configurable option?
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
- 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
Resolution Note:
This is currently by design due to per-platform limitations for specific platforms. I've added this as a feature request on our backlog and we will investigate supporting this in the future.