This has come up in a couple of threads already - it is a new feature in pov 
3.5 with rather confusing defaults.  Basically, (as I understand it), Pov 
3.5 prevents you from accessing any files outside the directory where you 
perform the render from (or something like that), unless you explicitely 
allow otherwise in your povray.conf.  Here's what I put in my 
/usr/local/etc/povray.conf:

----
[File I/O Security]
none

[Shellout Security]
allowed
----

And in my ~/.povrayrc:

----
Library_Path=/usr/local/share/povray-3.5/include
----

Not quite sure why it worked for you with the official version and not with 
mine (maybe they've changed the defaults in the official binary?).

Ken

John Coppens wrote:

> Ken Cecka wrote:
>> Coming in on the heels of everyone else's compiling woes and optimized
>> builds, I just got around to doing my own, and thought I'd post my
>> results. I don't have the official linux build or the windows build
>> installed to do comparisons with, but I did a default build and an
>> optimized build, and have results for each on my system:
>> 
> 
> 
> Hi Ken.
> 
> I ran the Athlon version on my machine and got the following error:
> 
> Parsing...Scene File Parser Initialization Error: I/O restriction
> prohibits read access to file 'benchmark.pov'. Refer to the platform
> specific documentation for details.
> 
> The only thing I changed was the executable. The original 3.5 version
> gave:
> 
> Time For Parse:    0 hours  0 minutes   6.0 seconds (6 seconds)
> Time For Photon:   0 hours  2 minutes  46.0 seconds (166 seconds)
> Time For Trace:    1 hours  7 minutes  18.0 seconds (4038 seconds)
>     Total Time:    1 hours 10 minutes  10.0 seconds (4210 seconds)
> 
> quite similar to your run.
> 
> Ideas?
> 
> John

Post a reply to this message