Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
10.1.0
Issue ID
1291676
Regression
No
[Shader Graph] Matrix type ports cannot be connected to Branch Node's True/False ports
How to reproduce:
1. Open the user's attached "shadergraph-branch-matrix.zip" project
2. Open the "New Shader Graph" Shader Graph
3. Connect the "Transformation Matrix" Node's port to "Branch" Node's True/False ports
Expected result: 4x4, 3x3, 2x2 matrices can be directly connected to the "Branch" Node's True/False ports
Actual result: 4x4, 3x3, 2x2 matrices cannot be connected directly to the "Branch" Node's True/False ports
Reproducible with: 7.5.1 (2019.4.14f1), 8.2.0 (2020.1.13f1), 10.1.0 (2020.2.0b11, 2021.1.0a5)
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
- 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
This work is on the backlog and will be completed in time, we want to get around to it sooner rather than later.