Some FBX files contains takes. If they do, Houdini creates takes upon import. Both these approaches seemed to work well for me using H19.
Open Take List and left-button drag some take onto Main. A pop menu allows to pick "Merge take (with override)". Simply "Merge take" is not enough as both Main and the unwanted take has values for the same channels.
In a Textport window: takemerge -f Main <name-of-unwanted take> Again it's the -f that does the trick of forcing the merge even though it means overriding Mains animation channels.
Rene Jensen Some FBX files contains takes. If they do, Houdini creates takes upon import. Both these approaches seemed to work well for me using H19.
Open Take List and left-button drag some take onto Main. A pop menu allows to pick "Merge take (with override)". Simply "Merge take" is not enough as both Main and the unwanted take has values for the same channels.
In a Textport window: takemerge -f Main <name-of-unwanted take> Again it's the -f that does the trick of forcing the merge even though it means overriding Mains animation channels.
Once merged, I just delete the unwanted take.
Uuggh, i got sabotaged by that FBX import, though i liked the nice brownish colors everywhere i didn't realize that's what it was. Working for hours with autotake on without knowing... and then stuck with that take with all the complications it brings down the road.
I'm trying to do the merge upward and it either crashes or hangs forever. No lucvk so far to get rid of that nuisance. Sorry to say but why am i not prompted about takes and auto takes upon import?
Cheers,
A.
EDIT: The textport method did it. The merge in the take list did not. THanks a lot.