For those who don’t know the tool: Redshift from Maxon is a GPU renderer for Cinema 4D, Maya, 3ds Max, Houdini and Katana. It targets final-frame GPU rendering and USD Solaris pipelines, sitting at lookdev and lighting in production.

Consolidation, not features

Maxon has released Redshift 2026.3.0. The build includes plugins for Cinema 4D, Maya, 3ds Max, Houdini and Katana. It is a maintenance release focused on stability, host compatibility and incremental displacement updates. No new headline rendering features are introduced.

On Apple hardware, Redshift now requires macOS Sonoma 14 or higher. Maxon recommends macOS Tahoe 26.2 as the latest officially supported version, while noting known rendering artefacts on Intel CPU plus AMD GPU systems on Tahoe. On Windows and Linux, updated NVidia driver minimums apply, including specific requirements for Blackwell 50xx GPUs. Linux requires glibc 2.28 or higher.

Texture displacement cleaned up

Texture displacement receives performance improvements and several correctness fixes. The update resolves holes in meshes, vertical artefacts in the software ray tracer and cases where displacement disappeared on tessellated meshes without UVs.

Support for smooth normals has been added to texture displacement. The UV Context Projection node gains a new camera selection mode for camera projection mapping.

Additional fixes address deformation motion blur with displacement, incorrect auto-bump behaviour, and noisy details on scaled meshes. Material blending issues involving stacking and the Material Blender shader have also been corrected.

Hydra and Solaris updates

Redshift adds support for Houdini 21.0.559 and 21.0.596 and drops support for 20.5.654 and 21.0.440. The Hydra delegate now supports the Solaris 21.0 statistics panel in the latest Houdini 21.0 production build.

Hydra 2.0 fixes include motion blur limitations, primvars sampling issues, light linking problems, nested instancing errors and live updating of custom light and camera parameters. Support has been added for USD implicit surface primitives, USD mesh lights via the Geometry Light LOP, and updated USD and Alembic procedurals. AOV-related bugs affecting ObjectID, Depth, cryptomatte, deep and Refractions Light Groups have been fixed.

Redshift 2026.3 is a stabilisation release aimed at removing pipeline friction introduced in earlier 2026 builds. As always, new tools and innovations should be tested before use in production.

// Redshift 2026.3.0 Release Notes
// https://support.maxon.net/hc/en-us/articles/Redshift-2026-3-0-2026-02-February-10-2026

The post Redshift 2026.3 fixes displacement headaches first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

A tasting of the dynamics and geometrys side (of) effects

This release is not about the number of features, but about finishing what was started, achieving true production readiness, robustness, performance, and ease of use. It’s a version focused on quality of life. Feature sets like MPM simulations and Karma have matured like a good wine. The machine learning tools respect the artist’s skill set and have left their state of play are actual usefull in production.

Even though SideFX remains modest in its official statements, Houdini 21 is a massive release. For the feature-hungry among us, the highlights include a fully matured APEX; a refined and clever animation and rigging framework; a simulating Copernicus (think Substance on Dope), and in the VFX realm, the production-ready MPM Solver. On top of that, we’re seeing machine learning tools popping up in all the right places (AI for people who don’t expect a Pixar film from a single click), faster and expanded rendering with Karma, and a healthy dose of quality-of-life improvements.

Since our editorial cat can only count to 300, we can’t tell you the exact number of new or improved features, but we’re impressed nonetheless. And soon, you will be too. To avoid overwhelming both writer and reader, we’re breaking this article into a mini-series. We’ll start with VFX & Geometry, followed by Solaris & Karma, Copernicus & Terrain, and the massive Animation & Rigging tools.

MPM

One of the most exciting additions in H20.5 was without question the MPM Solver. The MaterialPointMethod truly allows you to simulate a wide range of different materials. From water, snow, and sand to honey, metal, and concrete, all within a single Solver setup. The geometry is simply substituted by points or particles, which are then simulated. The different materials interact physically accurate and constraint-free, purely based on their assigned parameters.

The initial release was already impressive, but it left users standing somewhat in the simulated rain when asking: “How do I get a proper mesh with UVs?” That exact issue has now been beautifully solved in H21. Any MPM simulation, whether rigid body or fluid, can now be meshed (as polygons or SDF volumes), including UVs, color, and other attributes, using no more than two nodes.

A nice and usefull addition to this workflow is the MPM Debris node, which generates new points along fracture lines as sources for smoke, dirt, or secondary debris effects. So let’s take a look at meshing hard and fluid or granular surfaces across a few setups and scenarios and wrap things up with a creamed cookies drink while watching the official and very excellent MPM demo.

Surfacing MPM Simulations

Testing time! For this test setup, we’ll have a clay ball smash into a vase model, paying close attention to UV transfer and the generation of smaller fragments through the Debris Source. The easiest way to start an MPM simulation is by typing “MPM Configure” into the node search. This gives you a complete set of starter nodes right away. (Under MPM Configure, you’ll also find plenty of additional example setups for study or creative repurposing.) By the way, the MPM container on the far right controls the overall resolution of the entire simulation.

We replace the default sphere with our own model and can now assign materials directly inside the mpmSource node and tweak them to our liking. It’s genuinely fun. Feels a bit like a mini-game. Since a concrete material would be more realistic but also quite boring as a vase material, we went with Chunky Snow instead. The environment comes in via an Object Merge directly into the mpmCollider Sop, ready to go. Our clay ball, the antagonist of this little simulation, isn’t a collider per definition but another mpmSource ready to be smashed, merged with the vase and given its own material behavior, Chunk Soil.

To make sure the particles can actually see and “love” each other, we need to enable Particle-Level Collision in the solver. The new Auto Sleep feature helps keep the vase passive until the collision happens, preventing it from collapsing at frame one and saving quite a bit of compute time.

Since the clay ball will be meshed as a fluid and granular surface and the vase as a rigid object, we first separate the MPM particles using a Blast node, filtering them by their respective source names.

For surfacing the vase, we use the mpmPostFracture node, which takes the rest-geometry and the MPM particles as input. This node essentially breaks the geometry apart “end to start,” so it needs to be fed the final frame of the simulation. After that, we choose either Voronoi or Boolean Cut as the fracture method. The latter can generate interior details, subtle irregularities on the inner faces of the fracture, that weren’t visible before, and it’s also faster to compute. We can further control the number of pieces as well as define the minimum fragment size at which new pieces should be generated.

The final node in the chain is mpmDeformPieces, which transfers the newly generated fracture geometry onto the MPM particles and just like that, the vase shards, physically convinced they’re made of snow, go flying through the scene, complete with perfectly intact UVs. For more of a muddy mess, we could have generated a liquid or granular surface instead, but we’ll save that for the clay ball. The result from the Debris Source, which lets you precisely define when and where particles based on fracture are emitted, is then passed into a POP network, including collisions from the vase and background).

Time to get serious:

Continuos Emissions & Surface Tension

