Only one minor problem encountered here, been using the same povray.ini 
copied to each new installation and apparently Output_File_Name= requires a 
final backslash \ in the path (if just a folder is used) or else an error 
about not being able to write the "pov state" file happens.

c:\renderings\  is ok,  c:\renderings  is not.

Not a problem for the installed povray.ini since it doesn't have that added 
until someone does so but thought I better mention it since it isn't obvious 
at first what's going wrong.

Another change I had when going from beta 28 to 29 is Library_Path= was 
causing problems when finding older files while biscuit.pov was being tried 
after the install.
Examples like keyword  version  needed a semi-colon, and logo.inc had 
undeclared things because they weren't included ahead of calling that file. 
These trouble files were from ver. 2.0 and 3.0, I realize, but what 
surprised me was how the same setup went unnoticed until now. Maybe I was 
overlooking message stream warnings before and this new beta opens the 
offending files and stops render.

I'm posting about all this more for the reason to give a heads up for anyone 
else it happens to. Maybe this has an explanation I didn't read or have 
forgotten.

On another note, I really like the new message window text colors. Great 
idea there.

Oh, and lastly... I found the uninstall (done from Program Files not Control 
Panel) doesn't totally clean out the AppData\Roaming\Povray\ subfolders (not 
Local but Roaming in my case anyway), same as most any uninstall, so beta 
testers will probably want to go in there and manually take care of the move 
(remove duplicates...?) to the new location at Documents. Obvious enough, 
right? But these --hidden folders might get overlooked by some people and 
cause confusion until-- or when-- this is far in the past as the betas move 
onward.

I'm really glad these are getting put out into Documents, for lack of a 
better place anyhow. My preference would actually be directly under the user 
name, parent folder of Documents, but I won't ask for that myself alone. 
Could be easier to work with in Documents anyhow for the pre-Vista Windows.
: )

Re-reading the above I probably shouldn't have said anything about duplicate 
files, won't matter to later beta installers and other current beta testers 
should know about all this. Reason being, with the installation in two 
places someone could mess it up. Thinking of that, I guess I need to remove 
the Program Files\POV-Ray for Windows v3.7 since it isn't being used... 
right...?

Regardless, I suggest everyone watch the file path when opening and saving 
files.  ; ) I've mistaken the file locations I thought I was using many, 
many times.

Bob

Post a reply to this message