I ran the update and 8Direction.MovingAngle still returns values like 44.9999... If the player walks diagonally long enough, the value gradually corrects itself, but this takes an unacceptably long time to occur (greater than three seconds). This is probably true for both versions.

Also, rather than having angles more than 180 degrees, the values instead switch to negative numbers (so moving upward is -90 instead of 270, etc.). Here is a quick illustration:

<center>Expected behavior:

<img src="http://dl.dropbox.com/u/25752478/8dirbug/standard.png" border="0" />

In Construct 2:

<img src="http://dl.dropbox.com/u/25752478/8dirbug/inconstruct.png" border="0" />

</center>

I understand this is intended behavior and is independent of issues with float rounding, but it's still nonstandard, undocumented behavior, and it works this way for no obvious reason. You can see an example of this making code more complex in the .capx file in the first post.

http://dl.dropbox.com/u/25752478/8dirbug/8dirbug.capx

8Direction.MovingAngle is unpredictable when moving at diagonals, because of what I'd guess to be a float rounding error. To see why this is a problem, walk orthogonally in the demo and move at a diagonal in the opposite direction without stopping.

This bug can be mitigated, but not wholly solved, by using the floor() function; the value returned by MovingAngle can be slightly below the correct value rather than above, and floor() only rounds downward.

NEW plugin: I look forward to it.

In the meantime, though, could you upload an example project using this plugin? The download doesn't come with one, and I can't figure out how light cells work. :c