![](/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) |
3c0942f8@news.povray.org...
> It does this only if the gradient found was really zero, which can i.e. be
> the case if there was no intersection. I will adjust the warning message
to
> ignore such cases, yet.
But the fact that the warning message happens even when a max_gradient is
given by the user is still a bug, isn't it ? Or am I confused about the
purpose of the warning ? Like JRG I was a bit surprised to see my current
scene output hundreds of (useless in this case) iso warnings...
> That Gilles can't turn off the warning with -GW is also not correct,
> however, there is a much better workaround than - GA in section 5.2.5.4 of
> the documentation, which explains the warning level option. Hopefully
> Gilles has found it by now...
Well, thanks a lot, warning level 0 works.
I'm still wondering at the difference between -GW (turn console display of
warning text off), and WL0 (turns off all warnings), though... -GW should
work, at least, since it's working for #warning, or am I (again) totally
confused by what the text streams mean ? It's true that I never spent much
time investigating this part of Povray as it seemed quite straightforward.
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
> Thorsten
>
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: tho### [at] trf de
>
> Visit POV-Ray on the web: http://mac.povray.org
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) |
In article <3c094c4c$1@news.povray.org> , "Gilles Tran" <tra### [at] inapg inra fr>
wrote:
> But the fact that the warning message happens even when a max_gradient is
> given by the user is still a bug, isn't it ? Or am I confused about the
> purpose of the warning ?
As explained in my response to JRG only the output of 0.0 is a bug. For
details about the message and relating changes, see the thread 'beta 8' in
p.pre-beta.
> I'm still wondering at the difference between -GW (turn console display of
> warning text off), and WL0 (turns off all warnings), though... -GW should
> work, at least, since it's working for #warning, or am I (again) totally
> confused by what the text streams mean ? It's true that I never spent much
> time investigating this part of Povray as it seemed quite straightforward.
No, as I noted in my previous response to JRG, there is a problem. In short
lets just say POV-Ray does not expect any text stream outputs after
rendering is complete and it would reset the user settings prior to
releasing memory of the scene. However, that is exactly the time when
isosurfaces check the maximum gradient and output it if necessary...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
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) |
Wasn't it Jide who wrote:
>Athlon, 512 Mb ram, Win ME, beta 8(both compiles)
>
>IsoCacti.pov in advanced dir gives dozens of max_gradient found
>was 0.000 warnings for line 73.
>Is this a bug or a case of "bad" functions?
I had a quick check to see if this had been fixed in beta 10.
The reported problem has been fixed, but the output doesn't look
anything like cacti any more. It looks like there's something wrong with
the camera.
--
Mike Williams
Gentleman of Leisure
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) |
"Mike Williams" <mik### [at] nospam please> wrote in message
news:1$sqAKA8LkR8Ewk5@econym.demon.co.uk...
> The reported problem has been fixed, but the output doesn't look
> anything like cacti any more. It looks like there's something wrong
> with the camera.
It's the new camera.. just:
#version 3.1;
camera {...}
#version 3.5;
and it works fine.
Ari-Matti
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) |