In article <3e775c35@news.povray.org> , "Scott Gammans" 
<nos### [at] scottgammansspamisevilcom> wrote:

> Thank you for your usual nasty reply, Thorsten. At least the others gave
> useful replies without the sour attitude.

Well, you asked if it makes any sense!  And several of the other replies
where incorrect.  Or assume that the textures are what is slowing you down
(which can neither be confirmed nor denied without the actual scene).  In
fact, if the sum of objects makes the whole slower than the two parts, then
your problem is insufficient memory and not POV-Ray.

Anyway, in fact, a bit of simple logical thinking gives you the answer to
your question right away...

Originally you have the following times:
Object Intersection 1 + Texture 1 + Object Intersection 2 + Texture 2
(actually less for textures assuming one object hides the other)

Your current way of rendering both separately gives the following times:
Object Intersection 1 + Texture 1 + Object Intersection 2 + Texture 2

Your suggested feature however will result in the following work being done:
Object Intersection 1 + Texture 1 + Object Intersection 2
Object Intersection 2 + Texture 2 + Object Intersection 1

As you can see, your suggestion will always take longer.  Consequently it
does not make sense.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message