# Why are we not using integers in game physics?

We can use integer for game physics (or without physics, simply object representation): mass, position and rotation, where the integers represent, for example, the number of milligrams, millimeters or (1/56000) of a degree. However, almost all game code I've seen recently use floating points.

Is it slower to use integers for game physics calculations? Are there any other advantages and disadvantages from the developer's point of view for using integers? Or it is because all our hardwares

• floats are used because we want to represent continuous spaces like R.
– tp1
Jan 3, 2014 at 21:00
• Possibly the only benefit I could see, given the range and versatility of floating point, is a reduction in storage space down from 32 bits for a standard float. This might have some benefit on the GPU, for instance, where sending data across the bus comes at a premium. Jan 3, 2014 at 21:13
• Jan 3, 2014 at 21:43

The days where floating point computations were (significantly) slower than integer calculations are long gone. If I'm not mistaken it was the Pentium CPU that first leveled the playing field of floats vs integers.

So there's actually no reason whatsoever to not use float (or even double) for any calculation that benefits from it. The use of integers to represent floating points was just a crook in order to avoid the performance impact of floating point calculations on older hardware.

In fact modern (desktop) CPUs don't even make much of a difference between float and double, especially on 64bit CPUs running a 64bit OS.

• So you want to say that DDA and Bresenham drawing algorithms which use integers only, are no longer useful optimizations? I'd bet these will still be faster than naive float + round solution. Jan 4, 2014 at 13:58
• Anyway, I think it makes sense to use integers since everything - both time and space - in the game are discrete (pixels, time steps...) Jan 4, 2014 at 14:01
• @Tomas Betting is not knowing. ;) Besides to draw lines I can usually rely on glDrawLine and similar. And not everything is discrete, delta time for example. Also: subpixel rendering, anti-aliasing, and similar effects. Point being: even if there are optimized integer-based algorithms that may even to this day be faster, they typically aren't meaningful to most real world development being done today. Jan 4, 2014 at 14:16
• 1) anti-aliasing is for sure integer thing - it's the remainder in the DDA/Bresenham algorithms 2) and how is glDrawLine implemented? I'd bet (again :) its based on integer algorithms :-) Jan 4, 2014 at 14:44
• @Engineer Integer operations are very consistent across platforms. Fixed-point operations are implemented using integer operations (with scaling applied by the developer, who presumably would not scale differently on each platform). Dec 10, 2021 at 19:54

You can use integers for the inputs to your physics system. Although you're likely going to have to use non-standard units of measure. Typically we see meters per second, kilograms, etc. Using smaller units just so we can more easily round the values to whole numbers isn't hard, it's just kind of silly.

However, as soon as you want to perform any calculations, you're going to want to use floats, not integers. Any formula that has a division involved is going to want to use floating point values.

The reason we use floating point values is because it's closer to what we use in mathematics and real world physics. There's no reason to constrain ourselves to integers. Floating point calculations are very fast on modern CPUs.