With this new option, you can quickly fill containers, simulate expanding materials, or layer different materials on top of each other. The option is located in the mpmource node and spreads new particles apart using positive pressure.

Let’s take our vase and let a thick, viscous something ooze out of it. A good chance to show how simple MPM can be: if we want things to float inside the fluid, they just need a lower density. A few cubes are generated and assigned a jelly material. Two geometries, two MPM Sources, merged and fed into the solver. That’s all it takes. Just as easily, you can mix different fluids within the same setup. And for a bit more drama, we can dive into the solver and add a POP Wind node with some turbulence.

Surface tension allows for realistic effects such as droplets, tendrils, and flowing water. H21 introduces two new ways to control surface tension for both liquid and viscous materials inside the MPM Solver. The Point Based method offers higher accuracy and stability, making it ideal for small and detailed simulations. The Grid Based method, on the other hand, is optimized for performance and handles millions of particles more efficiently, which makes it better suited for large-scale scenes. External forces and friction can be increased if objects keep moving when they shouldn’t. Otherwise, you might end up with a scene straight out of Terminator 2.

To achieve high levels of detail without an unnecessarily large number of simulation points, the new, more precise collision detection allows you to use the fracture edges of a simulation as the source for a targeted secondary simulation. The attribute Jp (Plastic Compression/Stretching) is key here. It can be used to isolate the fractured areas and feed them into a Surfacing node set to VDB mode. This resulting volume can then serve as the source for the second simulation. And don’t forget to use the main simulation result as a collider.

And finally to top it off, the official demo. A detailed breakdown of that beautiful cookie shot.

Machine Learning in Dynamics

You won’t find any generative AI native in Houdini, but rather a growing collection of smart, locally running models, often trained by yourself, designed to simplify or speed up time-consuming tasks.

Surfacing Flip, Vellum & Particle Simulations

Alongside Neural Point Surfacing for MPM, the new Neural Point Surface and proven Particle Fluid Surface nodes now bring neural meshing to FLIP, Vellum, and POP simulations as well. Until now a bunch of points are trying to reconstruct the surface of a material. With neural meshing, you can now achieve much sharper, more detailed surfaces across a both high and low frequencies. The result: surfaces that are no longer uniformly fuzzy, but crisp, structured, and temporally stable. As before, you can train your own models, but even the included presets already produce finer details. And thankfully, the whole thing is GPU-accelerated.

Volume Upres

The core problem behind volume up-resing: for efficiency, artists often create and approve low-resolution simulations. But once the voxeldensity is increased, the overall shape of the sim tends to change. With the new tools, a low-res simulation can now be upscaled while preserving its exact shape. This not only keeps previously approved versions intact, but also allows for far more iterations. A model that’s been trained on a specific motion or behavior can now upscale multiple variations of it.

The Billowy Smoke recipe (or shelf tool) comes with a pretrained up-res model already integrated. Let’s start by looking at a comparison between the low-res input simulation and the 3× up-res result.

Details are nicely added, while the overall shape is preserved impressively well. Caching took a bit of time, but it’s still far faster than running a full high-res simulation. The real idea, however, is that we can now reuse this up-res model for all our future Billowy Smoke setups and honestly, we probably should. So, let’s quickly modify the setup and see if we can break the upscaler.

This time, the solver runs at a voxel size of 0.05, using the 2× upscaler. The 3× model didn’t really add more detail, just extra waiting time. For a bit more fun, a Gas Wind with random direction and a collision shape were added. That collision shape, as it turns out, gives the upscaler a bit of trouble as seen below.

But when comparing the up-res result to a true high-res sim, it’s clear that the system is really good at preserving the base form. Doubling the voxel size in the high-res sim, on the other hand, changes the overall shape and eats up a ton of time but stays artifact-free. Or, if you really want perfection, you could just train a model specifically for this type of collision.

If you want to train your own model, this Equinox Hive talk walks you through every detail:

Zibra AI VDB compression

With this plugin you can save up to 99 percent of storage space when caching VDB simulations, which makes it perfectly suited for use in real-time engines such as Unreal Engine 5. The Zibra toolset, distributed via SideFX Labs, provides three dedicated nodes.

The first, zibravdb_compress, writes and exports .zibravdb files for use in Unreal and similar environments. The second, zibravdb_decompress, brings those files back into Houdini. And finally, zibravdb_filecache acts as a modified File Cache node that automatically handles compression, loading, and decompression for further use inside Houdini. Before diving in, you’ll need to download the model and obtain a license, potentially a free personal one if your revenue is below 100 K USD. The license management can be accessed directly from any of the three nodes.

For a quick benchmark, I used the Fireball Recipe and cached one regular VDB sequence alongside two Zibra versions with different quality settings. The original VDB sequence weighed 294 MB. The Zibra compression at a quality setting of 0.2 came in at only 5 MB, roughly 98 percent smaller. At a quality setting of 0.9, the result visually matched the original VDB almost perfectly while staying at just 36 MB, around 88 percent less.
That insane low file size at 0.2 naturally comes at the cost of lost detail, as visible in the comparison graph below. Still, the results are impressive and they open up the possibility for bringing volumetric simulations into real-time pipelines far more efficiently than before.

Pyro Shelve Tool Presets

Another way to get artists up to speed faster are production-ready presets, not just educational examples, but tools meant to be customized for your very real projects. Each of them comes with a ready-to-use Solaris network, fully set up for rendering straight out of the box. Even better, the Help section now includes a short guide and exploanation of important Nodes for every preset.

SideFX strikes a noticeably new tone here, aiming to flatten the learning curve rather than overwhelming newcomers with endless options (which, to be fair, they still do from time to time). These guides can be found under Documentation → What’s New → Pyro. In this section, we’ll take a closer look at three fundamentally different presets, each showcasing its own approach and creative use case.

Stylized Flame

With the refined Copernicus toolset, entirely new worlds open up: stylized fire based on a classic Pyro simulation, right inside Houdini. And if needed, even live-rendered in Solaris.

To put the claim of “easy adaptability” to the test, we took the Pyro Fireball preset and gave it a Toon-style makeover. Adding the VDB field “Flame” inside the solver’s output was all it took to make it work. The output from the Cop node, by the way, can be merged directly into the scene for further Houdini style editing.

Ground Explosion B

This shelf tool sets up a sparse pyro simulation featuring a large-scale explosion, smoke trails, and a shockwave. For more control and efficiency, it’s actually made up of two separate simulations, layered on top of each other and interacting through their velocity fields.

Candle Flame

A candle flame might not be the most exciting thing visually, but it’s one of those Pyro results you end up needing again and again. What makes this preset interesting, though, is the procedurally modeled candle that comes with it. Exploring that setup is almost more fun than the Pyro sim itself.

Thruster FX

In true H21 fashion and in the spirit of overall efficiency boosts, the new Thruster FX tool makes its debut: a setup designed to create engine and propulsion emissions with ease. It’s not just a new node, but rather a complete Recipe, a preconfigured network of nodes that some might, in hushed tones, simply call “presets.”

