[Josephus Holt]

JD, I ran a short animation for a sun study and enabled "cache meshes" (the view stayed constant, only the time/date changed from frame to frame), however, every new frame I got this message "cached mx meshes have been invalidated" resulting in recreating the meshes for every frame.

[JDHill]

How did you create the animation? Are you trying to use Rhino's sun study, or are you scripting the plugin, as demonstrated in the manual?

[Josephus Holt]

I did it the way you told me some time ago as to how to batch render.
I set up the scene/lighting for the first date/time>"start animation">"render", then changed the date/time>"render", etc until the last date/time, then "end animation".

[JDHill]

Pretty sure I know what's happening - do you have the 'show sun in viewport' feature enabled? That moves a light in the viewport, and this causes the plugin to invalidate its cache. If anything physical in the scene is added, deleted, moved, etc., then the cache will be invalidated. The only actions which will not invalidate the cache are changes to the camera's position, material assignments, and scene parameter changes.

[Josephus Holt]

Pretty sure I know what's happening - do you have the 'show sun in viewport' feature enabled? That moves a light in the viewport, and this causes the plugin to invalidate its cache. If anything physical in the scene is added, deleted, moved, etc., then the cache will be invalidated. The only actions which will not invalidate the cache are changes to the camera's position, material assignments, and scene parameter changes.

Yes, I've had it enabled during this process. Will have to remember to disable it...next time.

[osuire]

Jeremy,
shouldn't this be considered as a minor bug ?
I would suggest to add the sun light object displacements to the list of things that do not invalidate the cached meshes.

Cheers,

--
Olivier

[JDHill]

Well, not a bug, really, but I'll see what it would cost (i.e. in processing) to try to single out that one object.