# Expressing Euler Rotation in Degrees | Geometry Nodes

While learning Geometry Nodes and constructing a functional clock face, I ran into an issue.

My animation should be a minute long - 1800 frames at 30FPS.

In the first part of my graph, I am multiplying the current frame number (#frame) by the value a second pin should move with each frame - 360deg/1800 expressed in radians as (tau/1800).

I then convert this value to degrees with the To Degrees Math Node. Same functionality could be achieved without conversion, working with Radians only. But seeing as the Conversion node exists, I had hoped to use it.

Later, this value is plugged into the Y slot of a Combine XYZ node. My goal was to create a Vector which could then be input into the Rotation of a Transform Geometry node.

It is here, where I suspect the problem arises.

At frame 450, the Second_pin object should be rotated by 90° along the Y-axis. The output of a Combine XYZ node is a (0,90,0) Vector.

This doesn't happen. Instead, the output looks like this:

My guess is that the Transform Geometry node uses a different data type to express rotation internally and my Vector gets converted wrongly. Is there a way to fix this?

Is it desirable to use degrees internally like this?

Thank you for any help.

• welcome. It's seems that the conversion is already done by the Transform Geometry so the Convert to Degree repeat the transformation. Delete it, it should work find. If I’m not mistaking something… Commented Mar 23 at 12:23
• Yeah, it's just confusing interface. The rotation field expects degrees if you type numbers into it. But if you plug a noodle it, it expects radians. Commented Mar 23 at 14:05