That hint about the averaging/smoothing step was
a good one, never really thought about it that way.
In my mind, it was more like a "take the adjacent
sides" in order to "know what height is coming at this
pixel", rather than thinking of it as smoothing.

I'll keep on experimenting. Hopefully I don't have to
rewrite my Mesh-Macros, cause I somehow expected
that connecting four corners with triangles via checking
shortest connection might harm the resulting mesh,
but perhaps the "original" algorithm works better just
for pixel-waves, rather than mesh waves. Its funny though
that I cannot find much about mesh waves on the net,
its just always the pixel-code.

Looks like people are just too possessive about how they
came up with things (there's always that second thing about
people getting it to work, and then just forget what they
did, cause they're just using it, instead of thinking about it).

Regards,
Tim

--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

Post a reply to this message