3 ms·
You're right that normally a more important consideration for production is consistent units. The units do matter though, since the absolute float value is wha
by dahart 9y ago
You're right that normally a more important consideration for production is consistent units.
The units do matter though, since the absolute float value is what determines your precision.
The author of this article translated by 200k units, so the precision loss is relative in this case. But artists might need to translate something 100 meters, so their precision loss depends completely on their choice of units.
- Const-me 9y ago> their precision loss depends completely on their choice of units. If an artist needs to translate a model 100 meters off center, and the model is in meters, the graph you’ve linked says the precision will be 10^(-5) model’s units, which is 0.01mm. If the same model is in mm, the graph says the precision for 100*1000 will be 10^(-2) model’s units, which is the same 0.01mm. As you see, it's independent on the choice of units.
- dahart 9y agoHow big can my world be in meters if I require at least 0.01mm precision and I model things in millimeters? Does that number change if I model in meters?
- fyi1183 9y agoBecause of how floating point works, it doesn't matter. The difference between modelling in meters or millimeters disappears in the exponents. What matters for precision is the mantissa, which is 23 bits in single precision floats. So you get ~16 million of your smallest unit before you're losing precision, counting the implied leading 1. You can double that to ~32 million by using the sign bit. Edit: this translates to 320m if you want 0.01mm precision.
- Const-me 9y agoAbout 0.008 km^3, each coordinate between -100 and +100 meters. The number's the roughly the same even if you'll model in km or imperial units.
- dahart 9y agoYeah, you're right. Brain fart. I'm mis-remembering production stories instead of thinking clearly about floats, despite having just linked the precision chart. :P