Flame workflow in combustion

[Anonymous]

More than once I heard about using combustion like a flame artist to increase combustion speed: precomping, secondary connection in schematic, etc, etc….
Since I’m not yet a flame compositor I really miss the point.
If there’s a way to improve Combustion workflow and render speed I think Flame users should share this to help little brother’s compositors.
Thank’s

[loops]

Precomping helps whatever tool you’re using. In Flame you can do this really easily in Batch now with the per-node caching. You could do a similar thing in Combustion by just letting it play through the part of the tree you want to cache, displaying the appropriate node. As I understand it Combustion will only cache what’s shown in a viewport (I think… anyone confirm?), so you have to be looking at the node to cache it. But after that, downstream operators can use the cache instead of recomputing.

Of course you’ll rapidly run out of memory if you do this much 🙂 But you can easily precomp to disk using by commiting operators, which renders them out, imports the result and hooks it up to a switch. Not as fast as memory caching but worth it for long things that you’re sure about.

Not sure what you mean about the secondary connections on operators… can’t really think of any way to use them other than the obvious 🙂

[Anonymous]

Thnak’s for your reply..
about the secondary connection use I don’t mean anything….is somethng I’ve often found mentioned by other users here, especially flame users, that’s why I was asking.
I’m curious since the only way I use it is when is available…can’ t really imagine other ways to use it.
Pre comping or nesting is not a secret to most of the combustioner users as committing to disk (just right clck on the layer or the node in the schematic view) so once again I’m wondering if there’s another way to tune combustion up by then.
First time I read something about that was here on topic like desktops applications vs. FFI.
Saludos

[Author]

Posts