Skewed Rotation values from camera actors in print string

When using the camera actor and modifying the rotation values, the values made in the print string do not seem to match the actual values of the camera's rotation. The values appear to be close, but are off by several degrees, with the exception of the Yaw value, the values printed seem to be either close to 0 or -180, despite the value of the Yaw being 180 (though this may be related to the gimble lock). This issue is not a regression

Versions Tested: issue occurs in all versions
4.16.3 - CL: 3561208
4.17.1 - CL: 3586342
4.18.P1 - CL: 3655406

1. Create a new project (no template or starter content needed)
2. Create a new Actor class blueprint of type Camera Actor > Name it "CameraBP"
3. Add 2 instances of CameraBP into the level
4. For the first camera Set the rotation to X: -90 Y: -89 Z: 180
5. Set the Second camera's rotation to X: -90 Y: -90 Z: 180
6. In the level blueprint add the references of the camera actors
7. Using the references get the actor rotation for each and print them out using the print string node
8. PIE
   Result: The printed values do not accurately match up to the values of the camera's rotation
   Expected Result: The printed values accurately match up to the values of the camera's rotation

How do I set a material as a post-processing material?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

How does TextureRenderTarget2D get TArray<uint8> type data?

How to delete some elements correctly when deleting an array loop?

any help with here I am using a relativly highpoly model with 4k displacement and still get this wagy edges

Проблема с сборкой проекта

trying to launch uefn and it is crashing and saying pakchunk4522 is courrupt, anyone have the fix for this?

How to convert the datasmith scene file to BluePrint. Create animations in BluePrint.

Why does the volume fog disappear from a distant view?

How to achieve HLSL Multiple Render Target in Material blueprints?