Thanks for this! This tutorial was very helpful, I’ve been trying to get away from the Prefab thirdperson control system for a while now :)

Super helpful!

If you don’t believe, put a print() or Debug.Log():

Debug.Log(in_curFrame/in_gridX);

You will see that it never returns a float. So Math.ceil() here is redundant. Instead, because we are doing an integer division, we will always get a “round-down” result.

To understand it, I first think it is good to understand what each variable is

in_gridY = the total number of rows in the sprite map ( images will be across and stacked if more than 1)

in_curFrame = current state of the animation. If the sprite map is 3 horizontal by 2 vertical (6 states), this number could range from 1-6.

in_gridX = total number of images that go horizontal across the image map

The only time that conditional will be ran is if the sprite map has stacked images like a two story building would be stacked.

If a sprite map has 6 states(3 on the top, 3 on the bottom), the manager needs to know which row it is in. The bottom or the top?

Dividing the current state (in_curFrame) by the amount of horizontal states (3 in my example), it can find out if the image location is on the bottom or top. If it is on state 4, doing the Math.Ceil() will return 2, since 4/3 is more than one.

Going with our 3 x 2 sprite map, the main thing to see is that it divides the current element by the total elements horizontally. All it needs to know is that if the current state is 4, it needs to go to the bottom row to get the right image. The whole number is all that matters. You will always round up since there is no image at 3 1/2 places.

I don’t know if that was confusing, probably a picture would explain this a little more concisely and clearly.

if (in_gridY > 1) {
//If there is more than one grid on the y-axis update the texture
in_col = Mathf.Ceil(in_curFrame/in_gridX);
}

The problem is in_curFrame and in_gridX are both integers, and so in_curFrame/in_gridX will always return integer, e.g. 1/2 returns 0 and not 0.5. And so why Mathf.ceil???

If so, I think I’d be interested in buying a copy too. (I haven’t started on my next game yet, so I could switch to Unity. It’s something I’ve considered.)