POV-Ray : Newsgroups : povray.binaries.animations : Mysterious vanishing isosurface : Re: Mysterious vanishing isosurface Server Time
7 Jul 2022 03:35:01 EDT (-0400)
  Re: Mysterious vanishing isosurface  
From: Mike Horvath
Date: 11 Dec 2016 21:11:22
Message: <584e074a$1@news.povray.org>
On 12/11/2016 7:08 PM, clipka wrote:
> Am 12.12.2016 um 00:51 schrieb Mike Horvath:
>
>>> A suggesting is trying the isosurface coded in your scene at a rotations
>>> around where it is breaking up, at a low resolution, no aa+, area light,
>>> etc., as
>>>
>>> isosurface {
>>> }
>>>
>>> not used by reference (github #114 (#113 is related)), so you get some
>>> idea what the max gradient really is and how it is changing.
>>>
>>> Bill P.
>>
>> I don't understand. What are you saying?
>
> He's suggesting that rather than
>
>     #declare Whatever = isosurface {...}
>     ...
>     object { Whatever }
>
> you should use (at least temporarily)
>
>     isosurface {...}
>
> as this will allow POV-Ray to give you a warning if it thinks your
> max_gradient is a poor choice (whether unnecessarily high or too low).
>
>
> Alternatively, use the brand-new development release I posted about a
> couple of minutes ago, which should be able to do the same stunt without
> any changes to your scene file.
>


"Shutdown Warning: The maximum gradient found was 32.504, but 
max_gradient of the isosurface was set to 100.000. Adjust max_gradient 
to get a faster rendering of the isosurface."

According to this, max_gradient setting is not the problem, right?

Mike


Post a reply to this message

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