With a cheerful click on Thruster Exhaust in the Pyro Shelf Tools (or via Configure Thruster in the Tab menu), you’ll get a fully adaptable node tree, including a ready-to-render Solaris network. The effect itself isn’t a simulation but a cleverly layered, art-directable procedural system built around VOP Nodes. Multiple pyrothrusterexhaust nodes are stacked in layers, each responsible for different components like sparks, fire, and plasma. All working together to form a surprisingly easy to use thruster system.

So, what does it actually look like? And can it really be used straight out of the box, as promised? The short answer: pretty much, yes. The rendering comes surprisingly close to the viewport preview. To get it running, only a few connections inside the included Solaris network needed to be adjusted. For our small test scene, we did a bit of kitbashing inside Solaris, then added some glow and polish in Fusion.

Let’s take a closer look at the node, both from the outside and under the hood. The node expects a primitive as input, and a simple circle usually does the trick. It outputs both particles and a volume containing density and temperature fields. In the General tab, you can control speed, length, and the overall shape via a spline ramp. The Exhaust section handles the color ramp and lets you tweak the underlying noise pattern, which has a strong impact on the overall form. Under the hood, the node generates a VDB from Polygon, then modifies the result with a Volume VOP and a Volume Adjust Fog node.

As part of the ongoing effort to simplify things and lower the learning curve, SideFX has also released a good and detailed tutorial mini series: sidefx.com/tutorials/how-to-create-thruster-fx

Car Destruction FX

So that we can also crash the rigs built with the Car Rig SOP introduced in H20.5, Houdini 21 brings us the new Car Destruction Tools, led by the mighty RBD Car Fracture SOP, supported by the RBD Car Transform SOP. The first one takes care of fracturing and constraint creation, automatically handling the typical materials you’d expect in a vehicle: glass, metal, wood, and rubber. The RBD Car Transform SOP, similar to Transform Pieces, ensures that all pre-fractured parts are efficiently transformed based on the simulation points. You’re not limited to cars, by the way. Anything that follows the same basic logic can be blown apart. From motorcycles to helicopters, it all breaks just fine.

Destruction-hungry artists will find a detailed yet easy-to-follow example scene in the SideFX Content Library, the same visuals you might recognize from the keynote: sidefx.com/carbd-dual-car-collision/. A fitting go-through video can be found here:

Geometry, Viewport and other tasty QoL

Coming from its deep VFX roots, Houdini has taken quite a journey to establish its own distinct style of procedural modeling. With H21, that journey continues, extending existing nodes and adding a few genuinely useful new ones along the way. This time, even the viewport got some well-deserved love, now powered by Vulkan and capable of loading Gaussian Splats directly.

Sculpting in Time

The Sculpt SOP, introduced in H20.5 and (surprisingly) quite useful, now gets a genuinely groundbreaking new feature called Shot Sculpting allowing time-based, keyframe-free sculpting. Originally intended as a correction tool for character animation, the node turns out to be just as handy for VFX and motion design work.

Temporal control is handled through the Shot Sculpt panel, which at first glance looks a lot like an NLE timeline and, in principle, works much the same way. Sculpting can be organized into layers that can be offset in time, faded in and out (complete with easing), muted, or adjusted in opacity. Alternatively, you can use mask_track to paint time-based attributes, which can then be passed downstream and used in other nodes, for an obvious example, as masks.

Otherwise, the same rules apply as for the regular Sculpt SOP, whose updates we’ll take a look at next. In line with the new Shot Sculpting feature, the mask system has been reworked. Masks can still be painted manually, but can now also be loaded from an upstream float attribute, saved permanently, and blurred or sharpened as needed.

There are also new brushes. My personal highlight, the Elastic Grab brush:

Of course, the complexity and depth of ZBrush remain unmatched, but for many tasks, artists can now comfortably stay right inside Houdini.

Geometry Masks

There are also updates when it comes to masking. Several well-known nodes now include a Mask parameter, allowing the effect to be restricted to a painted or procedurally generated mask. Among them: Peak SOP, Soft Peak SOP, Inflate SOP, Flatten SOP, and Point Jitter SOP.

UV Flatten from Points

The latest addition to Houdini’s already powerful UV toolset could just as well be called “UV from Voronoi” since that’s exactly what it’s based on. The node distributes random or precisely placed points across the surface and uses them to calculate clean, non-overlapping UVs. It’s primarily designed for complex, high-resolution meshes, where traditional unwrapping tends to get messy fast.

Vulkan Viewport

Now enabled by default, the new Vulkan 3D viewport offers noticeably improved lighting, Ambient Occlusion, shading and ray tracing with built-in denoising, and a more accurate texture display though performance can take a hit if you push it too far. New worklights including a fully adjustable Dome Light, Physical Sky, and Three-Point Light setup now serve as the default viewport lighting.

Looking toward the future, the viewport can now display Gaussian Splats directly. Since splats are essentially just point clouds, and Houdini is fundamentally point-based, this opens up a rather promising combination. The .ply file can simply be loaded via a File SOP and passed into a Bake Splat SOP for further processing. From there, you can treat and manipulate the splats just like any other geometry using the usual SOP tools. More on rendering those Splats in the upcoming section on Solaris & Karma.

Curve Tools

The new Extract Contours SOP can generate object outlines from a camera’s perspective either directly as edges or as an edge group. Quite handy for toon-style effects.

The well-known Curve SOP now allows you to interactively split points into branches (with unique vertex numbers) or fuse them back together.

Unsubdivide

If things ever get a bit too much, this node can reconstruct a low-res input geometry based on Catmull-Clark.

Conclusion after some bottles of VFX

Even though the stated (and achieved) goal of H21 was mainly polishing existing systems and adding plenty of quality-of-life improvements, it still manages to sneak in a massive load of new features along the way. And we’ve only scratched the surface here. Deep dives on Copernicus, Solaris, Karma, Rigging, and Animation are already in the works.

What’s also refreshing is the ongoing effort to flatten the learning curve through better documentation, tons of in-house tutorials, and solid example files in the Content Library. Many things have become easier or let’s say, more accessible, without losing depth, at least for those who want to go there. As always, most nodes can still be cracked open and modified at their core. Nice one, SideFX.

The post Houdini 21: Like good wine (Part1, VFX & Geo) first appeared on DIGITAL PRODUCTION and was written by Manuel Kotulla.

With The Conjuring: Last Rites crossing the $500M mark to become the highest-grossing horror film of 2025, Digital Domain stood at the heart of the film’s supernatural terror. Under the supervision of Alex Millet, the studio delivered 425 shots ranging from invisible fixes to hero sequences: Annabelle’s monstrous transformation into a 12-foot stalker, Abigail Arnold’s unnerving smile, the haunted mirror’s shattering hallway nightmare, and an entire Pennsylvania mill town built in CG. Armed with Houdini, Nuke, Maya, Solaris, Photoshop, and V-Ray, the team balanced photorealism with dread, crafting visuals that were frighteningly real without ever slipping into camp. We sat down with Millet to discuss scope, artistry, and the technical pipelines behind conjuring digital horror.

