"jr" <cre### [at] gmailcom> wrote:
> how about, for every scene file, you add a corresponding .ini file ?  there, not
> only can you provide explicit paths (via 'library_path'), but also "fix" other
> stuff you'd usually provide on the command-line, like antialias etc.  "added
> bonus" is being able to simply write:
>   $ povray myscene.ini
> and done ;-).


Is that easier than defining a path?
I don't think so.
It would just shift the problem to an (additional) ini file.


Alain Martel <kua### [at] videotronca> wrote:
> When POV-Ray looks for include files, it start in the same folder as the
> current scene file, then, it search in the include folder.
> When searching for an include from inside another include file, it
> search in the folder where the first include is located.

The last sentence is my problem. What I would need would be something like a
Povray variable that says where the currently included script is. Then I could
use it to load more scripts of this "sub-include".


But maybe I'm not describing my problem well enough.
I'll do it with manual path information first, maybe then I'll get a hint on how
to do it more elegantly.

Thank you for the tips.

ma

Post a reply to this message