Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> Folks,
>
> I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> some of you could test it as the installer in particular is a re-write.
>
>   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
>
> Note: on Vista systems, the files will be installed by default to your
> local profile. On XP and earlier, the default remains Program Files.
>
> -- Chris

I uninstalled 3.6.1c a few days ago, and just now installed 3.6.2 (64 bit; Vista
Home Premium 64) about 30 minutes ago.

Before running the installer under Vista I set to -> "unblock". At some point
after running it a couple of times from the desktop shortcut (but I haven't
rendered anything yet), I have set the desktop shortcut to "Run as
Administrator"; no particular reason, I just did that with 3.6.1 back in 2007
when I got my new Vista computer, and I thought it might help with the "HELP"
problem mentioned in para (2) below (it didn't fix the problem).

DURING installation, I forced the install folder to "C:\POV-Ray\", due to some
old Vista oddities that became apparant when I installed 3.6.1 back in 2007.

(1)(a) Splitting off the INI files, scene files, etc into - > Documents is VERY
confusing. Why not just intall these into the POV-Ray installation folder? (In
my case under C:\POV-Ray\).

I have two (500 Gb) hard drives in a RAID 1 config, "Documents" is on D:\ (thats
just the way my computer builder set it up back in 2007). So now POVRay is on
C:, the INI files and so forth are shoved into D:\Documents. I ** think ** I
have figured out how to "transplant" all of the stuff from D:\Documents into
C:\POV-Ray (where they belong, in my opinion...), and alter things so that the
"transplants" are recognized - I don't want to fool with it until after I get
some replies to this... hopefully with a precise procedure to follow.

(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.

(1)(c) When I FIRST ran the desktop shortcut, it (Vista) did not know where to
find the executable. I had to "Browse" to it manually the first time.

(2) While IN POV-Ray, clicking "Help" has no effect. Neither does any "Help with
This Menu". I have to manually navigate into C:\POV-Ray\help\, and click on the
povray36.chm file. I invoked REGEDIT.EXE and searched for povray36.chm, and
NONE of the ini files seem to point to the help files. How do I fix this?

I CAN work with 3.6.2 the way it is, but I would rather "fix it" (if possible).
If there is something different that I could do during installation, I am
prepared to UNinstall 3.6.2 and re-install it.

.... and one reason that I am reporting these oddities is to (hopefully) prevent
them from appearing whenever 3.7 is officially released (in my history w/
POVRay, I am reluctant to even try betas, I tend to wait for the official
releases).

- Thanks

Post a reply to this message

"JeffBTX" <nomail@nomail> wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> > Folks,
> >
> > I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> > some of you could test it as the installer in particular is a re-write.
> >
> >   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
> >
> > Note: on Vista systems, the files will be installed by default to your
> > local profile. On XP and earlier, the default remains Program Files.
> >
> > -- Chris
>
> I uninstalled 3.6.1c a few days ago, and just now installed 3.6.2 (64 bit; Vista
> Home Premium 64) about 30 minutes ago.
>

Never mind and sorry, to an extent... I think I now see why the INI files (etc)
were forced into \Documents (sorry, I should have done that forum research
BEFORE I made my post).

Okay, then... I can assume that it will be this way (probably) for 3.7, as a way
of coping with the Vista "Program Files and Ini Files" problem.

Can I ALTER POVRay so that all files (includes, ini's, etc) are copied (moved)
from D:\Documents into C:\POV-Ray, and this will be recognized and it will work
properly? (I THINK I see how to do this, but better wait for a reply or three
before I try it).

How do I fix the Help File problem? POV-Ray 3.6.2 under Vista (installed into
C:\POV-Ray) is not invoking the help file (povray36.chm). I have to do invoke
the help file manually/ separately. I CAN work with this, but it is
inconvenient. (and kind of foolish... clicking "HELP" does not "help". Its kind
of like... you hire contractors to build you a new house, but your porch light
switch turns on the dishwasher, and turning on the dishwasher does nothing...
or perhaps raises your neighbor's garage door).

Post a reply to this message

ALSO....

I just rendered one scene from Advanced to get started... Sounds are apparantly
NOT working. I just rendered "biscuit.pov" from \advanced, no sound when done.
I double checked Render -> Sound settings.

Post a reply to this message

Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> Folks,
>
> I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> some of you could test it as the installer in particular is a re-write.
>
>   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
>
> Note: on Vista systems, the files will be installed by default to your
> local profile. On XP and earlier, the default remains Program Files.
>
> -- Chris

"StephenS" <nomail@nomail> wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> ....
> > I'd appreciate it if
> > some of you could test it as the installer in particular is a re-write.
> ....
> Installed and ran without issue, WinXP sp3 media center edition.
>
> Looking through the changes I see the new +ac/Antialias_Clipped option,
> interesting :-)
>
> Stephen S

Apparantly "+AC" is on by default....(?)

.... this is new to me, it is apparantly not covered in the help file that was
distributed with POV-Ray 3.6.2 for Windows.

The help file needs to be updated for 3.6.2

What is "Antialias_Clipped"?

Post a reply to this message

"JeffBTX" <nomail@nomail> wrote:
> ALSO....
>
> I just rendered one scene from Advanced to get started... Sounds are apparantly
> NOT working. I just rendered "biscuit.pov" from \advanced, no sound when done.
> I double checked Render -> Sound settings.

Nevermind...

I figured out how to get 3.6.2 re-pointed to the proper place to play the
sounds.

Problem was:
The 3.6.2 installer, by default, sets some paths to users ... AppData ...
roaming ... (etcetera); and I installed to C:\POV-Ray (forced during the
install), but the installer does not take that into account. Fixed within
POV-Ray by invoking the Render menu -> Sounds -> and re-pointing to the actual
WAV locations in C:\POV-Ray.

Also... fixed the Help File problem by copying the C:\POV-Ray\help directory
(and contents) into Users\(ID)\AppData\Roaming\POV-Ray\v3.6\

Its looking like I should have just installed to the default directory that the
3.6.2 installer wanted to install to in the first place? Is that right? And to
avoid the Vista versus INI Files in Program Files problem, the installer places
INIs and INCLUDES (etc) into \Documents?

I am just going to uninstall / reinstall I think.

Post a reply to this message

"JeffBTX" <nomail@nomail> wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> > Folks,
> >
> > I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> > some of you could test it as the installer in particular is a re-write.
> >
> >   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
> >
> > Note: on Vista systems, the files will be installed by default to your
> > local profile. On XP and earlier, the default remains Program Files.
> >
> > -- Chris
>
> "StephenS" <nomail@nomail> wrote:
> > Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> > ....
> > > I'd appreciate it if
> > > some of you could test it as the installer in particular is a re-write.
> > ....
> > Installed and ran without issue, WinXP sp3 media center edition.
> >
> > Looking through the changes I see the new +ac/Antialias_Clipped option,
> > interesting :-)
> >
> > Stephen S
>
> Apparantly "+AC" is on by default....(?)
>
> .... this is new to me, it is apparantly not covered in the help file that was
> distributed with POV-Ray 3.6.2 for Windows.
>
> The help file needs to be updated for 3.6.2
>
> What is "Antialias_Clipped"?

In revison.txt for 3.6.2:
Change 4387 on 2007/04/13 by chormann@chho

  [docs] adding documentation for the +ac/Antialias_Clipped option

I cannot find this anywhere.

Post a reply to this message

Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> Folks,
>
> I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> some of you could test it as the installer in particular is a re-write.
>
>   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
>
> Note: on Vista systems, the files will be installed by default to your
> local profile. On XP and earlier, the default remains Program Files.
>
> -- Chris

Okay... SINCERELY SORRY about the "static" that I posted over the past couple of
hours... it was due to a knee-jerk reaction to differences between 3.6.1 and
3.6.2 installations under Vista.

I have re-installed into the *default* directory as suggested by the installer
(C:\Users ... AppData ... Roaming ... Confusing_Vista_Path_Stuff ... etcetera).

Everything is working fine. I can live with those critical files being in
D:\Documents. If this is the way that 3.7 is going to work (thanks to Microsoft
& Vista) thats OK I will get used to it (you have to remember that I am a
semi-senile old fart that built his first computer in 1978, and still sort of
misses DOS... actually I HAVE a legacy DOS 6.22 machine in the corner, that I
power up from time to time...).

One issue left; Documentation for 3.6.2 appears to need updating.

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...


Things like...
"Change 4428 on 2007/04/25 by calimet@lavender"
"photons change 3379"
(is this an "under the hood fix", or has photons changed to an extent that there
is something that users need to know?)

.... and possibly other things.

Post a reply to this message

Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> Folks,
>
> I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> some of you could test it as the installer in particular is a re-write.
>
>   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
>
> Note: on Vista systems, the files will be installed by default to your
> local profile. On XP and earlier, the default remains Program Files.
>
> -- Chris

POVRay 3.6.2, installed under WinVista Home Premium 64 bit;

For Options -> Editor Window -> Create Backups; I could not disable this by
clicking (changing from Checked to UnChecked). I had to use regedit.exe to hack
it.

.... might be an issue that will occur with 3.7, if not fixed.

Post a reply to this message

"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

Post a reply to this message

"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).

Post a reply to this message