Meet Alex Millet (IMDB | Linkedin), a familiar face in the world of visual effects and someone whose résumé reads like a tour through modern cinema. Currently Visual Effects Supervisor at Digital Domain, Alex began his career as a lighting and look-development artist, later moving through roles as CG Supervisor, Sequence Supervisor and DFX Supervisor.

His filmography spans some of the most recognisable titles in contemporary filmmaking, including The Dark Knight Rises, Inception, Doctor Strange in the Multiverse of Madness and The Electric State. Each project sharpened his eye for realism and storytelling through light, texture and composition, preparing him for his latest haunting venture with The Conjuring: Last Rites (2025).

DP: Alex, can you start by outlining the scope of Digital Domain’s work on The Conjuring: Last Rites?

Alex Millet: The major effects were the Smurl street environment, the hallway destruction and the Annabelle doll sequence. Combined, these represented a little over half of the scope. On top of these, we also had a very complex ceiling replacement in the mirror room, a CG dog, some fire enhancement and along with many other invisible effects such as glasses reflections, TV insert, background replacement, etc. The team grew up to about 150 artists, and production lasted about 8 months. 

DP: Which sequences do you personally consider the centerpiece of your team’s work, and why?

Alex Millet: The Smurl environment was a big part of our scope. We recreated the entire street surrounding the Smurls’ house and the looming factory. The environment was seen in multiple sequences at different times of day, each with different lighting and “life” in the neighbourhood. The hallway destruction was another big challenge because of all the destruction that we had to create. And, of course, Annabelle being so iconic, the sequence where she comes to life was an important one.

DP: Horror relies on timing and subtlety. How did you collaborate with the director and editorial team to ensure the VFX didn’t overwhelm, but instead amplified the tension?

Alex Millet:Scott Edelstein was the VFX Supervisor on the production side and our main link with the director, Michael Chaves. Working with Scott and Michael was amazing; they were open to ideas and understood what was possible, which made it feel very collaborative.

The goal for us is always for our effect to disappear and blend with the on-set photography to complement the look and feeling the director created. We match every detail as closely as we can; down to the subtle amount of wind in the atmosphere. The production team did a great job anticipating our needs while shooting, which made it a lot easier to integrate our image and keep our effect non-distracting.

DP: The Annabelle transformation is one of the film’s signature moments. What were the creative conversations around taking an iconic prop and making it terrifying at a larger-than-life scale?

Alex Millet:We started by building a CG version of the original doll, then turned it into the 12-foot version. As the giant version came to life in the hallway, the iterative process began. The 12-foot version of Annabelle went through a few rounds of redesign to become the scary character that the director wanted to see. Once the new look was found, we received a concept and started rebuilding our asset and worked on a new post viz. Annabelle needed to look determined and threatening as she came out of the room, yet not totally in control of her body.

As the animation team took over, some aspects they focused on were Annabelle’s silhouette, matching some of the poses established during the concept phase, and the transformation. The transformation needed to feel abrupt, painful, and scary. We scaled different limbs at different times across the cut while working very closely with our CFX team to make sure the jerky motion did not break the dress simulation or make it distracting. The lighting also played a key role in the scare, keeping things dark yet revealing just enough to feel Annabelle’s presence, until the final jump scare with the flashlight.

DP: Abigail Arnold’s smile is disturbingly subtle. How much back-and-forth was involved in refining something so specific, yet so essential to the character’s menace?

Alex Millet: We were lucky that the Director, Michael Chaves, is quite VFX-savvy, and provided us with a concept of the look and smile he wanted Abigail to have. The goal was to match his concept and bring her to life. We started with recreating the concept for different lighting scenarios, then developed a range of smile variations, ranging from neutral to wide extended smiles. The director was then able to select the right performance and the range of the smile that worked for the shots.

A lot of the subtlety is in everything around the smile. The mouth only moves so much, but the way the cheeks, nostrils, eyelids or even eyebrows, compress and deform, all contribute to the realism and expression. Once we had selected range we refined the motion further, and the compositing team integrated the new face into the shot. We used this process for different shots, all in different lighting environments.

DP: Horror effects can easily cross the line into unintentional comedy, the dreaded “absurdist 80s VHS fail.” How do you dial a CG effect into the sweet spot where it reads as horrifying, not parody?

Alex Millet: Here again, blending into the tone and vision established by the practical photography is always the most important for the effects. Our goal is always to make sure the VFX are as seamless as possible, and not distracting.

Other than matching the look, lighting and ambience of what was done on set, that also means making sure that any animation does not go over the top, and breaks the tension. The Abigail smile was a great example, we could get a much wider range for a smile but instead, the more subtle ones, and in some cases barely moving at all, kept her looking disturbing.

DP: Any tips for your peers on how to land that “maximum horror” effect faster in iteration, instead of burning weeks on trial and error?

Alex Millet: Hiding things is often a lot scarier than trying to explicitly create something scary. As VFX artists, we’re very analytical of our images and want to see every detail to make sure it’s perfect, but in this case, we needed to hide part of the image and let things fall into darkness. We’re still just as concerned with every detail; it’s more of an extra step: now that we know how it looks, what does it look like way darker? What parts are gone, and which ones are left. We, then, let the audience fill in the blanks.

DP: You’ve mentioned the Pennsylvania mill town environment. Can you walk us through how the team extended sets into a fully believable small town, while keeping continuity across day and night shots?

Alex Millet: We knew we were going to see the street in many different shots, angles and lighting scenarios; we just didn’t know what these were going to be until the edit stabilized. So it started with concept work, then committed pretty early on to building the entire street as a fully renderable CG asset.

We started with a rough 3D layout of the neighbourhood, then focused on the street the Smurls’ house was on. We built the houses in a modular way, like Lego blocks, and split them between the different floors and roofs, so we could easily swap the different pieces and create a lot of variations. This allowed us to start working on our assets to a high level of detail early on, and also prevented having to redo work if, for example, Scott or Michael wanted to move a particular house, or change the roof on another.

Once the VFX sup & director were happy with the look in some early development shots, we worked on the different lighting environments and added life with props, cars, atmosphere, etc. So having the street fully built made it easy to maintain continuity across the shots, or break it if we wanted to do so for creative reasons. Around the CG street, we used 2.5D, mixing matte painting with supporting geometry for the factory and background, and lastly, the far background and sky were 2D matte painting.

DP: Beyond the big hero moments, you delivered a large volume of invisible effects, reflections, vehicles, ceiling replacements. What kind of pipeline ensures consistency across such a wide range of tasks?

Alex Millet: Having a scalable pipeline is key. Many individual effects were only for a few shots, while others, like the Smurl street or the hallway destruction, spanned over 100+ shots. Having a single but scalable pipeline allows us to be nimble and iterate quickly to get started, but then scale up to handle any volume of shots. If things change, it also prevents us from having to go back and build things differently or with a different approach.

