this is a serious problem, and I don't even know how to fix it correctly so as not to break someone else's code, most likely after I make corrections I will add a separate "worldRotation" field without this bug, and "rotation" will remain as legacy. I would also like to know if it is possible to use a rotation distorted by incorrect calculations(to understand the level of severity of the problem)?

In its current form, it is completely unusable. When the gps is rotated only in 1 axis at a time, the calculations are correct. However, when rotated in 2 axes, some values become inverted. When rotated in 3 axes, the calculations become completely wrong

it's horrible... could you try to fix the GPS script. just commenting out a line is not enough, as you need to impose noise on the measurements. the standard conversion method is sm.quat.fromEuler didn't work for me for some reason

I temporarily removed the rotation noise from the GPS, when I make it work normally, I will make it so that it can be turned off in the "Permission Tool"

I also added a creative GPS unit that does not contain any noise at all, and even when I make the correct noise formula for the rotation, the creative GPS unit will not contain any noise