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

Post a reply to this message

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

Post a reply to this message

Um, I will say great thing first and thank you Chris.

You did say in Vista it will go into the user profile... I'm in Windows 7 RC 
(build 7100) and I thought it might be the same way you have it for the 
POV-Ray beta, going into the documents folder with a POV-Ray parent folder 
in there.
This install turned out like earlier P-R betas and went into AppData\roaming 
so the scene files are hidden away. Hopefully not something to do with 
already having the old 3.6.1c in Program Files.

BTW the old POV-Ray icon sure would look better if done like the beta, 
smooth alpha AA. I use the appearance difference to my advantage, of course, 
but I guess we will need to keep them both different and nice-looking...? 
;)

P.S.
I had looked at the install log when asked and noticed at the end it 
mentions a reboot = yes. Nothing asked or happened at the end so I restarted 
Windows 7 but before I did I found the Explorer (user folders and files) 
wasn't allowing me to change settings to show hidden files. Also a padlock 
over the user name icon. Could be my ineptitude about this particular thing 
but thought I better mention it.

Bob

Post a reply to this message

BobH wrote:
> You did say in Vista it will go into the user profile... I'm in Windows 7 RC 
> (build 7100) and I thought it might be the same way you have it for the 
> POV-Ray beta, going into the documents folder with a POV-Ray parent folder 
> in there.

Nope, it was too much work to split the program locations in v3.6, it's an
old code base. This is really just a maintenance release to get it working
on Vista.

> This install turned out like earlier P-R betas and went into AppData\roaming 
> so the scene files are hidden away. Hopefully not something to do with 
> already having the old 3.6.1c in Program Files.

Nope, nothing to do with that. It does create a shortcut to the scene files
on the desktop, though.

> BTW the old POV-Ray icon sure would look better if done like the beta, 
> smooth alpha AA. I use the appearance difference to my advantage, of course, 
> but I guess we will need to keep them both different and nice-looking...? 

Which icon didn't come out well? The program itself, the shortcuts, or the
menu items?

> I had looked at the install log when asked and noticed at the end it 
> mentions a reboot = yes. Nothing asked or happened at the end so I restarted 

Not sure why that's there, must be some installshield thing that sets up a
reboot if required. However certainly for POVWIN it's not needed.

> Windows 7 but before I did I found the Explorer (user folders and files) 
> wasn't allowing me to change settings to show hidden files. Also a padlock 
> over the user name icon. Could be my ineptitude about this particular thing 
> but thought I better mention it.

Thanks for mentioning it. While I can't explain what that would be caused
by, I'd be surprised if it was the installation.

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a193ca8$1@news.povray.org...
> BobH wrote:
>> You did say in Vista it will go into the user profile... I'm in Windows 7 
>> RC
>> (build 7100) and I thought it might be the same way you have it for the
>> POV-Ray beta
>
> Nope, it was too much work to split the program locations in v3.6

Ok, just wasn't sure what was meant before.

> It does create a shortcut to the scene files on the desktop

Yep, got that... :) wondering if naming it 3.6 instead of 3.62 might confuse 
people.

>> BTW the old POV-Ray icon sure would look better if done like the beta,
>> smooth alpha AA. I use the appearance difference to my advantage, of 
>> course,
>> but I guess we will need to keep them both different and nice-looking...?
>
> Which icon didn't come out well? The program itself, the shortcuts, or the
> menu items?

Program. A "jaggy" perimeter causing an ugly gray and black edge. Well, ugly 
compared to the new 3.7 one and compared to most other programs.
Main point being different icons will be needed or else there's no visual 
cue to know which is which, not that it matters if a previous 3.6 version is 
present.
Maybe you don't need to see them but I'll post at p.b.i  those two icons 
from my Vista's recent programs list.

Oh, and install into Vista went perfectly fine just haven't checked actual 
changes yet. No news will be good news on that.

Bob

Post a reply to this message

BobH wrote:
> Program. A "jaggy" perimeter causing an ugly gray and black edge. Well, ugly 
> compared to the new 3.7 one and compared to most other programs.

This should be fixed now. Please try again, filename is now:

  http://www.povray.org/temp/POVWin-v3.62.msi

Unless problems crop up I intend this to be the actual release (hence no RC
suffix).

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a1a8d32@news.povray.org...
> BobH wrote:
>> Program. A "jaggy" perimeter causing an ugly gray and black edge. Well, 
>> ugly
>> compared to the new 3.7 one and compared to most other programs.
>
> This should be fixed now. Please try again, filename is now:
>
>  http://www.povray.org/temp/POVWin-v3.62.msi
>
> Unless problems crop up I intend this to be the actual release (hence no 
> RC
> suffix).

