UE-22228 the bug where the camera spins the wrong way in the sequencer doesn’t seem to be fixed. I have a U shaped camera rail and i’m trying to make the camera follow the inside of the curve. The camera spins the wrong way to hit the next rotation point. Is there a fix for this? Can I have an option to choose which way the camera rotates (counter-clockwise or clockwise) to reach it’s next rotation point, please?
1 Like
Wait, i’m dumb. You can change the euler angles in the graph 
1 Like
Right clicking in the transform field >properties and set to use Quaternion Rotation did the trick for me!
Or maybe thats what you meant 
9 Likes
Yes! Thank you for this
Where exactly is Transform Field Properties?
Oh, found it. You need to right click on the root Transform area of the timeline (above your location and rotation keys) and then go to properties and you’ll see the option for Quaternion Rotation).
3 Likes
Oh, so in my situation, switching to Quaternion made all of the rotations seem linear and mechanical even though my curves were not linear. They all had an abrupt stop to them rather than a smooth transition. So, I actually figured out that what was happening was my pitch value was going above 360 into a range around 700 to 800+. So what I did was subtract 360 from those values (744 - 360 = 384) and manually set a new pitch value for all of my frames, and this actually removed the extra spin on my camera. Now granted, I had to do this for every single key frame AFTER the rotation glitch which in my case was 23 keys which was tedious, but it meant that I didn’t have to use Quaternion rotations which kept all of my rotations looking smooth. So just be aware that switching to Quarternion rotations for the entire sequence isn’t the easy fix that it seems to be as it will drastically change the result of your rotations.
2 Likes
Four and a half years later, your answer has helped me Many thanks
1 Like
Okay so I have revived this bug in 5.2 and I realized that when my Engine Scalability is set to Cinematic that I was seeing it, with none of the previous fixes working, and setting engine scalability down to Epic made the issue go away.