|
![](/i/fill.gif) |
In article <3a9e2cf2@news.povray.org>, Warp <war### [at] tag povray org>
wrote:
> If this is a problem, then outputting to a 48-bit png can help a lot
> (you get basically 65536 depth values instead of the usual 256).
Why not a TGA or ordinary 24-bit PNG with hf_gray_16 enabled?
There should be a high-precision grayscale format somewhere out
there...it'd be nice to store large height fields without the wasted
space.
But anyway, there may still be problems with resolution...areas with a
high slope will get fewer triangles, and you may have trouble getting
them smooth. And holes inside the object or through the sides will not
work correctly. An intersection of several height fields may help some
of this, but will get slower and more memory consuming...the best option
is to simply convert it to a mesh and use MegaPOV.
--
Christopher James Huff
Personal: chr### [at] mac com, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tag povray org, http://tag.povray.org/
<><
Post a reply to this message
|
![](/i/fill.gif) |