

The planets, moons, other craft, buildings, etc. All parts of the spacecraft relate to that origin. In effect, the visible spacecraft that you see on screen is the ORIGIN of the universe. Instead of a single origin for the universe from which all x-y-z positions are related, the origin moves with the spacecraft. At some point, the spacecraft is no longer a single cohesive unit, and it explodes. However, as the craft proceeds into deep space at millions of kilometers from the launch site, the recalculated individual parts' x-y-z positions and rotations begin to "drift apart" (due to rounding errors). Visually, the spacecraft appears to be a single mass.

As the spacecraft moves, the x-y-z and rotations of the individual parts are all constantly recalculated. At launch, these parts are all "next" to each other. This x-y-z position (along with rotation about these axis) are related to the origin of the spacecraft itself. 34 bit precision would get you numbers that are 4 times more accurate than they are currently, 40 bit would get you 256 times more accurate.Įvery part on a spacecraft has an origin, an x-y-z position. You could always simply move to 40 bit precision or even 34 bit. That said, you don't neccessarily have to go out to 64 bit precision on your math. This would likely be a case where performance would suffer, as it would create a greater workload for the processor. So it isn't simply being able to address more memory, there are other benifits as well.Īlso as Leax256 pointed out, 64 bit would allow greater math precision.

The performance difference is usually pretty small, but we are talking generally in the realm of 3-10% is the typical speed up you can see from moving a program from 32-bit to 64-bit. Most programs/parts of programs run faster with a larger register space. There are some workloads that actually run slower with a larger register space, but those are few and far between. One perk though of 32-bit over 64-bit is that it allows larger registers to be used (how memory is addressed and instructions issued). At a likely rate of growth about roughly a doubling in RAM density every 2-3 years, we'll hit that cap on high end machines in about 20-30 years. Granted my desktop only has 16GB of RAM and most seriously loaded enthusiasts machines and workstations might have 64GB (I am ignoring servers).

I don't believe this is a limitation on the AMD64 instruction set though, but a limitation to Windows itself. However, 64-bit Windows is written such that it'll only allow 256TB of RAM to be addressed to reduce load.