Looks good! The install asked me to uninstall the previous one so that 
answers a question I was wondering as to whether or not a backup was 
possible same as earlier 3.6 installs. Guessing the idea is clean installs 
only...?

Got to say it... program and scene file location is bothersome to me.
Going into the desktop shortcut and running a file from there or dragging it 
into POV does okay, yes, but when trying to open a file from within POV it 
wants to go elsewhere and the hidden scenes location is lost. I presume this 
is in part due to the install finding the file open location where 3.6.1c 
was last at.

This is worsened by Vista not allowing folder and file view settings to be 
changed (same as what happened in Windows 7) so getting to the new location 
is impossible at first. I thought maybe having a file opened from the 
desktop shortcut would update the File|Open but it didn't.

I'm sure this particular aspect would be good to hear observations from 
other people not just me.

I've only tried several renders, all seems right so far.

Bob

Post a reply to this message

BobH wrote:
> This is worsened by Vista not allowing folder and file view settings to 
> be changed 

Press the ALT key, and you get all the XP menus back. There's also a hack to 
turn it on permanently.

-- 
   Darren New, San Diego CA, USA (PST)
   There's no CD like OCD, there's no CD I knoooow!

Post a reply to this message

"Darren New" <dne### [at] sanrrcom> wrote in message 
news:4a1ac9ce$1@news.povray.org...
> BobH wrote:
>> This is worsened by Vista not allowing folder and file view settings to 
>> be changed
>
> Press the ALT key, and you get all the XP menus back. There's also a hack 
> to turn it on permanently.

Not here, although I think I know what you meant Darren.
What I'm seeing happen in the File|Open dialog is just the Organize 
drop-down with the "folder and search options" inaccessible. ALT doesn't 
change anything here.

To get back into AppData\Roaming\POV-Ray\v3.6\Scenes I must first change the 
"view hidden files" setting outside of POV to see it in the open file 
dialog.

Both Vista and 7 are like this for me. Interestingly, I did have the hidden 
path in the folder path drop-down list while in Vista, yet not in 7. Just 
wasn't thinking of looking there before.

So I'm still believing this could be trouble because navigating away from 
these hidden files (while files are set to be hidden, the default) then 
later try to return it becomes likely you won't be able to use the open file 
menu to get there until changing to view hidden files again (outside POV, as 
said already).

Hope I'm making sense.

Bob

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a1a8d32@news.povray.org...
> BobH wrote:
>> Program. A "jaggy" perimeter causing an ugly gray and black edge. Well, 
>> ugly
>> compared to the new 3.7 one and compared to most other programs.
>
> This should be fixed now. Please try again, filename is now:
>
>  http://www.povray.org/temp/POVWin-v3.62.msi
>
> Unless problems crop up I intend this to be the actual release (hence no 
> RC
> suffix).
>
> -- Chris

Hi Chris,

The install went smoothly on Vista 64 but it intalled the 32 bit version 
rather than the 64 bit version. I presum the 64 bit compile will be made 
available in a different dowload package once you have time to put it 
together?

Ken Tyler

Post a reply to this message

BobH wrote:
> To get back into AppData\Roaming\POV-Ray\v3.6\Scenes I must first change 
> the "view hidden files" setting outside of POV to see it in the open 
> file dialog.

Oh, that's what I was talking about. The option to get to "view hidden 
files" is hitting ALT in Explorer. They hid the "normal" menu bar.

I agree that putting the user's data files under AppData seems like the 
wrong place. If you can use it with other programs (e.g., text editors), it 
should probably go under "My Documents" somewhere.

> Hope I'm making sense.

Yes.

-- 
   Darren New, San Diego CA, USA (PST)
   There's no CD like OCD, there's no CD I knoooow!

Post a reply to this message

Ken wrote:
> The install went smoothly on Vista 64 but it intalled the 32 bit version 
> rather than the 64 bit version. I presum the 64 bit compile will be made 
> available in a different dowload package once you have time to put it 
> together?

Hi Ken,

Yes, the version of InstallShield I've got doesn't allow me to make dual 32
and 64-bit installers. I'll make the 64-bit one available once the 32 is
settled.

regards,

-- Chris

Post a reply to this message

BobH wrote:
> Looks good! The install asked me to uninstall the previous one so that 
> answers a question I was wondering as to whether or not a backup was 
> possible same as earlier 3.6 installs. Guessing the idea is clean installs 
> only...?

This isn't really under my control, it's a Windows Installer thing, so yes
- clean installs only. It's also why I use a different install path (even
on Windows XP); there's no way for me to tell Windows Installer to backup
the old files, especially files that weren't installed by it (as 3.61c did
not use WI).

