Search Issue Tracker
Fixed in 2021.3.29f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a22
Votes
2
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b19
2023.2.0a17
Issue ID
UUM-28758
Regression
Yes
The “Invalid subscript 'texCoord2'“ error appears when using a TextureSize node
Steps to reproduce:
1. Open the attached project “ShaderIssue“
2. Select the “Assets/FullScreenTextureSizeTest.shadergraph“ Shader Graph
3. Observe the “Errors” table in the Inspector window
Expected result: No errors are displayed
Actual result: The “Invalid subscript 'texCoord2'“ error is displayed
Reproducible with: 14.0.2 (2022.2.0a9), 14.0.6 (2022.2.5f1), 15.0.4 (2023.1.0b2), 16.0.0 (2023.2.0a1)
Not reproducible with: 10.10.1 (2020.3.45f1), 12.1.9 (2021.3.17f1), 14.0.1 (2022.2.0a8)
Reproducible on: Windows 10
Note: Shader Graph fails to import when using 14.0.1 (2022.2.0a8)
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
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
Fydar
Feb 20, 2023 10:07
This is NOT a regression. The issue is present on and after version 14.0.02 because of new features introduced in this version.