POV-Ray : Newsgroups : povray.beta-test : too much flushing / slow pre/post parse Server Time
29 Jul 2024 08:11:31 EDT (-0400)
  too much flushing / slow pre/post parse (Message 3 to 12 of 12)  
<<< Previous 2 Messages Goto Initial 10 Messages
From: Thorsten Froehlich
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 05:26:38
Message: <408b844e@news.povray.org>
In article <Xns94D633C1AFF81raf256com@203.29.75.35>, "Rafal 'Raf256' Maj" 
<spa### [at] raf256com> wrote:

> From Pov 3.5 (or even 3.1) there still is a delay after and of render.

Well, if the behavior is the same in previous versions, your post is a
feature request...

> It is caused by
> - closing/flushing output file, -f elimitase it

Of course, if you don't output the image to file, the image file does not
have to be written and rendering will be faster.  Obviously, this cannot be
avoided if you want an image written to disk.

> - flushing all streams, -Ga eliminates it partialy

Information output takes time.

> - rendeing of message window slooowly scrolling (in Win32 version), hidding
> messages window helps it.

Maybe you should get a faster graphics card if scrolling is too slow? - On
the other hand, I have yet to see scrolling being slow, so probably your
system is having other problems.  Maybe your graphics card driver is missing
and Windos defaulted to the universal VGA driver?

> Once I turned off everything (all outputs/streams etc) and then one render
> took 0.05 second (it was ofcourse siiiimple image in 50x50 resolution), so
> could accualy watch a little povray animtion in real time :)
>
> It would be nice to make this behaviour default.

You can easily edit povray.ini if you want such a default.

> I.e make two render buttons - one designed for preview (no streams or
> messages, is there is no errors), and one for normal render (all streams,
> output file).

So POV-Ray is to magically predict there will be no errors or warnings and
disable all output prior to even having parsed the scene?  Sure.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Rafal 'Raf256' Maj
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 07:29:18
Message: <Xns94D689184D2Draf256com@203.29.75.35>
tho### [at] trfde news:408b844e@news.povray.org

>> - rendeing of message window slooowly scrolling (in Win32 version),
>> hidding messages window helps it.
> Maybe you should get a faster graphics card if scrolling is too slow?
> - On the other hand, I have yet to see scrolling being slow, so
> probably your system is having other problems.  Maybe your graphics
> card driver is missing and Windos defaulted to the universal VGA
> driver? 

GeForce 4 Fx :) This is *very* fast card. Ofcourse with newest drivers etc.
 
>> It would be nice to make this behaviour default.
> You can easily edit povray.ini if you want such a default.

But newbies to PovRay cant. Same thing as with Sound settings (greate job 
btw).

>> I.e make two render buttons - one designed for preview (no streams or
>> messages, is there is no errors), and one for normal render (all
>> streams, output file).
> So POV-Ray is to magically predict there will be no errors or warnings
> and disable all output prior to even having parsed the scene?  Sure.

*TWO* render buttons.
Or even better three,
[Run preview]
[Run Normal]
[Run Finla]]


And in .ini files You could define i.e.

[run_preview]
-a -g -Ga

[run_normal]

[run_final]
+a0.03 +ar2 +am2


Ofcourse this is obvious for You, me, and other povray users.
But software designer realy should think as a normal-peopes, that dont have 
a clue what .ini file is, and want to faslty have choose quality/speed, 
without reading tons of help. No all pov-users are programmers You know :)


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


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 07:50:14
Message: <408ba5f6@news.povray.org>
In article <Xns94D689184D2Draf256com@203.29.75.35>, "Rafal 'Raf256' Maj" 
<spa### [at] raf256com> wrote:

> And in .ini files You could define i.e.
>
> [run_preview]
> -a -g -Ga
>
> [run_normal]
>
> [run_final]
> +a0.03 +ar2 +am2
>
>
> Ofcourse this is obvious for You, me, and other povray users.
> But software designer realy should think as a normal-peopes, that dont have
> a clue what .ini file is, and want to faslty have choose quality/speed,
> without reading tons of help. No all pov-users are programmers You know :)

Did you actually think about the consequences of your suggestion?
Essentially when previewing a scene during development of said scene you
could not see any errors.  Nor could new users see it.  POV-Ray would just
stop!

It should be absolutely obvious that neither new users nor any user for that
matter should be offered a user interface that shows no information in the
event of errors or warnings.  If an advanced users really elects to not care
about any errors and warnings it might be acceptable.  However, for a
default configuration to just not show any problems at all is about as wrong
as user interface design can possibly be!

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Rafal 'Raf256' Maj
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 08:05:55
Message: <Xns94D68F4D4E276raf256com@203.29.75.35>
tho### [at] trfde news:408ba5f6@news.povray.org

> It should be absolutely obvious that neither new users nor any user
> for that matter should be offered a user interface that shows no
> information in the event of errors or warnings.  If an advanced users
> really elects to not care about any errors and warnings it might be
> acceptable.  However, for a default configuration to just not show any
> problems at all is about as wrong as user interface design can
> possibly be! 

Well right. Maybe just remove statistics stream and fie output then (from 
preview mode)?

But generaly idea of easy accesible 3 rendre modes (3 buttons, maybe 3 
short cuts) is not so bad idea? it is uded in every other rendering 
software i.e. moray (wireframe / raytrace / etc)

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


Post a reply to this message

From: Rafal 'Raf256' Maj
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 08:09:07
Message: <Xns94D68FD82F2CAraf256com@203.29.75.35>
spa### [at] raf256com news:Xns94D68F4D4E276raf256com@203.29.75.35

> Well right. Maybe just remove statistics stream and fie output then
> (from preview mode)?

And disable saving INI to RERUN/ because rotating rerun hisotre needs to 
open/read/write/close over 10 files. Some ini option for not writing rerun, 
and add this also to preview.

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


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 08:55:07
Message: <408bb52b$1@news.povray.org>
In article <Xns94D68F4D4E276raf256com@203.29.75.35>, "Rafal 'Raf256' Maj" 
<spa### [at] raf256com> wrote:

> Well right. Maybe just remove statistics stream and fie output then (from
> preview mode)?

You can already disable individual streams.  Please refer to the user manual
for details.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 08:57:41
Message: <408bb5c5@news.povray.org>
In article <Xns94D68FD82F2CAraf256com@203.29.75.35>, "Rafal 'Raf256' Maj" 
<spa### [at] raf256com> wrote:

>> Well right. Maybe just remove statistics stream and fie output then
>> (from preview mode)?
>
> And disable saving INI to RERUN/ because rotating rerun hisotre needs to
> open/read/write/close over 10 files. Some ini option for not writing rerun,
> and add this also to preview.

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.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Rafal 'Raf256' Maj
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 10:30:38
Message: <Xns94D6A7D59F57Draf256com@203.29.75.35>
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.


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


Post a reply to this message

From: Rafal 'Raf256' Maj
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 10:35:33
Message: <Xns94D6A8AAE9C8Craf256com@203.29.75.35>
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

From: Patrick Elliott
Subject: Re: too much flushing / slow pre/post parse
Date: 25 Apr 2004 15:14:08
Message: <MPG.1af5bb00bd178f47989a27@news.povray.org>
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

<<< Previous 2 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.