DP: Let’s talk specifically about the mirror sequence. How did you design your glass-break pipeline for that scene?

Alex Millet: We had to create the shattering glass in the hallway sequence as well as the crack that’s on the mirror throughout the movie. Glass is really unforgiving in the sense that it needs to be fully built for all the reflections and refractions to behave correctly; there is no shortcut. Our asset team built a CG version of the mirror first, ensuring the glass layer had the correct thickness and reflection behaviour.

Then for the shattering, the FX team fractured the glass with an evolving crack. Fracture simulations don’t always result in the cleanest geometry and with glass, any imperfection can result in unwanted highlights. So after the glass was fractured in FX, we went back to the asset team and spent more time refining the geometry to make sure everything behaved correctly and looked as real as possible. For the static cracks, we had a different approach and started with a 2D concept of the overall shape, then sculpted it directly into the geometry.

DP: The haunted mirror and hallway destruction sequence demanded complex simulation. What tools and workflows did you lean on to ensure the scene felt both physically credible and cinematically heightened?

Alex Millet: The hallway sequence was a challenge. We started with building a CG version of the hallway that had to be water-tight to work with the FX simulations. Our assets are mainly built in Maya for modelling, Mari for texturing, then Houdini & VRay for Lookdev.

Once our asset matched the set, we added some extra geometry behind the walls and floor, to be revealed during the destruction and added material variations to the debris. The next step was to animate the mirror moving through the wall and start working on the look of the broken wood and floorboard simulation.

Our FX team, working in Houdini, did different iterations of breaking wood and drywall to find that rhythm and dynamic pop in the destruction. We also played with different amounts of smoke, either slowly filling the room or shooting from the impacts. We then went back to lookdev to create some procedural materials for the additional geometry.

That’s all the inside faces that didn’t exist in the original model and were created once the geometry was fractured. Some of the finer effects, like smoke or fine particles, went directly from the FX team to the compositing team, but the main fractured geometry was passed to the lighting team to render with the mirror and the rest of the hallway. The lighting team rendered everything with VRay and Solaris in Houdini, then passed it to the compositing team to put all the elements together in Nuke.

DP: How many iterations did it take to nail the timing and behavior of the breakage, and how did you balance simulation randomness with director’s notes?

Alex Millet: The biggest challenge was to tie in the propagating crack, which was an FX simulation, with the main cracks. The main cracks, under the actor’s hands, had a very specific art direction to look like they originated from the hand. They also needed the right timing to happen when the actors touched the mirror. We laid out the main impact points first, then matched the speed of the simulated propagating crack to tie everything in.

Once the timing worked, we tweaked the geometry of our propagating crack once more so the lines would connect with the main impacts. The final effect was meant to look like a single event, moving across the entire glass but with specific impact points tied to the actor’s performance..

DP: Looking back, what do you consider the biggest technical achievement of your team on The Conjuring: Last Rites?

Alex Millet: The hallway sequence was an interesting technical challenge; it came in late in the schedule, but required a full rebuild of the hallway and a heavy amount of FX destruction in almost every shot. The mirror was plowing through the walls and floors, and we needed to maintain some consistency in the destruction across the sequence.

We also had to be very careful of the actors’ reflections, as we sometimes had to replace the mirror with a CG one for the animation and destruction to work, but we needed to maintain the actors’ reflections. Overall, the biggest challenge of the project was the aggressive timeline and wide scope of work; we had a big environment build with the Smurl street, a lot of FX simulation, some animation and character work with Annabelle and Abigail, a huge oner shot, and the list goes on. The team did an amazing job delivering this project on time and without any outstanding notes.

The post When Annabelle Grew Up: The Digital Domain Horror Pipeline first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Cargo 2.0: new importer, larger free library

KitBash3D has released Cargo 2.0, the rebuilt version of its asset manager for browsing and importing KitBash3D’s architectural and environment kits. The update arrives with a redesigned Houdini importer, co-developed with SideFX, that integrates natively into Solaris and exports all content in USD.

Alongside the importer, Cargo 2.0 expands its free offering. Users of the free Cargo Basic account now receive access to 364 free assets:

• 215 modular 3D models
• 141 materials
• 8 vehicles

All assets include textures up to 4K resolution in PNG or JPG. These files can be used in personal projects such as portfolios, student reels, or tests. Commercial use requires either purchasing the individual kit or upgrading to a paid Cargo subscription.

Houdini Solaris integration

The most significant change in Cargo 2.0 is the Houdini importer. KitBash3D rebuilt the plugin in collaboration with SideFX, ensuring that it works natively with Solaris. Assets imported through Cargo appear directly in Houdini’s Asset Catalog as USD files, complete with automatically generated thumbnails. Once imported, they remain in the catalogue across sessions, avoiding the need to reimport them for every new project.

Materials integrate through Solaris’ MaterialX system, making them usable within the Stage environment without additional setup. For larger projects, the Stage Manager node ties into the Cargo Asset Catalog, letting technical directors place and manage hundreds of assets procedurally inside the scene graph. For artists working in layout, the workflow is as simple as dragging and dropping assets into Solaris.

The importer works on both Windows and macOS. This marks the first time that Houdini users on macOS have had access to Cargo integration.

Other DCC integrations

Cargo 2.0 does not limit itself to Houdini. The application connects to a broad set of DCC hosts, including Autodesk 3ds Max, Blender, Maxon Cinema 4D, Autodesk Maya, Unity, and Unreal Engine. Version support starts with 3ds Max 2021, Blender 3.0, Cinema 4D 2023, Maya 2020, Unity 2021.3, and Unreal Engine 5.2. By centring its pipeline on USD, Cargo ensures a consistent workflow across platforms, while each DCC importer follows the conventions of its host application.

Free versus paid: what you actually get

Cargo remains free to download. With a Basic account, users can access all of the kits they have previously purchased as well as the newly expanded library of 364 sample assets. This is the only no-cost option, and it is explicitly limited to personal use.

Professional users face two subscription tiers. An individual licence costs $995 per year and grants access to the complete KitBash3D library of over 20,000 assets. A business licence costs $3,995 annually and is intended for studios requiring full access along with extended commercial rights. Both tiers include ongoing updates to the asset library as new kits are released.

Asset formats and pipeline alignment

All content in Cargo 2.0 is distributed in USD, accompanied by textures in either PNG or JPG format at resolutions of up to 4K. This decision to standardise around USD is consistent with how the industry is moving and directly benefits Houdini’s Solaris integration. By aligning its pipeline with USD, KitBash3D ensures that its content behaves predictably in other USD-based contexts such as Unreal Engine.

The generation of persistent thumbnails on import is a practical detail that benefits daily use. Assets can be previewed inside Houdini’s catalogues without the need to reload them. For larger studios, this feature saves significant time during layout when hundreds of assets may be in use simultaneously.

Workflow demonstration

