running povray with command :
povray +Ifracpos11a11.pov

Persistence of Vision(tm) Ray Tracer Version 3.5.0c-10 (Debian 
i386-linux-gcc)
 This is an unofficial version compiled by:
 Jeroen van Wolffelaar <jer### [at] wolffelaarnl> for Debian (www.debian.org)
 The POV-Ray Team(tm) is not responsible for supporting this version.
Copyright 1991-2002 POV-Ray Team(tm)
Parsing Options
 Input file: fracpos11a11.pov (compatible to version 3.5)
 Remove bounds........On  Split unions........Off
 Library paths: /usr/share/povray-3.5 /usr/share/povray-3.5/include
   /etc/povray-3.5/gini
Output Options
 Image resolution 320 by 240 (rows 1 to 240, columns 1 to 320).
 Output file: fracpos11a11.png, 24 bpp PNG
 Graphic display......On  (type: 0, palette: 3, gamma:  2.2)
 Mosaic preview......Off
 CPU usage histogram.Off
 Continued trace.....Off  Allow interruption..Off  Pause when done.....Off
 Verbose messages.....On
Tracing Options
 Quality:  9
 Bounding boxes.......On  Bounding threshold: 3
 Light Buffer.........On  Vista Buffer.........On  Draw Vista Buffer...Off
 Antialiasing........Off
Animation Options
 Clock value....   0.000  (Animation off)
Redirecting Options
 All Streams to console.........Off
 Debug Stream to console.........On
 Fatal Stream to console.........On
 Render Stream to console........On
 Statistics Stream to console....On
 Warning Stream to console.......On
Parsing...Possible Scene File Parser Initialization Error: Could not
find file 'fracpos11a11.pov'
 Scene File Parser Initialization Error: Cannot open input file.

Post a reply to this message

"Greg M. Johnson" <gregj;-)565### [at] aolcom> wrote in message
news:42ae4667$1@news.povray.org...
> running povray with command :
> povray +Ifracpos11a11.pov

:snip:

> Parsing...Possible Scene File Parser Initialization Error: Could not
> find file 'fracpos11a11.pov'
>  Scene File Parser Initialization Error: Cannot open input file.
>
>

running this command from inside QTPovEditor? Can you render any scene
loaded in QTPovEditor?

what happens when you run it from a command prompt in the directory where
the scene file exists?

Post a reply to this message

Can you confirm that that's the outpput of "your" program? Is it possible 
I've downloaded too many competing versions of povray and somehow QTPOV is 
invoking another?

It does not work with a file freshly created in QTPOV.
Typing "povray FILNAME.pov" however works.

Post a reply to this message

Okay, here's the fix (or the workaround required by the way i screwed up my 
system).

1) Pick a directory for your files
2) edit as root your  /etc/povray-3.5/povray.ini
3) Add library path

Now as long as you've saved your files to that directory, you're set to go.

Q:  are these properties of your actual system, or have I installed two 
things atop each other?


"Greg M. Johnson" <gregj;-)565### [at] aolcom> wrote in message 
news:42af8ec7$1@news.povray.org...
> Can you confirm that that's the outpput of "your" program? Is it possible 
> I've downloaded too many competing versions of povray and somehow QTPOV is 
> invoking another?
>
> It does not work with a file freshly created in QTPOV.
> Typing "povray FILNAME.pov" however works.
>
>

Post a reply to this message

Hi,

It seems that povray(megapov) installer does not always add the correct 
path to you libraries. You mays also have problems if you have enabled 
IO restrictions (I still don't understand the meaning of such a feature 
on systems with secured filesystems).


If you have an other soucy with QTPE, don't forget to ask on the 
official forum (does not require to be registered) ; 
http://qtpoveditor.sf.net

Thierry





> Okay, here's the fix (or the workaround required by the way i screwed up my 
> system).
> 
> 1) Pick a directory for your files
> 2) edit as root your  /etc/povray-3.5/povray.ini
> 3) Add library path
> 
> Now as long as you've saved your files to that directory, you're set to go.
> 
> Q:  are these properties of your actual system, or have I installed two 
> things atop each other?
> 
> 
> "Greg M. Johnson" <gregj;-)565### [at] aolcom> wrote in message 
> news:42af8ec7$1@news.povray.org...
> 
>>Can you confirm that that's the outpput of "your" program? Is it possible 
>>I've downloaded too many competing versions of povray and somehow QTPOV is 
>>invoking another?
>>
>>It does not work with a file freshly created in QTPOV.
>>Typing "povray FILNAME.pov" however works.
>>
>>
> 
> 
>

Post a reply to this message

> It seems that povray(megapov) installer does not always add the correct 
> path to you libraries.

	This might indeed be the case with 3.50c, although I didn't check it.
In principle installing 3.6 (povlinux or source distro) handles library
paths correctly.  Now Debian won't probably integrate 3.6 in their package
tree before 2 or 3 years  ;-)

> You mays also have problems if you have enabled 
> IO restrictions

	True again with 3.5, which I/O restriction feature was awkward.

> (I still don't understand the meaning of such a feature 
> on systems with secured filesystems).

	The filesystem "security" usually lets you write anything in your
user space.  Meaning it won't protect you from screwing up any user file
unless you manually change its write permission through 'chmod'.  Such
attack is possible via povray SDL when I/O restrictions are not set.
I/O restrictions just try to add another security level on top of the
filesystem permissions.

	- NC

Post a reply to this message

>> (I still don't understand the meaning of such a feature on systems 
>> with secured filesystems).
> 
> 
>     The filesystem "security" usually lets you write anything in your
> user space.  Meaning it won't protect you from screwing up any user file
> unless you manually change its write permission through 'chmod'.  Such
> attack is possible via povray SDL when I/O restrictions are not set.
> I/O restrictions just try to add another security level on top of the
> filesystem permissions.
> 
>     - NC

Ok, thanks for these explanations. Since I'm a single user I have no 
need in this sort of securities and that's what make my wrong fealing.

Thierry

Post a reply to this message

>>     The filesystem "security" usually lets you write anything in your
>> user space.  Meaning it won't protect you from screwing up any user file
>> unless you manually change its write permission through 'chmod'.
>
> Ok, thanks for these explanations. Since I'm a single user

	Well in fact my explanation attempt was a bit unclear and apparently
somewhat confusing, as guessed from your "Since I'm a single user" statement.
Please read again:

http://www.povray.org/documentation/view/3.6.1/794/

which better explains what I meant by "it won't protect you from screwing up
any [...] file" in your user space -- note the correction I make here  :-)

	- NC

Post a reply to this message

I did well understand what you meant, but what I mean is that my usage 
of povray won't harm my computer nor my personnal files because I don't 
use external files (excepted the ones from Gille Tran and Chris Colefax 
wich are known to be sure).


>>>     The filesystem "security" usually lets you write anything in your
>>> user space.  Meaning it won't protect you from screwing up any user file
>>> unless you manually change its write permission through 'chmod'.
>>
>>
>> Ok, thanks for these explanations. Since I'm a single user
> 
> 
>     Well in fact my explanation attempt was a bit unclear and apparently
> somewhat confusing, as guessed from your "Since I'm a single user" 
> statement.
> Please read again:
> 
> http://www.povray.org/documentation/view/3.6.1/794/
> 
> which better explains what I meant by "it won't protect you from 
> screwing up
> any [...] file" in your user space -- note the correction I make here  :-)
> 
>     - NC

Post a reply to this message