Map property values

[sinewav]

Is there a limit to the numeric values in map properties?

For example, are these OK...?

<Wall height="99999999999"/>
<Wall height=".0000000001"/>

Thanks.

[Z-Man]

Is there a limit to the numeric values in map properties?

Yes, the limits in range and accuracy are those of standard single precision floating point numbers. The precision is around 1 in 10^6, the range is from -10^32 to +10^32.

For example, are these OK...?

<Wall height="99999999999"/>
<Wall height=".0000000001"/>

Yes.

[Jonathan]

Is there a limit to the numeric values in map properties?

Yes, the limits in range and accuracy are those of standard single precision floating point numbers. The precision is around 1 in 10^6, the range is from -10^32 to +10^32.

Precision is better than 1 in 10^7 (scaled by the magnitude of the number), at least before accumulating rounding errors. Range is over ±10^38. Not that it matters for a typical map.

P.S. Thanks in advance for nitpicking this nitpick by mentioning denormals and everything else there is to know about floating point.

[ivantis]

what would happen if you maxed out a variable's type in an occasion like that? server crash?

[Jonathan]

I think you'll get some weirdish physics and graphics at most.

[sinewav]

I think you'll get some weirdish physics and graphics at most.

Maybe that's how you made your avatar?!

[Jonathan]

Nope. There's no floating point at all, besides normalization and gamma correction of the final integer samples.

[sinewav]

This might be interesting to note. I had a map with the property and value <Wall height=".0001"> work locally, but not on a 0.2.8+sty server. I changed the value to ".001" and it worked. I don't imagine this being a recurring problem in the future; I just thought I would mention it. Unfortunately, I don't have access to the log to get the error message, but I bet it could be easily recreated if anyone cares to look into it.