> Got to say it... program and scene file location is bothersome to me.

I don't like it either. I feel uncomfortable having everything in the one
place (which is why I fixed it in 3.7). However the code refers to the
install path in many places and since the codebase is now so different
between v3.6 and v3.7 I'd basically have to do all the changes over again.

But thinking of it, I really think you're right. I might just have to go in
and do it.

> wants to go elsewhere and the hidden scenes location is lost. I presume this 
> is in part due to the install finding the file open location where 3.6.1c 
> was last at.

This would be due to the shared registry settings.

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a1b930d$1@news.povray.org...
> BobH wrote:
>
>> Got to say it... program and scene file location is bothersome to me.
>
> I don't like it either. I feel uncomfortable having everything in the one
> place (which is why I fixed it in 3.7). However the code refers to the
> install path in many places and since the codebase is now so different
> between v3.6 and v3.7 I'd basically have to do all the changes over again.
>
> But thinking of it, I really think you're right. I might just have to go 
> in
> and do it.

Which is why I didn't want to make you feel pressured to do that just for my 
own sake. I'm sure you would rather consider this new 3.6 version finished.

The way it's an update to 3.6 I know most people will find all this to be a 
problem, too, when they try to go from the old to new. I thought it might 
not matter if no previous file were already left open in 3.6.1c when last 
used. What I really didn't expect (but probably should have) was 3.6.2 
finding one elsewhere even when no open files were left in editor, by going 
into File|Open.

For me, not so much a problem if the file view settings had not locked me 
out. That made me believe it was causing trouble for either Windows, or POV 
itself had difficulty interfacing with the file system, or whatever other 
reason unknown to me. I've only kept everything as administrator status, no 
other user account exists.

Bob

Post a reply to this message

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

I've updated this to RC2, which includes splitting the binaries and text
files dirs.

    http://www.povray.org/temp/POVWin-v3.62-RC2.msi

Scenes, INI files, etc, will be installed to "My Documents\POV-Ray\v3.6"
(or the equivalent).

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a1bcd68$1@news.povray.org...
>
> I've updated this to RC2, which includes splitting the binaries and text
> files dirs.
>
>    http://www.povray.org/temp/POVWin-v3.62-RC2.msi
>
> Scenes, INI files, etc, will be installed to "My Documents\POV-Ray\v3.6"
> (or the equivalent).

Wow, that was fast! A tremendous thank you from me to you. So much better 
this way.

Guess I'm going to be removing 3.6.1c after I check this new one awhile, 
MegaPOV, etc.

Hmmm. Some tidying up to do in that first install location, the uninstall 
left renders in there because I didn't change from default file output.  : )

Bob

Post a reply to this message

"BobH" <omniverse*charter!net> wrote in message 
news:4a1c0e57@news.povray.org...
>
> Guess I'm going to be removing 3.6.1c after I check this new one awhile, 
> MegaPOV, etc.

Trouble with library paths using megapov, needed to move its includes into 
the v3.6\includes. Seems peculiar that it didn't want to use the 
Library_Path= I added for its own location(s).
So to anyone else doing megapov+v3.6.2, put the files into the v3.6 
locations (unless you have success any other way first). I just didn't want 
to mix them but this was the only way.

Post a reply to this message

Another pass at a hopefully final 32-bit binary and installer:

  http://www.povray.org/temp/POVWin-v3.62.msi

The only significant difference between this and RC2 is that libpng has
been updated to the latest available.

-- Chris

Post a reply to this message

Ken wrote:
t smoothly on Vista 64 but it intalled the 32 bit version
> rather than the 64 bit version. I presum the 64 bit compile will be made 
> available in a different dowload package once you have time to put it 
> together?

Hi Ken,

Please give this a try:

  http://www.povray.org/temp/POVWin-v3.62-64bit.msi

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a2252f6@news.povray.org...
> Ken wrote:
> t smoothly on Vista 64 but it intalled the 32 bit version
>> rather than the 64 bit version. I presum the 64 bit compile will be made
>> available in a different dowload package once you have time to put it
>> together?
>
> Hi Ken,
>
> Please give this a try:
>
>  http://www.povray.org/temp/POVWin-v3.62-64bit.msi
>
> -- Chris

Worked just peachy, Chris. The install was clean and the renderer appears to 
be fully functional.
I'll beat up on it for a while but the few scenes I've rendered so far look 
good.

Ken

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

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

"JeffBTX" <nomail@nomail> wrote:
> 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.

Just for additional info: Works fine under Windows XP Professional x64 Edition.

Post a reply to this message

"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