Move Component simple bug

Why when i try to rotate any component with rotator (the position is Z 179 and it must to rotate to Z - 179) it always start from 179>100>30>-10>-80>-180 ? Why it must to rotate over 350 degrees and cant move 179>-179 (only 2 degrees) ?
And litle minor which havnt any meaning but i see it, when i have rotator X-0 Y-0 Z-50 if i make split struct it make X-0 Y-50 Z-0 . I am not sure for this.

Hi urksqrk,

For the first part of your question - This is due to gimbal lock. You will need to account for Gimbal lock when doing any rotation math. You can find information on Gimbal lock here:

And Quarternion math here:

For the second portion of your question -

  • What steps can I take to reproduce this on my end?

  • Does this occur in 4.12 or only in 4.11?

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?

The second - I try this in 4.11.2 version in ThirdPersonCharacter and LevelBluePrint. Move component to have X-1 Y-2 Z-3 When i make split struct they are X-2 Y-3 Z-1

With location i havn’t problem.

I try it in other 4.11 project, 4.12.5, 4.13 and again i have this problem.

Now I remembered that when I use split struct i have problems with rotator, maybe this mix was the problem.

Now i test Teleport and again when rotator is 1 , 2 , 3 and i make split > 2 , 3 , 1

Hi urkqsrk,

Do you have a video of the error occurring that I can see? I think it would help show me what is occurring.

Can you tell me program which can make video on my screen?

You can use programs such as FRAPS or Snaggit to video capture your monitor.

Sorry for this full screen.

Does this only affect printed values or is your actor rotating along the wrong axis when you do this?

Only printer, now i make rotator and and test first X +20 and then split struct X +20 and all is normal if i change the variables after split.

Hi urksqrk,

Thank you for submitting a bug report. I have reproduced this issue and logged a report for it here. You can track the report’s status as the issue is reviewed by our development staff.