KitBash3D has released a video walkthrough showing Cargo 2.0 in action with Houdini 21. The demonstration begins with importing a model, which automatically generates a thumbnail for Solaris’ Asset Catalog. Materials are imported in the same way, appearing within a persistent catalogue that remains available for future sessions.

Within Solaris, artists can either drag and drop assets into the Stage or make use of the Stage Manager node for larger setups. The video also shows how materials can be accessed through Solaris’ Material Linker, enabling them to be applied quickly to geometry in the scene. The goal of the redesign is clear: provide a simple workflow for generalists while supporting technical directors with procedural control at scale.

System requirements

Cargo 2.0 runs on Windows 10 or newer and on macOS 11.0 or newer. Plugins are available for all supported DCC hosts mentioned earlier. KitBash3D does not provide specific hardware requirements, but real-world performance will depend heavily on the host DCC and the size of the assets being loaded, particularly when working with USD datasets at scale.

What it means in practice

For independent artists and students, Cargo 2.0’s primary draw is the free library. The 364 included assets provide enough variety to build test scenes, practice workflows, and assemble portfolios. The new Solaris importer is especially relevant to Houdini users, since it finally closes the gap between KitBash3D’s content and a USD-native pipeline.

For studios, the decision is more financial. The $3,995 business licence gives access to the full catalogue, but the value depends on how heavily a team relies on KitBash3D assets in production. For layout-heavy pipelines, or for studios that regularly need large-scale architectural assets, the cost is justifiable. For occasional use, it may not be.

Test before production

KitBash3D claims that Cargo 2.0 improves both stability and pipeline alignment. These claims have not been independently verified at press time. As with any new tool, teams should test Cargo 2.0 carefully in their own production conditions before relying on it. This includes validating asset import behaviour, thumbnail persistence, and compatibility with existing USD workflows.

The post KitBash3D Cargo 2.0 lands with Houdini Solaris importer and 350 free assets first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

We first take a close look at the new functions and then test various workflows in general. As a special treat we have an interview with Simon Hall from Blackmagic Design about the development of Fusion – which you can read very soon. Stay tuned! But now, let’s start up Fusion and see what’s what.

Native support for Cryptomatte

Or the “compositor’s lifesaver” – with a cryptomatte, complex masks can be created quickly and easily from all objects or materials present in a 3D scene. The only prerequisite for this is that Cryptomattes are included when the 3D scene is rendered. Manual object selection or ID assignment is not necessary.

The Cryptonode itself presents these masks as extremely colourful surfaces that can be selected with a simple click and converted into an alpha channel. The mattes can be combined as required and removed again from a simple list view. Complex adjustments such as the colour grading of objects in the blur can be implemented quickly with cryptomattes, although they can also reach their limits here (we will look at a workaround for this special case later in the chapter on multilayers).

USD & 3D compositing

Let’s stick with this example. Suppose we want to make the light a little more dramatic or add particle FX or text in the room or or or or … Here, in addition to the possibility of masking things to infinity, the fantastic (real) 3D space of Fusion comes into play, which can be fed with all kinds of data from FBX to USD. Let’s take a look at the updated USD workflow.

The USD file generated by Houdini Solaris is simply dragged and dropped into Fusion and is then loaded and ready for use. Incidentally, the 3D space opens automatically as soon as a 3D object is to be displayed on one of the viewers (shortcut “1” or “2”).

To make the rear lion’s head a little brighter, we can now add a USD light and illuminate the head as desired. As we are working with real 3D data, the light is modulated correctly, which is a huge advantage over working with conventional masks. To avoid potentially disturbing influences on other objects, these are faded out using uVisibility. A newly added 3D layer acts as a light blocker to allow the light to flow gently downwards. Finally, this black and white image generated by a uRender Node is added directly over our original rendering – or better, used as a mask for a colour corrector.

3D text can be added in a similarly simple way, and parts of Fusion’s proprietary 3D system can be integrated into the USD Scene – as is the case with a Text3D Node. Particularly nice: If a Z-channel is also output via uRender, Fusion can perform a so-called depth merge, in which the merge node automatically “masks” the objects in the correct order using the Z-channel.

To round off the trip, we export the whole fun as USD and load the file back into Houdini as a sublayer and can access the new light and the Lightblocker here.

What we would like to see in a future update: A USD stage manager and more Hydra delegates aka render engines that support Fusion.

An alternative to relighting via 3D is the relatively new relight node, which uses a rendered or calculated normal map. This is practical if you don’t have a 3D scene to hand and can do without precision.

(Real)Deep Compositing

Deep compositing is a brand-new feature in Fusion for intervening deeply in the image – and completely without 3D. Here, the pixels are also given depth values during rendering so that Fusion now knows where these pixels are located in 3D space.
The decisive advantages are mask- and Z-channel-free merging of objects and the creation of real depth position-based masks (the above-mentioned depth merge accesses a Z-channel, a 2D representation of the depth in space), which, in contrast to the volume mask (which accesses the world position), are very precise and virtually free of edge problems. Volumes such as smoke and explosions can also be handled wonderfully, as objects can interact correctly with volumes. The new freedom comes at the price of larger data volumes and necessarily a render engine that supports deep data (e.g. Karma, Vray, Arnold, Octane, Renderman and Redshift).

But right from the start – how do we even know that we are dealing with deep rendering? Fusion writes “deep” + colour depth after the resolution in the viewer and shows a cheerful “Z” in the channel selection (not multilayer selection).

The new node “DeeptoPoints” then shows the whole truth – as a point cloud. We do not see “haptic” 3D objects, but the distribution of individual image pixels in space.

Let’s assume we now want to mount a fireball behind the lion heads. In “normal” compositing, volumes (explosions, smoke …) are a guarantee for alpha channel problems – not so in deep compositing.

Above: The delivered explosive DeepEXR rendering (via Karma) and the Deep2Points view – the explosion has an actual volume of points, which will be very useful to us in a moment. The two deep renderings are merged using dMerge Node – and automatically know which elements should be in the foreground thanks to the 3D depth information they contain.

The fireball can even be moved in depth using dTransform and is automatically covered by the corresponding objects – or even partially covers other elements.

To bring new 2D elements into the deep space, there is the Image2Deep node, which is attached behind all possible 2D nodes such as graphics, footage and renderings. The result is then available in the deepcomp, but of course remains flat itself.
For example, texts can be perfectly integrated into the fireball. Partially concealed, without a mask and the resulting alpha problems.

The final DeepNode is called Deep2Image and brings the deepcomp into the classic 2D space for further processing or output. We have the fireball, but the right reflections are still missing. Let’s take a look at the brand new EXR multilayer workflow.

EXR Multilayer Workflow

For the greatest possible flexibility in compositing CGI renderings, other helpful render layers such as masks, reflections, depth, separate lights and world position are added alongside the actual beauty pass (“the image”), which then allow a number of far-reaching adjustments to be made in compositing.
For reasons of clarity and working speed, these passes, which can be imagined as Photoshop layers, are not rendered separately as individual file sequences, but in a multilayer ERX sequence. This is then split up in compositing – which was also possible in principle in the past, but was very cumbersome.

