 |
|
|
|
|
|
| |
| |
|
|
From: Robert Chaffe
Subject: Where is max_gradient in Message window?
Date: 16 Feb 2002 11:34:44
Message: <3c6e8a24@news.povray.org>
|
|
|
| |
| |
|
|
Trying to learn how to use isosurfaces, I am playing with provided samples.
Specifically I am interested in seeing max_gradient estimation in action.
So I went to the isosurface in the crackle3.pov sample file, uncommented the
evaluate keyword and changed its parameters to 1, 10, 0.99 as suggested in
the manual. Also changed max_gradient to 5 as suggested. Then rendered it.
I am looking and looking in the Message window after rendering and I do not
see a warning about the max_gradient POV-Ray should have found for me to
copy and paste.
Is it called something else? Or am I doing something wrong? Or is this a
bug?
- rc
Version 3.5.beta.11.icl.win32, Windows ME, Intel Pentium 4, 1.7 GHz, 128MB
RDRam.
ps, Here is my Message window:
----------------------------------------------------------------------------
Preset INI file is 'C:\GRAPHICS\POV-RAY FOR WINDOWS
V3.5\renderer\quickres.ini', section is '[160x120, No AA]'.
Preset source file is 'C:\Graphics\POV-Ray for Windows
v3.5\scenes\textures\patterns\crackle3.pov'.
Persistence of Vision(tm) Ray Tracer Version 3.5.beta.11 win32 (.icl)
This is a time-limited beta test version. No re-distribution
of any sort is permitted.
Copyright 1991-2002 POV-Ray Team(tm)
This Windows version by Christopher J. Cason
Parsing Options
Input file: C:\Graphics\POV-Ray for Windows
v3.5\scenes\textures\patterns\crackle3.pov (compatible to version 3.5)
Remove bounds........On Split unions........Off
Library paths: C:\Graphics\POV-Ray for Windows v3.5\INCLUDE
C:\WINDOWS\Fonts
Output Options
Image resolution 160 by 120 (rows 1 to 120, columns 1 to 160).
Output file: crackle3.bmp, 24 bpp (system format)
Graphic display......On (type: 0, palette: 3, gamma: 2.2)
Mosaic preview......Off
CPU usage histogram.Off
Continued trace.....Off Allow interruption..Off Pause when done.....Off
Verbose messages.....On
Tracing Options
Quality: 9
Bounding boxes.......On Bounding threshold: 3
Light Buffer.........On Vista Buffer.........On Draw Vista Buffer...Off
Antialiasing........Off
Animation Options
Clock value.... 0.000 (Animation off)
Redirecting Options
All Streams to console.........Off
Debug Stream to console.........On
Fatal Stream to console.........On
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console.......On
Scene contains 72 frame level objects; 2 infinite.
Statistics for C:\Graphics\POV-Ray for Windows
v3.5\scenes\textures\patterns\crackle3.pov, Resolution 160 x 120
----------------------------------------------------------------------------
Pixels: 19200 Samples: 19200 Smpls/Pxl: 1.00
Rays: 30588 Saved: 0 Max Level: 2/5
----------------------------------------------------------------------------
Ray->Shape Intersection Tests Succeeded Percentage
----------------------------------------------------------------------------
Isosurface 6350 2208 34.77
Isosurface Container 8793 6351 72.23
Isosurface Cache 2036 60 2.95
Plane 51565 19200 37.23
Sphere 30588 30588 100.00
Superellipsoid 22279 7664 34.40
True Type Font 7459 403 5.40
Bounding Box 318496 33072 10.38
Light Buffer 553921 339327 61.26
Vista Buffer 181301 125630 69.29
----------------------------------------------------------------------------
Calls to Noise: 0 Calls to DNoise: 68338
----------------------------------------------------------------------------
Shadow Ray Tests: 37049 Succeeded: 460
Reflected Rays: 11388
----------------------------------------------------------------------------
Smallest Alloc: 25 bytes Largest: 12056
Peak memory used: 256982 bytes
----------------------------------------------------------------------------
Time For Parse: 0 hours 0 minutes 1.0 seconds (1 seconds)
Time For Trace: 0 hours 1 minutes 14.0 seconds (74 seconds)
Total Time: 0 hours 1 minutes 15.0 seconds (75 seconds)
POV-Ray finished
----------------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
AFAIK evaluate is more or less obsolete as povray warns you about a wrong
max_gradient regardless of whether you have specified evaluate or not.
If povray doesn't tell anything about max_gradient, it probably means
that the max_gradient you have specified is correct enough.
--
#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
|
|
| |
| |
|
|
From: Christoph Hormann
Subject: Re: Where is max_gradient in Message window?
Date: 16 Feb 2002 12:41:00
Message: <3C6E99AB.5CA3E6C6@gmx.de>
|
|
|
| |
| |
|
|
Warp wrote:
>
> AFAIK evaluate is more or less obsolete as povray warns you about a wrong
> max_gradient regardless of whether you have specified evaluate or not.
> If povray doesn't tell anything about max_gradient, it probably means
> that the max_gradient you have specified is correct enough.
>
That's about it, 'evaluate' is now only used for the dynamic max_gradient
method, the warnings are generated when you use max_gradient and the found
value differs too much from the specified one.
The docs are going to be updated as soon as the changes concerning this
are finished.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 06 Feb. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: Where is max_gradient in Message window?
Date: 16 Feb 2002 13:12:38
Message: <3c6ea116@news.povray.org>
|
|
|
| |
| |
|
|
In article <3c6e9304@news.povray.org> , Warp <war### [at] tag povrayorg> wrote:
> AFAIK evaluate is more or less obsolete as povray warns you about a wrong
> max_gradient regardless of whether you have specified evaluate or not.
> If povray doesn't tell anything about max_gradient, it probably means
> that the max_gradient you have specified is correct enough.
This is not completely correct. The current warning will only be shown if
evaluate is off. The warnings are off when evaluate is used since beta 10
until some of the problems with it with evaluate on have been corrected. The
documentation has not been updated yet regarding any of these changes - it
still makes it look like evaluate is mandatory or necessary. This is not the
case for almost all scenes now. Using max_gradient, and _only_ max_gradient
is sufficient.
For a beginner, I strongly recommend to ignore evaluate now. Just _not_
adding it to any scene is sufficient.
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
|
|
| |
| |
|
|
|
|
| |
|
|
