Hi

If I'm in the middle of a long trace. The output file is specified in the
command line (+fp16 +otest.raw) and now I'd like to queue the next trace as
an INI containing new trace options like image height, width and I/O options
input name and output name. Do the INI file settings override the command
line? It won't be nice to find out that the previous got written over..

Ari-Matti

Post a reply to this message

"Ari-Matti Leppanen" <ari### [at] tutfi> wrote in message
news:3c206279$1@news.povray.org...
>
> If I'm in the middle of a long trace. The output file is specified in the
> command line (+fp16 +otest.raw) and now I'd like to queue the next trace
as
> an INI containing new trace options like image height, width and I/O
options
> input name and output name. Do the INI file settings override the command
> line? It won't be nice to find out that the previous got written over..


Command line always takes precedence over INI.  If you are using the beta of
v3.5 you can add the new command line in during the current render and it
will (should) be used upon rendering the next scene file added to your Queue
(don't need to specify that on command line, just use Render|Queue or Alt Q.
Checking to be sure here (done it before but have to be sure) it is flawless
for beta 8 anyway.  If you aren't using v3.5 then I don't have an idea,
unless maybe the pvengine.ini can be edited to remove the command reference.

Sorry to tell you this but it does not, just tried editing pvengine.ini and
testing it out that way.  It only holds that info from when POV-Ray last
runs and won't change anything even when quit and started again.  Changes
once the command line has been invoked through a render.
--
text{ttf"timrom""bob h"0,0pigment{rgb 7}translate 7*z}

Post a reply to this message

Terribly sorry, good thing I reread my reply to you.  I left out how you
need to go about it.  The v3.5 beta script would need a

 //cmd: +w320 +h240 +oFilename   (plus whatever else)

added to that first then right-clicking onto it you Copy to command line.
You can't get into it any other way AFAIK.
Hope that finishes my answer.
--
text{ttf"timrom""bob h"0,0pigment{rgb 7}translate 7*z}

"bob h" <omn### [at] charternet> wrote in message
news:3c20749b@news.povray.org...
> "Ari-Matti Leppanen" <ari### [at] tutfi> wrote in message
> news:3c206279$1@news.povray.org...
> >
> > If I'm in the middle of a long trace. The output file is specified in
the
> > command line (+fp16 +otest.raw) and now I'd like to queue the next trace
> as
> > an INI containing new trace options like image height, width and I/O
> options
> > input name and output name. Do the INI file settings override the
command
> > line? It won't be nice to find out that the previous got written over..
>
>
> Command line always takes precedence over INI.  If you are using the beta
of
> v3.5 you can add the new command line in during the current render and it
> will (should) be used upon rendering the next scene file added to your
Queue
> (don't need to specify that on command line, just use Render|Queue or Alt
Q.
> Checking to be sure here (done it before but have to be sure) it is
flawless
> for beta 8 anyway.  If you aren't using v3.5 then I don't have an idea,
> unless maybe the pvengine.ini can be edited to remove the command
reference.
>
> Sorry to tell you this but it does not, just tried editing pvengine.ini
and
> testing it out that way.  It only holds that info from when POV-Ray last
> runs and won't change anything even when quit and started again.  Changes
> once the command line has been invoked through a render.

Post a reply to this message

"bob h" <omn### [at] charternet> wrote in message
news:3c207e6a@news.povray.org...

> added to that first then right-clicking onto it you Copy to command
> line.

Ah, forgot the right-clicking. Thanks!

Ari-Matti

Post a reply to this message