Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
10.10.1
12.1.7
13.1.8
14.0.3
15.0.1
Issue ID
SGB-358
Regression
No
Shader Graph atan2 function is defined incorrectly
Steps to reproduce:
1. Open the “IN-18938” project
2. Open the “test” script (Assets folder)
3. Notice the parameters given to the atan2 function
Expected result: The function is called atan2(y, x)
Actual result: The function is called atan2(x, y)
Reproducible with: 10.10.1 (2020.3.41f1), 12.1.7 (2021.3.14f1), 13.1.8 (2022.1.23f1), 14.0.3 (2022.2.0b16), 15.0.1 (2023.1.0a20)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Note: The code is copied from [https://docs.unity.cn/Packages/com.unity.shadergraph@8.0/manual/Polar-Coordinates-Node.html|https://docs.unity.cn/Packages/com.unity.shadergraph@8.0/manual/Polar-Coordinates-Node.html|smart-link]
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
- Increased Memory usage when Update Mode 'On Demand' Realtime lights are used and DX12 API is selected
- Shader warnings in URP ShaderGraph when using the Normal From Texture node
- 'Stack overflow' error logged in the Console when a script that has a lot of classes is compiled
- Memory Leak warnings are thrown when creating a new material
- The type selector in the UI Builder does not display primitive types when trying to select one in the "Select Type…" window
Resolution Note:
Our current design for binary operations are to use an alphabetical (A or B) distinction to indicate left-hand and right-hand operands. In this case, our atan2 node matches this pattern. With that in mind, we are looking at refreshing our port names and this node is in consideration for future changes.