# SEVERE BUG IN 4.18.2

**URL:** <https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974>\
**Category:** Cinematics & Media\
**Tags:** bug, unreal-engine, question\
**Created:** [January 7, 2018, 8:27pm UTC](https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974 "2018-01-07T20:27:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_b1038657](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b1038657](https://forums.unrealengine.com/u/anonymous_user_b1038657)\
**Post date:** [January 7, 2018, 8:27pm UTC](https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974/1 "2018-01-07T20:27:47Z")

</div>

In 4.18.2, whenever you add a camera and rotate Z 90 degrees, and then put it in Sequencer, the rotation changes itself to 89.999992.

When you fix it back to 90 degrees, and add a keyframe in Sequencer, it changes itself back to 89.999992.

This never happen in 4.16 or before. It only happens in 4.18.2. It is screwing up my work.

Please solve this issue.

---

<div class="post-metadata">

**Author:** ![Shadowriver](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Shadowriver](https://forums.unrealengine.com/u/Shadowriver)\
**Post date:** [January 7, 2018, 8:58pm UTC](https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974/2 "2018-01-07T20:58:55Z")

</div>

I don’t think it’s a bug and this actually CPU doing, float point values are not 100% precise due to way they are store in memory

> **[Floating-point arithmetic](https://en.wikipedia.org/wiki/Floating-point_arithmetic)**
>
> In computing, floating-point arithmetic (FP) is arithmetic that represents real numbers approximately, using an integer with a fixed precision, called the significand, scaled by an integer exponent of a fixed base. For example, 12.345 can be represented as a base-ten floating-point number:
> In practice, most floating-point systems use base two, though base ten (decimal floating point) is also common.

> **[Why are floating point calculations so inaccurate?](https://effbot.org/why-are-floating-point-calculations-so-inaccurate/)**
>
> Why are floating point calculations so inaccurate?

So even if UI will show you 90.0 calculations based if ut still be perfect either way.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b1038657](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b1038657](https://forums.unrealengine.com/u/anonymous_user_b1038657)\
**Post date:** [January 8, 2018, 2:21am UTC](https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974/3 "2018-01-08T02:21:40Z")

</div>

It is affecting my animations. It is not just 90 to 89.999992, but happening to any other values, for example 180 will become -179.999985 °, 230 will become -129.999985 °, etc. In my sequencer animation i need to rotate the camera from left to right, but after it changes itself, its rotating the opposite way! and not even correctly in the opposite way.

My animation is totally screwed up! I redownload 4.16 but it says my map is not convertible back to a older version of engine.

I feel like slapping myself for downloading 4.18. Should be more cautious next time.

Is there any reason why Epic is doing this to 4.18? It was never like this in 4.16 or earlier versions.

Please help!

---

<div class="post-metadata">

**Author:** ![Daverkex](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Daverkex](https://forums.unrealengine.com/u/Daverkex)\
**Post date:** [January 8, 2018, 7:01pm UTC](https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974/4 "2018-01-08T19:01:35Z")

</div>

This issue is duplicate from [Sequencer Bug: Camera Rotate - Cinematics & Media - Unreal Engine Forums](https://answers.unrealengine.com/questions/351738/sequencer-bug-camera-rotate.html) and is logged with UE-22228. I hope Epic will solve this problem as soon as possible.But the problem isn’t a numerical representation.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b1038657](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b1038657](https://forums.unrealengine.com/u/anonymous_user_b1038657)\
**Post date:** [January 9, 2018, 12:00am UTC](https://forums.unrealengine.com/t/severe-bug-in-4-18-2/413974/5 "2018-01-09T00:00:05Z")

</div>

Seriously i think 180 should be 180 and not -179.999985, 230 should be 230, and not -129.9999985. etc

This just makes Unreal engine look bad.
