• texturing: if you choose 256, 256x256 is your base texture size and (in a wider sense) more detailled than a lower measure
• if you take a small measure, you could have problems with collision precision, physics eventually
• if you take a measure which is very great, you could exceed on large maps the native map size and you could get errors at the bounds
• if you take a very small measurement, you can eventually get in trouble when you do extensive division calculations
• if you take a measure that is kinda proporional to the decimal 10-base, your calculations, etc., may be more "natural"; or: if you do reconstruction you can work precisely

• tables with 30cm thick plates ^^
• too thin walls... imagine a grenade-explosion next to a 5cm thin wall and it will remain undestructed, ouch
• in first person games: the enemies are way too big or way too small
• I am standing on a plaza and the tiles beneath my feet are 10x10 centimers big (too small) or 10x10 meter ^^
• measurement faults appear often when textures are wrong scaled: you see a very shrinked texture next to a texture which seems to have scaling factors == 1000
• bullets are as big as fists
• city skyscrapers are reaching the sky, but the streets are as wide as my bedroom and as long as the way to my toilet

Quote:

---

but since models replace more and more the scenery, the quants get less important.

---