For Fusion 20, Blackmagic has revised the entire AOV / multilayer system and created a very fast workflow. The first major innovation is the layer dropdown in the viewer, which can be used to view all the layers contained in the EXR or PSD (shortcut: pageUp/Down) – to simplify things, we are using a rendering here that already has the fireball integrated.

At first glance, there does not appear to be an equivalent to Nuke’s shuffle node for extracting the AOVs. However, to get to the individual layers, we can simply use … any node. For the sake of clarity, we use the ChannelBool node, which can generally be used to swap image channels.
(Update with Beta 4: Blackmagic added a Node called Swizzler which acts more like the shuffle node.)

Below on the left viewer we have only extracted the effects of the AOV rimlight on the reflections (LPE rendered from Karma) using Setting > Backgroundlayer and then made them brighter using a ColourCorrector.

In order to return these to the actual image, we must first remove the rimlight present in the beauty pass, otherwise it will be calculated twice. To do this, we can use the newer Multimerge Node, which allows us to process different layers with different mathematical operations. The layer called “Difference” removes the original rimlight, while the “Add Rim” Layer adds the new processed light using Alphagain = 0 (which is the same as the Nuke plus operation).

Caution: The title “Layerlist” only refers to the sequence in the merge node, not to the EXR layers/AOVs themselves.

As the nodes can access the AOVs directly, nothing needs to be extracted for simpler operations such as a Hueshift. The colour corrector can access the layer directly, in this case the emission pass. The rest happens as usual, a merge removes the previous emission pass, a second merge adds the new, blue-coloured pass.

Further application examples: The books on the left are too shiny? Simply subtract the reflection layer (limited to the books by crypto)!

To give only the explosion a glow, the “DirectEmission” pass can be selected directly in the X-Glow Node as an area mask. Last but not least, we add a camera blur using fresh air Depth of Field. Conveniently, the depth map can also be read directly from the stream here.

By the way, if you want to add new layers to the flow, you can do this with the LayerMux node. LayerRegex allows layers to be removed or renamed. The new workflow not only supports EXR, but also Photoshop layers.

What about ML?

Blackmagic has always been well positioned when it comes to machine learning tools. First and foremost the extremely practical Magic Mask, which can significantly speed up rotoscoping tasks. Version 2.0 is already integrated in Resolve 20, while Fusion still has to make do with version 1.0 in the current beta.

In the Magic Mask Node, lines are simply drawn on a reference frame over the objects to be masked and then tracked. The mask itself can be refined or blurred using the “Matte” tab. As the whole operation is quite computationally intensive, the result is best cached (by right-clicking on the node).

To whet your appetite, let’s take a look at the new version, which has been simplified and improved in terms of precision. With our woolly friend, 2 clicks instead of strokes (the sun collector is precisely recognised as a separate object) are enough to create the mask. After tracking, a temporally stable mask is ready for use.

Intellitracker

Another well-functioning machine-learning tool is the Intellitracker, which copes well with even the most jagged movements such as that of this flower in the wind – as can be seen from the movement path aka the green wild line. The Intellitracker is the new default tracker and is automatically selected as soon as the tracking node is called up.

It is usually not necessary to do more than move the tracker to the desired area and press “Track Forward then Reverse”. The tracker automatically selects the most appropriate colour channel, in this case the red channel (see bar chart below the tracker list). In this case, the text was not attached directly to the tracker. A downstream transform node, whose coordinates are linked to the tracker position, offers the flexibility to position the text anywhere in the image. The tracking path can be adjusted directly in the viewport frame by frame like a normal spline or in the Spline(Curve) Editor.

Let’s continue tracking, even without ML tools – with the Surface Tracker. This practical node is able to track intrinsically deforming objects such as clothing, newspapers or flower petals in the wind with a kind of fine grid and transfer the movement of the individual points to any graphics or text so that they follow the complex deformation. In this example, the text was only positioned on a reference frame using classic gridwarp; all other deformations are handled by the surface tracker.

For the sake of completeness, the planar tracker should also be mentioned – neither new nor ML, but tried and tested and easy to use: draw a spline around the area to be tracked, set the operation to e.g. Cornerpin, adjust to the area and define the new insert as the tracker foreground.

Multitext

One node to … surprise them all with beautiful typography. You can think of this innovation a bit like any number of classic text layers, with all the trimmings: transparencies, transitions, extensive typographical settings such as (manual) kerning, modifiers (more on this in a few staggered lines). This was also possible in the past, but a separate node was required for each text element. However, the dynamic frame and circle text familiar from DTP has never been available.

To quickly create procedural animations, you can of course write expressions (more on this later) and link parameters, but you can also add a modifier to the respective parameters by right-clicking and thus quickly create procedural effects such as random movement (wiggle sends its regards).

The modifiers are not just limited to the text node, but can be applied to almost all parameters in almost all nodes (and also linked to each other). For example, a master random modifier can control the opacity of different merge nodes at the same time.

The modifier “Follower”, responsible for “character-by-character” animation, is exciting for moving typographers. This allows you to animate letter by letter in opacity, colour, size, etc. – not only in 2D, but also in 3D, as Fusion has an extensive 3D text node, including bevel and extrude.

Shape Tools

Primarily intended for motion graphics, the Shape Tools are characterised by a vector-like workflow. In contrast to the other 2D systems from Fusion, they are basically resolution-independent and are only cast in pixels using a shape render node.

With the shape tools, various basic shapes and paths can be drawn, combined, duplicated, created as a grid and, of course, animated. Linking individual parameters with the above-mentioned modifiers offers great possibilities. The jitter node ensures random movements. For even more control (or chaos), the shape can be instantiated directly on a particle system.

Expressions

Many motion (and VFX) tasks can be significantly accelerated or automated with simple expressions. To access the expression editor, simply right-click on the relevant parameter field > Expression. For example, as the simplest of all possibilities, values can be changed by the pure passage of time(value “Time”) or linked and nested in complex ways. Parameters can be linked interactively using the small “+” icon.

You can find more examples here:
https://www.steakunderwater.com/VFXPedia/96.0.243.189/index4aa9.html?title=Simple_Expressions

Of masks and multipoly

The aim of the various ways of creating a mask is always the same – to create an alpha channel. Fusion is quite flexible in its use of masks, which are created using rectangles, ellipses, polygon splines or paint nodes. The individual masks can be easily combined, animated and attached to trackers. Individual mask points (if created by path) can be “published” and the parameters of other nodes can be linked to them. The bitmap node converts individual colour channels or the luminance of footage or graphics into masks (more precisely: into an alpha channel). Thanks to the new layer system, AOVs can now also be selected directly as masks here. Thanks to the node system, a mask can be reused or instantiated (copy>shift-v) as often as required.

A few examples:

