Search Issue Tracker
By Design
Votes
0
Found in
2020.3.40f1
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a11
Issue ID
UUM-15641
Regression
No
HasProperty misleadingly returns true when no "_ST"-named property exists in Shader file
How to reproduce:
1. Open the attached “ShaderGraphST” project
2. Select the “Unlit_CustomShader” Shader
3. Select the “Bugs → List Texture Properties” button in the menu
Expected result: HasProperty returns false meaning that “baseColorTexture_ST” property doesn’t exist and no warning is thrown
Actual result: HasProperty returns true meaning that “baseColorTexture_ST” property exists and a corresponding warning is thrown
Reproducible with: 2020.3.40f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Reproduced on: macOS 12.5 (Intel), Windows 11
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
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Resolution Note:
Auxiliary properties for textures are added to the material for each texture declared in the shader. The "_ST" one is not added if the [NoScaleOffset] attribute is present on the texture.
When you declare a custom vector property with the same name, it won't allow you to set the data on a non-texture property.