Search Issue Tracker
Fixed in 12.x.x
Votes
1
Found in [Package]
12.0.0
Issue ID
1327461
Regression
No
[Shader Graph] In the Inspector inputs for Vector 4 are shown when Vector 2/Vector 3 node is used
How to reproduce:
1. Open the attached "1327461_Repro" project
2. In the Project window select "New Material"
3. Observe the Inspector (Window->General->Inspector)
Expected results: The "Vector 2" variable has 2 inputs (X and Y) and the "Vector 3" has 3 inputs (X, Y, and Z)
Actual results: Both "Vector 2" and "Vector 3" variables have 4 inputs (X, Y, Z, W)
Reproducible with: 7.5.3 (2019.4.24f1), 10.4.0 (2020.3.4f1), 11.0.0 (2021.1.3f1), 12.0.0 (2021.2.0a12)
Note:
- While both Vector variables have more inputs in the Inspector than should they do not affect the Shader Graph if changed
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 12.x.x):
Fixed in 2021.2.0b7