 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
[followups set to povray.beta-test]
Folks -
Windows beta 29 is available via http://www.povray.org/beta/.
[followups set to povray.beta-test]
-------------------------------------------
Changes between 3.7.beta.28 and 3.7.beta.29
-------------------------------------------
Allow POVWIN 'save as' to succeed without 'file is already open in editor'
error if case of current file is being changed.
Improved detection of true number of logical and physical cores on Intel CPU's.
Added colored text output to POVWIN message window. warning and debug messages
get different colors than error messages and standard text.
Added ability to declare an identifier as deprecated.
Many updates to scene and include files (see revision.txt for more details).
Worked around issue where new (for 3.7) crackle hash function returns large
range of possible values, causing memory used by cache to grow quickly. Work-
around is to revert to old hash function (this may also make crackle faster
since now we will get more cache hits).
Moved assumed location of POVWIN user-editable files into a subdir of 'My
Documents'.
Fixed two crashes reported in thread
<web.48b1839e38b6f50ec03ef3130@news.povray.org>.
Fixed sphere_sweep parse crash reported in
<web.48bc447cc2ccad1e8510f03f0@news.povray.org>.
Changed POVWIN UCS2 handling so that ASCII codes > 127 but < 256 are able to
be used. This should solve the issue reported in <48c04138$1@news.povray.org>.
Changed media confidence test to accept 0.0 as per docs.
Fixed crash in JPEG code.
Included Solaris patch by John Martin as reported in
<web.47e9bdccd4b82d06c7064b8c0%40news.povray.org>.
Deprecation Support
-------------------
The ability to add a 'deprecated' flag to a #declare has been added. This is
to aid in migrating scenes away from old constructs (e.g. old textures). The
usage is illustrated below:
#declare deprecated Col_Glass_Old=color rgbf <0.8, 0.9, 0.85, 0.85>;
#declare deprecated once Col_Glass_Old=... etc
#declare deprecated "Some message" Col_Glass_Old=... etc
A deprecated identifier generates no message at the time it is declared: a
warning is only issued if it is used.
If the optional 'once' keyword is present it must immediately follow the
'deprecated' keyword and indicates that the warning should only be
displayed once per parse.
If the optional message string is present, it will be used as the warning
to be displayed if the identifier is used. Otherwise, a message of the form
"Identifier 'Col_Glass_Old' was declared deprecated." is used.
An identifier is considered 'used' if it is referenced anywhere (even if in
another #declare).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bob Hughes" <omniverse charter net> wrote:
> 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.
Output_File_Name=c:\renderings should output the image to c:\renderings.png
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Nicolas Alvarez" <nic### [at] gmail com> wrote in message
news:48e6e9ab@news.povray.org...
> "Bob Hughes" <omniverse charter net> wrote:
>> 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.
>
> Output_File_Name=c:\renderings should output the image to
> c:\renderings.png
I'd expect so unless a folder exists with that path name. Don't ask me why,
I just do.
Curiously, it seemed to not matter before, I'd get the image into the proper
folder anyhow. With beta 28 uninstalled I can't recheck that but I have
rendered many scene files with only the povray.ini telling where to put
them, backslash or not... until this beta complained.
Simple syntax things like this gets easily forgotten by me over time. I
wouldn't know if or when the correct way to write file paths ever changed
since I get one way working and move on from there. ; )
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Folks,
The beta 29 release now includes a Windows 64-bit installer and executable.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 04 Oct 2008 00:20:54 +1000, Chris Cason
<del### [at] deletethistoopovrayorg> wrote:
>Moved assumed location of POVWIN user-editable files into a subdir of 'My
>Documents'.
the other betas and can't check what the last ones used) Is there any particular
reason for that? I think it is giving my modeller problems importing the search
paths. No big deal it just means that I have to keep 3.6 and 3.7 in step.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen wrote:
> the other betas and can't check what the last ones used) Is there any particular
> reason for that? I think it is giving my modeller problems importing the search
yes; as a file that is intended to be edited by individual users, it can't
be installed in a system-wide location. while technically I could install
it in the same location as the binaries, the binaries aren't always going
to be unique to a single user and may not be writeable by the user using
the program.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 05 Oct 2008 15:37:12 +1100, Chris Cason
<del### [at] deletethistoopovrayorg> wrote:
>Stephen wrote:
>> the other betas and can't check what the last ones used) Is there any particular
>> reason for that? I think it is giving my modeller problems importing the search
>
>yes; as a file that is intended to be edited by individual users, it can't
>be installed in a system-wide location. while technically I could install
>it in the same location as the binaries, the binaries aren't always going
>to be unique to a single user and may not be writeable by the user using
>the program.
>
>-- Chris
Thanks, that makes sense. (There is still hope for me :))
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I've uploaded the windows beta 29 source, plus an updated set of
instructions. Please see http://www.povray.org/beta/source/.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
