"jr" <cre### [at] gmailcom> wrote:
> I'll play some more in the week, then post a list of .. issues.
turns out that, so far, there are only two things on that list. :-)
one is that 'povr' displays "povray: I/O restrictions are disabled". confused.
the 'povray.conf' file contains (edited):
[File I/O Security]
;none ; all read and write operations on files are allowed.
;read-only ; uses the "read+write" directories for writing (see below).
restricted ; uses _only_ "read" and "read+write" directories for file I/O.
; [Shellout Security] determines whether POV-Ray will be allowed to call
; scripts (e.g. Post_Frame_Command) as specified in the documentation.
; Specify one of the 2 following values:
; - "allowed" means that shellout will work as specified in the documentation.
; - "forbidden" means that shellout will be disabled.
have not yet tested whether it's just the displayed info.
the second problem is a "third party" scene which fails:
==== [Parsing...] ==========================================================
FILE FOUND - Including ../...../L_01_04.inc
File '/home/jr/POVr/share/povray-3.8/include/transforms.inc' line 92:
Cannot pass uninitialized identifier to non-optional LValue.
Fatal error in parser: Cannot parse input.
that scene works fine with 10064268.alpha.
have not, so far, found the time to re-read the various newsgroup posts wrt
'povr' specific features and changes[*], so will probably use it just as an
alternative to the 10064268.alpha.
[*] maybe you can put all those together, in some text file.
Post a reply to this message