Above: A simple vignette with ellipse mask node and strongly blurred mask edge aka softedge. In the right viewer the alpha channel of the mask.

Complex shapes are possible by linking individual mask nodes. Alternatively, the newer Multipoly tool can also be used for this, although this is limited to polygon and BSpline masks.

Quick and easy thanks to the new layer system: the blue channel of the AOV glossy transimission as a mask for a colour corrector. Connect the footage loader to the ColorCorrectNode as an input AND as a mask (blue input), set the effect mask layer to the desired AOV under Settings and select a channel under Channel if necessary.

A simple polygon mask in “DoublePoly” mode. The outer outline defines a soft edge gradient, which can be set in addition to the global “soft edge”.

Timesaver: The Multiframe option allows you to change mask points for all keyframes simultaneously – similar to Mocha’s Überkey.

Masks can of course also be drawn beautifully and even support graphic tablet pen pressure …

… and brushes such as this useful fish (available as a preset).

To track a mask, the mask centre can be linked to a tracker modifier. The actual mask path can then still be adjusted or even animated, as only the centre position of the node is actually attached to the tracker.

Particles

Fusion comes with a very powerful and intuitive native particle system. The setup is very simple: The basis for every ParticleFX is the pEmitter Node. As a starting point, it can assume various basic shapes, use 3D shapes (see text example above) or an image input (see crypto example above) and the pRenderNode, which displays our particle system either in 3D space or as 2D pixels.

The particles created in this way can now be subjected to various forces, e.g. the extremely popular turbulence. The effect strength can be set using a 3D mask (region), probability, particle groups or particle age.

Although the particles are not really simulated in comparison to Houdini, they can mimic many effects such as gravity and bouncing of objects

One of the most powerful nodes is the “replicate3D”, which can instantiate any 3D objects on the points and vary their size, rotation and position randomly.

ACES 2.0

Fusion 20 now supports ACES 2.0 & OCIO 2.4.2. Let’s take a look at what this looks like in practice.

The loaded rendering was created in ACEScg, which can be seen in the metadata (hotkey “V”, right-click and display metadata). The display is too dark without display transform.

The small raster icon (1) leads to the Display LUT/Transform menu. Here we select ACES Transform (2) and edit (3) the input & output transform (4) depending on the pipeline, here ACEScg in, sRGB Gamma 2.2 out.

Now we see the image correctly displayed in the viewers (but only displayed, the image itself is not sRGB!) and can continue to perform all operations in ACEScg.
For the final output as e.g. ProRes 4444, however, we have to apply these values via ACES Transform Node.

If you would like to work with AGX / Filmic and co, proceed as follows: Again via the ViewLut menu (1), this time select OCIO Display (2) and edit with the following settings (4). The conversion for the final output is carried out this time via the OCIO Colourspace or Ocio Display (!) node, with the same values as in the ViewLut. The necessary config comes this time from: https://github.com/Joegenco/PixelManager

So much for the application in Fusion. If you want to read more about ACES or argue about it, you can do the former here: https: //chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces

Vector Warp

The new vector tools are based on analysing the movement of the image pixels. Fusion knows what happens to which pixel and can therefore apply complex deformations or retouching quickly and usefully. Areas of application include digital make-up or the insertion of new objects.

The basic prerequisite is motion vectors, which can be supplied externally or generated via an optical flow node (cache without any need!).

To simply place new objects on the background, the new VectorWarp node in “Generate Warp Map” mode is sufficient. The deformed result is placed over the background again using the Merge Node.

For more complex retouching, the VectorWarp node can be set to “Unwarp” and “freezes” the object in time. In this way, objects can be retouched or new ones added using the Paint Node. The result then flows into a 2nd Vector Warp Node, which brings the image back into motion using “Generate Warp Map”.

Curve Warp

The warper previously only available in Fusion Reoslve can now also be controlled using curves. Simply draw a line or an outline, set limits if necessary and bring the object into the desired shape.

Node versioning

A very small and extremely practical function is the somewhat hidden versioning of a node. Up to 6 different settings can be saved to quickly try out different looks. These are not presets, but can be created as such by right-clicking on the node name and Save Settings.

Performance optimisation

Fusion offers various optimisation options to keep performance high despite complex effects and comps:

1. The render area selection (region of interest) limits the calculation to a selectable part of the image
2. Proxy mode reduces the preview resolution (click on the PRX button on the right for further options)
3. High Quality Preview and Motionblur can be switched off for faster previews
4. Framestep skips every frame and leads to faster previews (right click on the play icon for more options)
5. Cache to disc renders and saves the flow up to the selected node (right-click on the desired node)

Reactor

Reactor, which can be downloaded free of charge from the unofficial official Fusion forum, is the counterpart to Nukepedia and lets you install all kinds of macros, scripts and fuses, also commonly known as user-created plug-ins, directly from within Fusion. From exponential glows, edge blur and complete mograph solutions (Krokodove!), everything is included – including the Nuke2Fusion project, which bases shortcuts and settings on Nuke as far as possible.

Installation and instructions: https://www.steakunderwater.com/wesuckless/viewtopic.php?t=2159

Top nodes to try:
X-Glow for wonderful exponential glow
FTL tools for modular lens flares
Krokodove adds many motion graphics nodes to Fusion
OIDN denoiser to be able to use the Intel Open Image Denoiser directly in Fusion.

Last news but not least news: Fusion inside Resolve only: The option you have been waiting for since the integration in Resolve: You can now display the grading applied in the colour page in Fusion and set the start frame count independently of the footage.

Fusion Resolve (Studio) integrated vs. Fusion Studio Standalone

A quick look at the possible versions and versions of Fusion – the standalone is only (still) available as Studio and therefore costs just €355. However, for that money you not only get Fusion, but also Resolve Studio. Or vice versa.
The free Resolve version has Fusion integrated, but has to do without a few really practical Studio OpenFX such as Lens Blur, Termporal Denoise and the new Neural Engine FX such as Magic Mask II. For this reason, the Studio version is highly recommended, especially because it is a perpetual licence. No subscription. For Resolve Fusion. As you can see, it’s worth it.

If you don’t need the other Resolve tools for your current task, it’s better to use the standalone version for performance reasons – it’s simply faster and more flexible as it doesn’t have the Resolve overhead and also offers network rendering (with unlimited render clients). By the way: Before Blackmagic times Fusion alone cost around 2500 $ …

Conclusion

Fusion offers a powerful complete package for compositing / visual effects and also a lot of core power for motion graphics, if you can get involved with the NodeSystem and do without direct integration of Adobe Illustrator files. Working with the programme is fun and quick. The price of the programme is unbeatable, and Resolve Free is even free – just give it a try.

The beta is available immediately and can be downloaded from the Blackmagic website. A Resolve or Fusion dongle or key is required for operation. This is available as a one-off purchase for 355€ – as a perpetual licence.

The post Fusion 20: a deep look at the core first appeared on DIGITAL PRODUCTION and was written by Manuel Kotulla.