Bintang Senja Pratama writes:
Hello Everyone,
I want to share about how to setup an alembic workflow for an animation production.
Start from preparing the asset that is useful for lighting, export an alembic from animation scene.
And finally link the asset to new scene and apply that shot alembic without worrying about materials assignment on every shot because we use an asset that prepared for lighting at first, so we can use this asset on multiple shot which use different animation alembic cache, and also without rig in our lighting scene which is neat.
At the end of the day lighters only need to focus in lighting, not a complex rig in their scene. :)
Please note that what I show you in the video is the manual process, you can automate all those steps using python to be able effectively use it in production. ^^
Thanks
5 Comments
Sorry perhaps its me, im none English, but that intro was very confusing to read. Could only make up half of what was said.
Not sure what the benefit of this is inside a blender workflow. Seems more like a hustle compared to using blend files???
say you want to create crowds , having a croud of precached alembic characters is much "cheaper" in terms of performance than having live rigs in a scene.
Found this by accident, but anything after 05:30 raises more questions than the video answers imho.
Why create a library override when you make things local?
Why make just the objects local, when the vertex data is still linked? Doesn't that prevent it from working?
How is the file path to the Alembic empty? It's not in a test scene.
What happens if the model changes? You will have to replace everything in the chain?
Thank you for sharing this. I've used a similar workflow using Maya in two production environments in the past. It's a brilliant workflow when working in a departmentalized team. I've been looking for a way to recreate it in Blender now that we're making the shift, so tutorial is invaluable. Thank you.