Thanks, guys!
And, cheers for the hints, Hetzen, any shortcuts and tips are appreciated, it does feel like a juggling act when using TG for animating sometimes.
Is there any(this will have been asked before, no doubt) way to move keyframed content to a different set of keyframes, without actually having to manually transfer keyframed parameters? For instance, I'll often start something, get 200 frames in then, realize that something actually needs to happen before frame 1.(I know you can invert the sequence stepping, that's not what I mean, though, and it brings its own problems when working in a both negative and positive timeline), can I simply, for example,
'cut/copy keyframed animation' then,
'Paste before/into/after selected frame', effectually just moving things back/forward in time?
If it is possible, it isn't obviously clear how to do it, I've resigned myself to duplicating the animated nodes that need bumped along, hitting 'stay open', and then deleting the entire animated parameter in the node I am working with, to copy inputs by hand over a different time and obviously needing to flick between those separate frames to see the keyframed item values.
I'm not moaning, by the way, that kind of sounds a bit gripey up there. ^^
WAHHH! Why can't I do these extremely simple things?. I know that the animation functions are very basic for now, just wondering if I'm missing something that's right in front of me. I usually do.
_______________________________________
And, here's a tip that I've found, too, while I'm here: I've noticed that you(or, I) can't really animate cloud layer quality settings via the 'quality' slider. You must animate 'samples', otherwise, as soon as a cloud layer's properties change, even when the quality slider is keyframed, the 'sample' field does not update accordingly and you can end up with insanely long render times for less clouds than you've begun with because, when the samples do update, sometimes seemingly randomly, but always, I've noticed, if you touch the 'quality' parameter again at all, then you might end up with a quality value of 15.xxxx because the 'samples' won't auto-refresh between keyframes.
You have to always
type the 'quality' you want to keep between frames but,
never keyframe it. Instead, keyframe the newly updated 'cloud samples' that will refresh instantly from your input in the other field.
That kind of sounds like the opposite of the advice I think I'd like to give, or hear, about TG cloud quality, I'd like to tell TG to stay at quality='1' for xx amount of frames and have the samples react to
that value. You just can't be certain that on the way back down from high sample quality clouds, to less demanding clouds, that it will correctly refresh the .tgd.
Anyway, this is really what I always liked about TG2, you just get a grey window full of words and numbers and work it out yourself, like a Rubik's Cube!
Either that or, you
think you've got it worked out and then realise that you've left that one bloody green square on the red face...
