Let's make a couple of things clear:

  Povray always outputs to the directory where povray was run from (usually
you run it from the same directory as your .pov file is, so the image will
be created in that same directory). Unless, of course, specified otherwise
in some .ini file (although I don't see any reason for doing this).

  By default povray outputs to a file with the same name as the .pov file
only changing the extension to reflect the image format used.

  One reason for povray to fail creating the output file is that the user
doesn't have write permission in the current directory (pwd). It can also
be that the output file exists and the user doesn't have write permission
for that file (although this is a very rare case usually).
  There might, however, be other reasons as well.

  If you render something with povray, just make sure that you are in the
directory where the .pov file is, it's a directory owned by you (so that
you have write permissions) and that's it.
  A povray config file with some default settings wouldn't hurt either
(you can create it in your home directory with the name .povrayrc and
it's just an ini-file, ie. it's syntax is the same as in an ini file).
You'll probably want to put some +L commands in there, as well as specifying
your preferred image format and also things like: +v +d +p +x10 +b50


  Btw: Why everyone always suggest a HUGE command line for unix povray?
Short is beautiful.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message