 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I may be mistaken but has the max_gradient warning disappeared from 3.7?
I ran code from :
news://news.povray.org:119/web.52e8d82bcfb9f6d0a7cafab50@news.povray.org
and got no warning that the max_gradient (at 200) was too high. I then
ran it at max_gradient 20 (too low) and still no warning.
Just for comparison, I also ran under 3.6 and got warnings both times.
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Doctor John <j.g### [at] gmail com> wrote:
> I may be mistaken but has the max_gradient warning disappeared from 3.7?
> I ran code from :
> news://news.povray.org:119/web.52e8d82bcfb9f6d0a7cafab50@news.povray.org
> and got no warning that the max_gradient (at 200) was too high. I then
> ran it at max_gradient 20 (too low) and still no warning.
> Just for comparison, I also ran under 3.6 and got warnings both times.
>
> John
> --
> Protect the Earth
> It was not given to you by your parents
> You hold it in trust for your children
We had this discussion some months ago, but I cannot find it actually. IIRC the
solution is to declare the isosurface and then enclose it in an object {}.
Best regards,
Michael
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 30/01/14 07:12, MichaelJF wrote:
>
> We had this discussion some months ago, but I cannot find it actually. IIRC the
> solution is to declare the isosurface and then enclose it in an object {}.
>
> Best regards,
> Michael
>
>
Indeed you did. I missed it then (mainly because I don't follow p.b-t)
but I found it on the web Here:
http://news.povray.org/povray.beta-test/thread/%3C51c55b9f%241%40news.povray.org%3E/?mtop=384497
Declaring the isosurface then enclosing it in a object {} don't seem to
work. Also -WT1 doesn't help.
I guess this is a bug that still needs to be eradicated. Meanwhile, I'll
just carry on developing my landscape isosurfaces with v3.6
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Doctor John <j.g### [at] gmailcom> wrote:
> On 30/01/14 07:12, MichaelJF wrote:
> >
> > We had this discussion some months ago, but I cannot find it actually. IIRC the
> > solution is to declare the isosurface and then enclose it in an object {}.
> >
> > Best regards,
> > Michael
> >
> >
>
> Indeed you did. I missed it then (mainly because I don't follow p.b-t)
> but I found it on the web Here:
>
http://news.povray.org/povray.beta-test/thread/%3C51c55b9f%241%40news.povray.org%3E/?mtop=384497
>
> Declaring the isosurface then enclosing it in a object {} don't seem to
> work. Also -WT1 doesn't help.
> I guess this is a bug that still needs to be eradicated. Meanwhile, I'll
> just carry on developing my landscape isosurfaces with v3.6
>
> John
> --
> Protect the Earth
> It was not given to you by your parents
> You hold it in trust for your children
Hi John,
I just found your message now as I do not follow the unix n.g.
The answer to your question is to "unwrap" your isosurface and use the
isosurface in its "naked" form to get the max_gradient messages.
example:
#if (Naked)
isosurface {....}
#else
#declare Test = isosurface {...}
object {Test}
#end
In its naked version, the messages appear.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
