> The point is to not give the user this freedom.  It causes a lot of people
> to report holes and other bugs in isosurfaces because they simply forget
> about or (worse) don't understand max_gradient.  Only a warning gets their
> attention.

But a max_gradient value that's too high will not cause problems except a
difference in rendering speed. So can't you have it only warn when the
max_gradient is set too low (unless evaluate is being used)?

Post a reply to this message