I need to run a large number of POV files but each needs its own settings
(using MegaPOV4/Win, in fact). Can I specify the clock start and end, number
of frames, AA (or not), h and w,  etc. directly in the POV script using
global settings, or do I need to create a separate .ini file for each? And
if separate ini/s are needed, how do I call them from the script? I tried
including (#include "2povray.ini") in my script, but I got an error saying
the semi-colon on the first line was illegal, so POV didn;t know it was an
ini file, I assume.
Any help would be appreciated!
Thanks much,
D.


--
dhm### [at] mediaonenet
http://www.casdn.neu.edu/~dmiller

Post a reply to this message

In article <39791196@news.povray.org> , "D. H. Miller" 
<dhm### [at] mediaonenet> wrote:

> I need to run a large number of POV files but each needs its own settings
> (using MegaPOV4/Win, in fact). Can I specify the clock start and end, number
> of frames, AA (or not), h and w,  etc. directly in the POV script using
> global settings, or do I need to create a separate .ini file for each? And
> if separate ini/s are needed, how do I call them from the script? I tried
> including (#include "2povray.ini") in my script, but I got an error saying
> the semi-colon on the first line was illegal, so POV didn;t know it was an
> ini file, I assume.
> Any help would be appreciated!

Using INI files is explained in detail in the manual.  In POV-Ray for
Windows the manual is available in the Help menu.


      Thorsten

Post a reply to this message

I have checked the manual and cannot see where to call the ini file from
within the POVray script. Could you possibly show me what that would look
like? I mentioned in my previous message that #include "2povray.ini" does
not seem to work.
D.


--
dhm### [at] mediaonenet
http://www.casdn.neu.edu/~dmiller
Thorsten Froehlich <tho### [at] trfde> wrote in message
news:39795928@news.povray.org...
> In article <39791196@news.povray.org> , "D. H. Miller"
> <dhm### [at] mediaonenet> wrote:
>
> > I need to run a large number of POV files but each needs its own
settings
> > (using MegaPOV4/Win, in fact). Can I specify the clock start and end,
number
> > of frames, AA (or not), h and w,  etc. directly in the POV script using
> > global settings, or do I need to create a separate .ini file for each?
And
> > if separate ini/s are needed, how do I call them from the script? I
tried
> > including (#include "2povray.ini") in my script, but I got an error
saying
> > the semi-colon on the first line was illegal, so POV didn;t know it was
an
> > ini file, I assume.
> > Any help would be appreciated!
>
> Using INI files is explained in detail in the manual.  In POV-Ray for
> Windows the manual is available in the Help menu.
>
>
>       Thorsten

Post a reply to this message

"D. H. Miller" wrote:
> 
> I have checked the manual and cannot see where to call the ini file from
> within the POVray script. Could you possibly show me what that would look
> like? I mentioned in my previous message that #include "2povray.ini" does
> not seem to work.

You cannot "call" .ini files from within your pov file. If named
properly and placed within the same directory as the .pov file it
is read automatically. The .ini file must use the same name as
the .pov file you are using. If you need to change variables within
the .ini file between frames you will need to figure out a way
to #write them into the .ini file before the next frame is parsed.
I don't know if this is possible but I don't know why it wouldn't
be. 

-- 
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

On Sat, 22 Jul 2000 08:11:50 -0700, Ken wrote:
>You cannot "call" .ini files from within your pov file. If named
>properly and placed within the same directory as the .pov file it
>is read automatically. The .ini file must use the same name as
>the .pov file you are using. 

You can also specify which INI file to use on the command line.

-- 
Ron Parker   http://www2.fwi.com/~parkerr/traces.html
My opinions.  Mine.  Not anyone else's.

Post a reply to this message