Differences in roc.rcAngle between MMF2 and Fusion

Hey everyone,

I was wondering if there is a known difference in the usage/implementation of roc.rcAngle from LPRO pointers between MMF2 and Clickteam Fusion. I have an extension which modifies roc.rcAngle. The object consequently rotates in MMF2 while the object does not rotate in Fusion.

In MMF2, adding "1" to this value increases the object's angle by 1.
In Fusion, adding "1" to this value increases the object's angle by 1.4013e-045.

Original
I already had the angle as float unless it was specifically non-HWA in MMF2. Furthermore, the roc.rcAngle isn't matching up with angle expression from the actual object. Lastly, I just tried explicitly using roc.rcAngle as all floats, and nothing changed. Anymore ideas as for the culprit?

Update
In MMF2, roc.rcAngle returns the object's current angle.
In Fusion, roc.rcAngle returns a number significantly different from the object's actual angle, regardless whether it's casted as an int or float. It's also not returning in radians.

It's exactly that. I reverted back to ANGLETYPE for simplicity and discovered that returning just rcAngle has discrepancies between the two applications.