Search Issue Tracker
Fixed in 12.0.x
Votes
0
Found in [Package]
SRP Master (ccae6669bf)
Issue ID
1316128
Regression
No
[Shadergraph] Plugging both a fragment exclusive and vertex exclusive node into the same path lets you make an invalid route
Repro steps:
1. Create an add node
2. Plug a Sample Texture 2D node into the top slot
3. Plug a Vertex ID node into the bottom slot
4. Plug the result into vertex position
Expected result: having a fragment exclusive node plugged into a slot should make other slots incompatible with vertex exclusive routes, and vice versa (after plugging the Sample Texture 2D node into one slot it should not be possible to plug a Vertex ID node into the other slot on the add node)
Actual result: it is allowed and causes the shader to fail to compile, due to having a fragment exclusive node plugged into the vertex stage
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Add comment