|
When you work in Nuke you also can't freeze your
sequence. You either use a cache node or render out a file
sequence to disk.
Indeed, and it's not at-all uncommon to do so to speed things up
and or re-starting from a given point as an initial state.
I guess it was mostly to streamline that a bit.
On 02/22/17 11:27, Florian Breg wrote:
Working in Houdini is more similar to working in
Nuke than working in SI/Maya/etc if you ask me.
With Houdini you have data (e.g. bgeo, abc) that
is stored externally and the "scenes" more or less only
contain the rules to modify this external data.
Traditional 3D apps store data (e.g. polymeshes)
and the rules (e.g. operators) in the scene if you don't use
referenced models. That's why you can easily freeze stuff and
why it makes sense to do so.
When you work in Nuke you also can't freeze your
sequence. You either use a cache node or render out a file
sequence to disk. It is the same way in houdini.
One of Jordi's PDFs explained it in a more
elegant and complete way if I remember correctly. Maybe you
give them a try.
Have fun learning Houdini. It is worth it.
Cheers,
Flo
------
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
|
------
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with
"unsubscribe" in the subject, and reply to confirm.
