> No, but at least a valid and clear file names.  How to specify INi files
> and scenes files on the command line is outlined in the user manual in
> great detail.
> 
> You just specify two names without extension and the POV-Ray should apply
> mind reading to figure out which file to use as what.  That won't work :-)
> 

But it does, check this out:

[rob@musicbox Rendering]$ povray ini/res[normal] quality.ini[normal]
ship/ship.ini

The above line picks up that res is an ini file (the paht ini/ is just a
link from the current dir saving inputing the complete path) despite the
lack of  extention, but will not pick up the quality.ini is an ini file
and wont look for it in the library paths.  Here is the output.

Persistence of Vision(tm) Ray Tracer Version 3.5 Unix (.Linux.gcc)
  This is an unofficial version compiled by:
   R. Brown-Bayliss
   The POV-Ray Team(tm) is not responsible for supporting this version.
Copyright 1991-2002 POV-Ray Team(tm)
Possible Command Line Error: Could not open INI file 'quality.ini'.
 Parsing Options
  Input file: /usr/local/Rendering/ship/scene.pov (compatible to version 3.5)
  Remove bounds........On  Split unions........Off
  Library paths: /usr/local/share/povray-3.5
    /usr/local/share/povray-3.5/include /usr/local/share/povray-3.5/ini
    /usr/local/Rendering/includes /usr/local/Rendering/ship
Output Options

So it doesn't care about the extention, but it demands a full path which I
have cludged with a link from the current directory to /usr/local/share/povray-3.5/ini

Is this right?  Shouldn't it just look in the library path for any .ini
file, and why does it not need the .ini for a full path?

Post a reply to this message