Light cache hangs up.

[gadzooks]

Light Cache will not caculate. It just hangs up at 0 percent. This is a scene that has rendered many time in the past now all of a sudden it will not render anymore?

[vlado]

Are you able to cancel the calculation?

Best regards,
Vlado

[gadzooks]

yes. It processes the geometry and then goes into the light cache caculation ,and then it just sits thier. Its funny Vlado i just opened it up the other day and rendered several shots from it? Any ideas? Thanks Vlado

[dbuchhofer]

If you are using any visibility tracks, you cannot use light cache..

thats the main one i know of as yet.

[gadzooks]

What do you mean buy visibility tracks?

[gadzooks]

vlado any suggestions? Thanks

[Dynedain]

visibility track is an animateable track to control whether an object is visible or not.... its insanely slow though, even in scanline

[vlado]

It would be best if you can get me the scene so that I can and reproduce that here; it's hard to say what's going on right away. Usually this kind of stuff happens when there is an "explosion" of ray paths somewhere in the scene. Sometimes this may due to blend/shellac materials, transparent objects or object with visibility between 0 and 1 etc.

Best regards,
Vlado

[ngrava]

Are you using any kind of dynamic geometry? Recently I had a scene where I used the Vray displacement mod to smooth the object. It rendered fine until I upped the frame size for print rez. It never rendered after that. Eventually I replaced the displacement mod with a turbosmooth and it worked just fine. luckily I wasn't using displacements or I would have been screwed.

-=GB=-

[vlado]

Are you using any kind of dynamic geometry? Recently I had a scene where I used the Vray displacement mod to smooth the object. It rendered fine until I upped the frame size for print rez. It never rendered after that. Eventually I replaced the displacement mod with a turbosmooth and it worked just fine. luckily I wasn't using displacements or I would have been screwed.

-=GB=-

You could have just modified the Edge length value for the displacement/subdivision. This is a resolution-dependent parameter - higher resolutions mean a finer tesselation for the object, and therefore more memory.

Best regards,
Vlado