tho### [at] trfde news:408bb5c5@news.povray.org

> Hmm, maybe what you are looking for is a command-line version of
> POV-Ray?  I think there are some optimised command-line versions of
> POV-Ray 3.5 that run on Windows available.  I suppose others here know
> the links and can help you out, if not Google should provide links to
> them as well. 

Thanks, but that was not what I ment, sorry if I was unclear (bad english).

I ment to turn off writting /render/rerun

I disabel writting to /render/rerun (just by renaming this dir ro _retun)
and it gave grate boost in speed of post-render.

The delay between finishing render and possiblitity to contue editing 
(beta-4.win32) is now about 0.1 second (ewen with all streams on, comes out 
that streams was NOT the problem).

-- 
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics

Post a reply to this message

In article <Xns94D6A7D59F57Draf256com@203.29.75.35>, spa### [at] raf256com 
says...
> tho### [at] trfde news:408bb52b$1@news.povray.org
> 
> > You can already disable individual streams.  Please refer to the user
> > manual for details.
> 
> I know.
> I suggest to add predefined .ini and bind it to a key and to button.
> 
> alt+1 or button GO(fast) = turned off most streams -f +sp32 +ep4
> alt+2 or button GO
> alt+3 or button GO(final) = +a0.03 +f
> 
> and maybe also
> 
> alt+4 .. alt+9 - will fastly select quickres.ini section [fast_4] .. 
> [fast_9] and render it.
> 
> I know it is possible, but new-users might not.
> 
Wouldn't something like the 'drop-down on a button' things like some 
browsers have make more sense. Just click the button for normal behaviour 
or the little drop down arrow to get alternative behaviors. That way the 
option is there, but you don't need 2-3 extra buttons. And I tend to 
agree here. New users won't know how to set these things manually, and in 
the case of the re-run issue, you can't apparently even turn that off 
anyway, even though Rafal says it can drastically speed things up for 
those of us that *never* or rarely use it in the first place. Renaming 
the directory so that it simply fails in all cases isn't much of an 
option, since when you do need it, you have to rename the directory again 
to reenable it. :(

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message