-
more cloner time offset woes
So I guess any expresso tag inside the cloner doesn’t figure into any time offset set in the cloner. I have a few xpresso nodes inside an xpresso tag inside the cloner that are being driven by animation attached to objects also inside the cloner that do get offset in time but it seems the xpresso rig is taking the keyframes from the original time the keyframes live at and not the time offset that animated object is now rendering at. I’ve tried changing execution ordering thinking that might be the issue but perhaps I’m expecting too much of the cloner.
In addition, any textures with animations that are on the animated objects being offset in time also don’t get moved in time. So I guess this sort of time shifting is only good for those colored cubes that are in all the examples or things that have static textures.There isn’t a global time vs local time node is there? like the position attributes?
And just for fun I tried cloning just one instance – figuring that it might be too much to expect there would multilple virtual xpresso nodes generated. Nope – even with only one instance (I’m not really rendering instances, just setting the count to 1) it can’t do it either for xpresso or the textures.
So I guess instead of insanely compex shots like a billion sentinals swarming Neo, I can only do color cubes. I suppose I could put an unanimated frown on their 6 faces to make them look menacing. 🙁