On Thu, 06 Dec 2001 13:09:24 +0100, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <3c0f53e6.788389@news.povray.org> , ken### [at] uniplanit (Angelo 
>'kENpEX' Pesce) wrote:
>
>> Mhmm... I think that the raytracer should support those surfaces
>> directly as it's hard for a modeller to do accurate tessellation. I
>> know if I have only one big nurbs model and an infinite plane, i can
>> use max tessellation and go with this... But if I have a complete,
>> complex scene, with many nurbs characters and a complex background, I
>> don't want to alter manually the tessellation parameters for every
>> object if it's far away or near the camera...
>
>Ah, so the modeler can't do good tessellation and POV-Ray should magically
>be able to do a better job with the same input data?
Yes it should. Just because it's impossible for the modeller to do a
really good work, and because even if it's possible, you'll end up
with a gigabyte script and huuge parsing times even for a small
animation. That's why *nearly all* raytracers used with nurbs
modelling tools support directly nurbs as I demonstrated in another
post

Post a reply to this message