Bug Fix - Better Contour Textures

Thanks! You hit a corner case I never encountered,
and I am still puzzled why it occurs. Both the stored
distance and the newly computed distance are doubles,
and the stored value is computed by exactly the same
code as the new value.

I would expect an error like this if I had compared a
float and a double, or relied on two different computations
of a complicated expression where e.g. the terms were
summed in different order to return exactly the same
result, but this puzzles me. Anyway, thanks for the fix!

Other interesting sites

Better Contour Textures

by an anti-aliased distance transform

Other interesting sites

墟之城

welcome

星际异常管理局

Albums-template