POV-Ray : Newsgroups : povray.beta-test : Code gets the processor too hot? : Re: Code gets the processor too hot? Server Time
3 May 2024 12:21:24 EDT (-0400)
  Re: Code gets the processor too hot?  
From: Ger
Date: 2 Apr 2013 13:20:50
Message: <515b1372@news.povray.org>
clipka wrote:

> Am 02.04.2013 08:45, schrieb Ger:
>>
>> If you look at the code then you'll see that in both cases the object in
>> view is something like
>>
>> difference {
>>    union {
>>      box {}
>>      cone {}
>>      torus{}
>>      }
>>    50 x frame_number // for each iteration the same
>>    sphere{}
>>    }
>>
> 
> Nope; the code the Erode macro generates is
> 
> difference {
>    difference {
>      difference {
>        object { ObjectToErode }
>        sphere {}
>      }
>      sphere {}
>    }
>    sphere {}
> }
> 
> whereas the code the Erode1 macro generates is
> 
> difference {
>    object { ObjectToErode }
>    sphere {}
>    sphere {}
>    sphere {}
> }
> 

True, I stand corrected.

> Note that POV-Ray doesn't collapse nested differences into a single one
> (although it would probably be a good idea).

I have looked at the source code to find out as to what might possibly cause 
this, but it's several miles beyond my knowledge of code. (I don't go much 
further then "hello world")

-- 
Ger


Post a reply to this message

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