![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
You could just stop POV-Ray from printing messages with -GA
If you are rendering a long animation, you usually don't need to see
the scene statistics for anything.
--
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Aha, yup. I'll try that. Would it switch debug messages
(that my particle-system outputs) off too?
(That was a rherotical question, I'll see for myself...
Its not too hard to test, if you know what I mean)
Warp wrote:
> You could just stop POV-Ray from printing messages with -GA
> If you are rendering a long animation, you usually don't need to see
> the scene statistics for anything.
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmx de
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Had a look at it. Thanks!
"Kevin R." wrote:
> Try Start -> Programs -> Accessories -> System Tools -> System Monitor, and
> add the charts you want. It's a pretty powerful tool.
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmx de
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Another idea I had...
If this message window stream in Windows is the cause
of some errors (memory problems, to be precise),
how about putting a note in this in the
docs? It would be best to make this behaviour very
obvious, unless someone wants to hear someone really
upset talking about how he tried to raytrace a 5000
(for 200 secs) animation and ran into some problems...
Thorsten Froehlich wrote:
> Those have been explained a very long time ago in p-beta-test: Some people
> observed memory use increasing by a few KB with each render using the system
> monitor, which is exactly the size needed to store the statistics and other
> message output. So there is no problem and never was.
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmx de
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |