On 3/8/2017 1:15 PM, omniverse wrote:
> Mike Horvath <mik### [at] gmailcom> wrote:
>> I am having the same problem in a different scene posted in p.t.s-f.
>>
>> This time I used "evaluate" from the start. Render times are long but
>> artifacts still appear.
>
> Yow! I used max_gradient alone to see what POV-Ray was saying it wanted that to
> be and its way beyond what the other isosurface evaluate parameters were.
> Which BTW I finally ended up using MinFactor=0.7 to prevent any missing portions
> of that one.
>
> This current isosurface using max_gradient 10000 (sans evaluate) is rendering 5
> minutes at only 160X120 resolution, incomplete of course.
>
> Render message told me it needed max_gradient 7131910.500, so that really puts
> the evaluate numbers up there and the render time is obviously going to increase
> dramatically.
>
> Sorry I don't have a solution, can only tell you that much. If there's a way to
> reduce render times and still get a complete isosurface for this one I sure
> don't know the answer. Unless something can be manipulated to do so and someone
> else knows how to go about it anyway.
>
> Bob
>

I think clipka told me to use this:

	#declare cie_fClip1 = function(X,A) {select(X-A,A,X)}
	#declare cie_fClip2 = function(X,A) {select(-(X-A),A,X)}
	#declare cie_fD = function(C) 
{abs(cie_fClip2(cie_fClip1(C,-0.1),1.1)-0.5)-0.5}

instead of this:

	#declare cie_fD = function(C) {abs(C-0.5)-0.5}

as a workaround.


Mike

Post a reply to this message