"LibraryMan" <mrm### [at] attnet> wrote in message
news:web.3dab2e4bb35cc47c2b597c920@news.povray.org...

> Again, the specific area the camera is trained on (exact same location &
> look_at vectors) has not really changed that much, but other objects in
the
> POV file must really be slowing everything down!  And they're not even
> visible to the camera!! AARRGH!
> Many thanks,
> MMW

Is the area the camera is looking at reflective? If it is, the not visible
parts will
have to be calculated.

Are you using photons? isosurfaces? media? They can all be quite slow,
especially
used in combination.

What I tend to do is the folloing, at the top of the file I define switches
for parts of the
scene

eg from a current scene of mine

#declare ShowGlobe=0;
#declare ShowCat=0;

then later in the scene

#if (ShowGlobe=1)
    // all the code for the globe
#end

#if (ShowCat=1)
  // all the code for the cat
#end

This makes it very easy to turn parts of the scene off which gets
very important when render time for the entire scene > 20hr.

If you want more specific help, you'll have to post your code.
Don't worry about the messiness, we've all been there.

Gail
--
#macro G(H,S)disc{0z.4pigment{onion color_map{[0rgb<sin(H/pi)cos(S/pi)*(H<6)
cos(S/pi)*(H>6)>*18][.4rgb 0]}}translate<H-5S-3,9>}#end G(3,5)G(2,5.5)G(1,5)
G(.6,4)G(.5,3)G(.6,2)G(1,1)G(2,.5)G(3,.7)G(3.2,1.6)G(3.1,2.5)G(2.2,2.5)G(9,5
)G(8,5.5)G(7,5)G(7,4)G(7.7,3.3)G(8.3,2.7)G(9,2)G(9,1)G(8,.5)G(7,1)///GS

Post a reply to this message