Cousin Ricky <ric### [at] yahoocom> wrote:
> POV-Ray 3.8 cannot process .ini files in my library path; I have to
> provide the path to the .ini file in order to get a successful render.
> For example:
> This problem has existed since the POV-Ray 3.7.1 betas, and is present
> in the latest UberPOV. Previous versions of POV-Ray do not have this
> problem. (Earlier, I reported a failure to process certain .ini files
> from within their own directory; that problem no longer occurs.)
> There is no problem locating #include files from within a scene file.
The parsing of INI files works as designed and documented in 3.7. As you know,
the Library_Path option is documented in the "Scene Parsing Options" section. It
has effects only within the scene file.
The behavior in 3.6 and before was rather confusing and would pick up
configuration options in the order they were provided and execute them
instantly. This means it would also parse your INI file and the overwrite
whatever that file specified with whatever came after it in the original INI
file. Your usage only worked due to side effects of the INI parser already
storing the library include paths while it was parsing the options and the code
using the same function to locate files.
Post a reply to this message