With a Blend2D node set to Polar Input Mode you can manually input an Angle and it works correctly, but when you input it with a Number parameter it results in a seemingly random angle:
Maybe it’s because the angle is expecting a rotation value, which doesn’t exist as a parameter option, and it’s not correctly translating the Number variable?
Expected behavior
The number input from a parameter should be the same result as manually inputting the value directly in the node.
the angle parameter is in radians its not random
try converting it from degrees to radians
Then they should’ve made it consistent with the angle value itself instead of just making it exclusively degrees but make any input value radians.
I suspected that was the case, but there’s no option for making a radian parameter, just number. I would expect the behavior to be to either add a radian parameter option, or for number to automatically convert
Hi there, thanks for your report!
There is something we need to fix here, but I’ll have to give you some additional information first.
When we designed the polar mode, we made a conscious choice to display the angles in degrees in the UI, to be consistent with how Studio shows angles across all the plugins - in particular, angles are shown in degrees in the ACE, and we decided to keep that convention.
On the other hand, angles passed through the API (CFrame rotations, math trig functions, etc…) use radians, and we wanted to be consistent there as well.
This is why, when you type an angle in the Blend2D node, it is in degrees.
The main goal of parameters, however, is to be driven by scripts. This is why the angle you type as a parameter is evaluated in radians. It turns out that 90rad is 5156deg, which is equivalent to 116deg. The yellow cross appears around 116deg on the map.
What is confusing - and we need to fix - is that the angle in the Blend2D node field should not be clamped to -180 to 180 when coming from a parameter. That would help understanding the dual unit system.
