floatQ input initializes with invalid [0;0;0;0] value (expected [0;0;0;1])

[Adreos]

Describe the bug?

When attempting to drive a rotation with a lerp node, a slerp node, or drive it with a tween node the rotation does not gradually transtion from one angle to another, it instead snaps from start to finish.

Rotations drive by a raw input, or through a From Eular node still work fine. Outputs, both raw and through a Eular Angel node show the lerp, slerp are still changing values, the rotation driven just isn't receiving it.

To Reproduce

Attempt to drive a rotation with a flux node of lerp, slerp, or with a tween to the floatQ.

Expected behavior

I expect using a tween, lerp, or slerp to gradually rotate the object through all angles not snap from start to finish.

Screenshots

Video of bug is here
https://www.youtube.com/watch?v=MIdZxmiDVJQ

Resonite Version Number

Beta 2024.9.16.1105

What Platforms does this occur on?

Windows

What headset if any do you use?

Has occured on Desktop and Index

Log Files

RAGEL - 2024.9.16.1105 - 2024-09-17 11_31_19.log

Additional Context

Older rotation tweens and lerps seem to be working, its setting up new ones that is bugged.

Reporters

Adreos

[shiftyscales]

Upon investigating, I discovered that creating a new floatQ input from a ProtoFlux node generates an invalid quaternion [0;0;0;0] as opposed to the expected [0;0;0;1].

2024-09-17.09-38-52.mp4

[lxw404]

The invalid default quaternion was reported here as well: #1158.