Has this been resolved yet, or do we still use 3.5 for better antialiasing?
I just noticed that my IRTC entry has jaggies when rendered in 3.6 vs. 3.5.
Oh well.

"Dave Matthews" <dma### [at] wrmnwestmnscuedu> wrote:
> Warp <war### [at] tagpovrayorg> wrote:
> >   Post-clipped antialiasing causes problems in a multitude of images
> > very frequently. You only have to have a surface which is much brighter
> > than 1 and a sharp edge adjacent to a dimmer surface (which is quite
> > a common situation) to get ugly pixelation of the edge. Pixels much
> > brighter than 1 are completely normal, not modelling flaws.
> >   Just look at The Kitchen image carefully to see the ugly post-clipping
> > artifacts (these were not taken into account in judging because it
> > was decided that these artifacts can be got ridden of in future
> > versions of POV-Ray).
>
> Thank you.  That explains something I saw and thought was some sort of a bug
> involving 3.6 and blobs (since that's where I happened to see the problem
> in my case.)  Aparently, though, it's caused by post-clipped antialiasing,
> since the problem occurs at a place where reflections and specularity
> combine to get very bright pixels.  I tried upping max_trace_level,
> cranking anti-alias down to 0 -- finally decided to just use the picture I
> made with 3.5.
>
> Dave Matthews

Post a reply to this message