[BUG] Rotators report wrong values for first frame when going past -180~180 range

I’ve been using Rotators in Blueprints to set up Line of Sight checks.

However, I’ve noticed that when if you cross 0, 180 or -180 then the Rotators frequently report a value beyond the -180~180 range in Blueprints for the first frame of being beyond the range, before correcting themselves on the frame afterwards.

This can lead to bugs in peoples logic when they’re exclusive dealing with values within the range.

Hi Jimmy,

Could you post some screenshots of your setup to help us understand how you are using them?

I’m breaking the Rotators into Floats and then comparing the Yaws and Pitches against each other to create a view cone.

If I print the the Broken Rot results out on screen then I get occasional frames in which the numbers go beyond the Rot range.

Hi Jimmy_Jazz,

I’m sorry it’s been a few days. I haven’t been able to get your results yet. Which version of the editor are you currently using?

Hi Jimmy_Jazz,

We haven’t heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you’re still experiencing this issue, please feel free to post back here with additional information.

Thanks,
TJ