Search Issue Tracker
Active
Under Consideration for 12.1.X, 14.0.X, 16.0.X
Votes
0
Found in [Package]
12.1.11
14.0.7
16.0.2
Issue ID
SGB-555
Regression
Yes
Invalid Subscript Shader error when adding to Vertex in shadergraph
Repo steps:
# Open Unity Scene (HDRP)
# Right click in the project window
# Create > shadergraph > HDRP > Unlit shadergraph
# Pull string out of vertex normal and search "SpeedTree8BillBoard"
Expected Result: No errors in the console
Actual Result: Error is thrown after attaching to the vertex
Reproducible with: 2022.2.13f1, 2023.1.0b14, 2023.2.0a12
Not reproducible with: 2021.3.12f1
Cant test with: 2020.3.46f1 (Functionality does not exist)
Platforms tested: Win 11
Notes:
MA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING _ADD_PRECOMPUTED_VELOCITY _SURFACE_TYPE_TRANSPARENT _TRANSPARENT_WRITES_MOTION_VEC
DOTS_INSTANCING_ON INSTANCING_ON SHADER_API_GLES30 UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING _ADD_PRECOMPUTED_VELOCITY _SURFACE_TYPE_TRANSPARENT _TRANSPARENT_WRITES_MOTION_VEC
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment