|
 |
"clipka" <nomail@nomail> wrote:
> "JeffBTX" <nomail@nomail> wrote:
> > (1)(b) I thought I would try setting a "compatibility mode" for the desktop
> > shortcut (I did that with 3.6.1, it *might have* solved a couple of problems
> > under Vista back in 2007, but this is unverified) but the compatibility mode
> > settings for the shortcut are greyed out / un-set-able with 3.6.2 for some
> > reason.
>
> Heh, no surprise here: The main reason for releasing 3.6.2 was to provide a
> fully Vista compatible version of POV-Ray 3.6 :D
>
> So being installed as a "native Vista" binary on Vista systems, why should the
> OS offer any compatibility options? :P
Clipka;
Thanks much for your reply.... that makes sense. I've been playing with 3.6.2
all day, and now I have rendered many of the \scenes and some of the \portfolio
files... 3.6.2 seems to be working OK, except for a few very minor quirks.
Post a reply to this message
|
|
|
|
"clipka" <nomail@nomail> wrote:
> "JeffBTX" <nomail@nomail> wrote:
> > Antialias_Clipped is not covered in the documentation (revision.txt says that
> > the documentation WAS changed, but searching the CHM file I cannot find +ac,
> > +AC, or Antialias_Clipped). Would appreciate an explanation, I can't even guess
> > what "CLIPPING" is in relation to antialiasing...
>
> FYI: This refers to the clipping of overly-bright colors to the displayable
> range (0.0 to 1.0 in POV-Ray terms, or 0..255 in 8-bit RGB terms).
>
> With anti-aliasing active, "prehistoric" versions of POV-Ray clipped such colors
> on a *per-ray* basis, instead of the resulting pixel value. This seems to have
> been changed in the course of introduction of proper gamma handling, so that
> POV-Ray 3.6.1 clipped the colors on a per-pixel basis; note that this has the
> same effect as generating HDR output, and converting the image to 8-bit in a
> post-processing step.
>
> However, in some situations - especially with extremely-overly-bright objects in
> the scene - this approach may seem to give inferior results, which may be the
> reason why it was re-introduced later (as an option) in 2007 (but never
> released before; interestingly, it has also never been re-introduced to 3.7).
>
> However, I think it was an oversight to include the 2007 change into 3.6.2
> without at least changing the default to "off", as this has been the standard
> for years now.
>
> As already mentioned, POV-Ray 3.7 also invariably uses per-pixel clipping
> (unless HDR output is used of course, in which no clipping is performed at
> all).
.... then it sounds like something "not- to- worry- about", for someone
transitioning from 3.6.1 to 3.6.2 (I think...)
.... thanks for your reply Clipka.
Post a reply to this message
|
|
|
|
"JeffBTX" <nomail@nomail> wrote:
> .... then it sounds like something "not- to- worry- about", for someone
> transitioning from 3.6.1 to 3.6.2 (I think...)
Well, as it *does* change the behavior (again) from 3.6.1 to 3.6.2 (unless you
explicitly turn it off), I would consider it something to worry about. A bit. A
very tiny bit, to be frank. I wouldn't expect it to ruin your shot either way,
and I guess for most shots it will not make a difference at all.
Post a reply to this message
|
|
