For those who don’t know the tool: Blender uses Blender Cycles for path-traced rendering, and viewport denoising helps lookdev stay interactive while lighting and materials evolve.

The news, minus the confetti

NVIDIA says Blender Cycles will integrate DLSS 4.5 Ray Reconstruction as a new denoiser and ship it with Blender 5.3 in the fall. The goal is a more interactive viewport while keeping a “near-final” look in real time.

DLSS Ray Reconstruction targets ray-traced and path-traced content and replaces traditional hand-tuned denoisers with an AI model that reconstructs pixels in noisy areas where rays were not sampled. It also unifies denoising and Super Resolution into a single model that uses temporal and spatial engine data to rebuild higher fidelity images. Usually, that is for games – you need all the pixels and all the fidelities for veggie-mode in Microsoft Flight Simulator (Don’t Judge, the Dune expansion is great!) Here is a list of all Games that have that, and in that list, you can even spot Redshift, Marmoset and Keyshot. Strange calling those “Games”, but who hasn’t lost to a renderer?

The same announcement says DLSS 4.5 Ray Reconstruction arrives in August for games, and it is also coming to Blender 5.3 in the fall. That timeline matters for anyone planning tool rollouts around seasonal show crunch. Prep first,so you don’t have a bad surprise up ahead.

What changes inside Cycles

Cycles already has an integration path via NVIDIA OptiX. The new piece is DLSS 4.5 Ray Reconstruction as another denoiser option, layered on top of the existing OptiX integration.

If you spend your days in a path-traced viewport, denoising is not a luxury feature. It is the thing that keeps lighting decisions moving. A denoiser that keeps interaction up while pushing the look closer to final could reduce the familiar loop of tweak, wait, squint, tweak again. This sits squarely in the Blender Cycles ecosystem: you still light and shade the same way, you still render the same way, but the viewport becomes less of a tax on iteration.

The longer arc from hacks to shipping builds

Back in February 2026, Blender artist Blake Propst tested a Blender 5.1 build with DLSS on an RTX 3090, with reports of numerous bugs and visual issues. A patch also existed that added an option to use DLSS Ray Reconstruction for viewport denoising in Cycles, and users were encouraged to test Blender 5.1 beta and report issues toward a stable release.

Blender With DLSS!
byu/bbcool2002 inblender

That earlier phase sounded like classic early integration energy: exciting demos, messy edges, lots of caveats, and a very human amount of duct tape. It did prove one thing, though: artists wanted it badly enough to put up with rough builds, because interactive path tracing is still a wrok in progress on most desks. Now the situation shifts from experiments to a shipping target in Blender 5.3.

What DLSS 4.5 Ray Reconstruction claims it does

DLSS 4.5 Ray Reconstruction uses a second generation transformer model. It is improving image quality in ray-traced and path-traced content, and the announcement lists changes such as higher compute capability, more parameters processed while maintaining similar performance to the previous model, better temporal stability, and clearer motion in ray-traced and path-traced scenes. For artists, the practical question is not whether the model sounds clever. The practical question is whether it behaves well under production pressure: animated textures, fast camera moves, thin geometry, alpha heavy foliage, refractive messes, and the kind of lookdev that loves to change one variable per second.

Viewport denoising is where time disappears

A big chunk of render pain is not final frames. It is the time you spend waiting for a viewport to become readable enough to make the next decision. A clean enough image lets you judge lighting ratios, contact shadow behavior, glossy breakup, and whether your material values drift into plastic. A noisy image forces you to wait, or worse, to guess.

The boring parts you still need to know

Pricing is not specified in the sources – propably will be part of drivers or blender itself, so should be free. Read the T&C before downloading, though.

Hardware requirements are not spelt out for Blender beyond the general statement that DLSS Ray Reconstruction works on all GeForce RTX GPUs. The Blender sources mention testing on an RTX 3090 and as part of an RTX focused stack, but they do not provide minimum GPU or driver versions for the Blender 5.3 integration. We’ll see.

https://www.nvidia.com/en-us/geforce/news/computex-2026-nvidia-geforce-rtx-announcements/

The post NVIDIA brings DLSS denoising to Blender 5.3 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

In this video, we are taking a look at the ongoing effort of the Otoy team to modernise the Cinema 4D Plugin with “quality of life” improvement, as well as newly added features such as the “Material Link”. If you are an Octane C4D user, don’t miss out on this video. I bet you find one or more useful things in there!

CHAPTERS

00:00 Intro
00:32 Tut Overview
01:24 C4D Octane Material Link
03:03 C4D Octane UI Improvements
03:19 C4D Octane Scene / Plugin Settings
03:48 C4D Octane Imager UI
04:12 C4D Octane Rest Position Tag Improvements
04:18 C4D Octane Null Material Improvements
04:40 C4D Octane Nodes Selection Improvements
04:49 C4D Octane Round Edge / Mat Layer ON
05:18 C4D Octane Live Viewer Color Rollout
05:36 C4D Octane Live Viewer Scaling
05:51 C4D Octane Improved Node Previews
06:11 C4D Octane Node Color4 options
06:32 C4D Octane Attribute Node String
07:19 C4D Octane Clamp Edge Displacement
07:47 C4D Octane C4D OCIO support!
09:41 Conclusion
10:23 Patreon Thanks

Download the Tut Scene by becoming a Patreon member. No matter which tier!

VIDEO RELATED LINKS:
Maxon’s Official Website: https://www.maxon.net/
Octane C4D Otoy Official Website: https://render.otoy.com/forum/viewfor…

---

If you’ve ever wondered what happens when a VFX artist spends too much time obsessing over pixels and lighting, well, welcome to my world! You can find all my latest experiments, tutorials, and general nerdy shenanigans here:

Website: silverwing-vfx.de
Patreon: patreon.com/SilverwingVFX (Get scenefiles for all of my tutorial scenes also while supporting me)
Instagram: instagram.com/silverwingvfx (Finished 3D projects and engagement with the community)
YouTube: youtube.com/@SilverwingVFX (Updates and news about my work and what I am up to)

And if you’re into retro gaming and deep-dive nostalgia, check out the big article I wrote for this magazine: my love letter to the legendary Game Boy. Because nothing says “true love” like an 8-bit screen and a battery life that could outlast modern smartphones.

The post C4D Octane: 1.9.x Update Features Video first appeared on DIGITAL PRODUCTION and was written by Raphael Rau.

For those who don’t know the tool: Massive is a standalone crowd simulation app for building agent scenes, with Arnold rendering, and ties into wider Maya and USD pipelines via the commercial line.

Free, but not aimless

A free edition of Massive Crowd Sim is available for non-commercial use. The core promise is simple: crowd simulation with no limits on agent capabilities, and no limits on the number or complexity of agents in a scene. That makes it a legit learning build, not a teaser that stops when you finally get a crowd moving without looking like a synchronized swimming team. The catch sits where you would expect it: renders are watermarked, and the supported renderers list stays short at the moment, with Arnold plus the built-in Velocity renderer listed as supported.

What you actually get day one

The free edition ships with a complete set of video tutorials and a stack of demo scenes. The demos cover a wide range of setups, including quadrupeds, insects, rigid body dynamics, flying, and shooting. That mix matters, because crowd work rarely stays politely bipedal for long, except Military Propaganda Goosestepping, but the studios doing that don’t need free software and have ALL the budget.

Installation is refreshingly old-school

Setup reads like a throwback in a good way. Download the installer, unzip or untar, and run it. On Windows, you run the installer. On Linux, you drop the bin directory into /usr/local/massive/. The manual can be unzipped wherever you want.

After that, the only required step is to activate the license. Optional environment variables exist, with details documented in the manual. If your pipeline team loves containers, reproducible installs, and predictable paths, this is the rare vendor workflow that does not try to reinvent software deployment. The free edition still expects you to behave like a grown-up about where binaries live, especially on Linux.

Licensing: one machine, one account, bring patience

The first launch triggers a license activation window. You enter the same username and password you use for the Massive 101 forum login. If activation succeeds, the license file lands in the .massive directory in your home directory, then the app starts. After that first activation, the app starts immediately as long as the license remains valid.

There is also a hard limit: only one active license is allowed per account, and a six month delay applies before a new license can be issued. That detail matters for lab setups, shared training workstations, and anyone who reformats their OS the way some people change socks. Not judging, just sayin’.

This is also where a free edition stops being magic and becomes process. If you plan to teach a class or run a studio workshop, design around the one active license rule early, not five minutes before teh first session.

Support: community-first, by design

Because the edition is free and limited to non-commercial use, there is no formal support provided. Instead, the Massive 101 forum exists as the help channel, where users can share tips, ideas, and problem solving.

The forum post also says the team will keep an eye on it, and there might be some input from them. If you are used to commercial support tickets with response time targets, this is not that. If you are used to production artists helping other production artists with practical workarounds, this looks familiar, for better or worse.

Export and pipeline limits you should treat carefully

Massive 101 is almost completely fully functional, with the full simulation toolset and no limits on the number or complexity of agents. It also has specific pipeline restrictions, including that motion, cloth, and hair simulation files save in a Massive 101 file format that cannot be used in Massive Prime, plus that USD and geometry export are disabled.

That incompatibility for Massive 101 and the big one is that there isn’t a row of “Assistant stations” for setup, and only one license for the big Massive to bring it all together.

Those details are important if your goal is anything beyond learning and internal tests. Watermarked renders are an obvious non-starter for client finals, but disabled export can be a more subtle trap if you assume you can “just move it into the rest of the pipeline later”. If your studio pipeline leans on USD interchange, treat this as a training build unless you can independently confirm the exact export behavior in your own testing.

Compatibility and pricing, as stated

Compatibility is Windows 10 and Linux, and free for non-commercial use. For commercial pricing, a perpetual floating license of Massive Prime is at $3500, with rental at $2500 per year, and says Massive Prime includes Massive for Maya.

Where this fits with your current crowd toolbox

If you already live inside the Crowdsim-world, this release sits in a useful niche: training, R and D, seeing if Massive fits your needs, personal skill building, and previs-scale experiments where you want to learn behavior authoring without immediately paying for seats.

For teams already hooked on Maya, the commercial ecosystem includes a Maya-integrated edition, and the broader stack talks about rendering integration and pipeline hooks across supported renderers. That larger ecosystem matters, but the free edition itself focuses on learning and local runs, not studio deployment. Also, Maya, by now, has Golaem built in.

https://www.massivesoftware.com/massive101.html

https://www.massivesoftware.com/massive101/forum/viewtopic.php?t=2

The post Massive Crowd Sim gets a free 101-edition first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

VOXIFY voxelizes meshes while aiming to preserve color and other material maps such as roughness and metallic. The workflow captures UVs, then creates attributes so the voxel result can pull data from the original textures. If you want a drinking game: Take a shot every time we write the word Voxel, and consider your current life choices, when you play drinking games at 8AM in the morning on a Monday, when this news comes out.

The tool targets stylised voxel art renders, LEGO-style renders, game environments, and abstract motion graphics. It also calls itself non-destructive, meaning the setup stays editable as a modifier rather than forcing an immediate apply.

Material support comes with a big practical caveat. The modifier cannot work with simple colour materials or multi-material objects unless you first bake all materials and colours into a single texture, then use that texture for colour transfer. The same rule applies to other maps. VOXIFY works well with 3D-scanned assets, where the look already lives in texture maps.

Import, scale, then touch the voxel size slider

VOXIFY loads into a scene through Blender’s append workflow. You append a VOXIFY collection from the downloaded file, which loads an empty mesh with the Geometry Nodes modifier. Duplicate that empty mesh per asset, then place the duplicate into the working collection for that shot.

Before you voxelize anything, two basics: apply transforms and keep object scale sensible. Applying scale uses the standard apply transform workflow and voxel size behaves like a real world control, so a tiny prop and a skyscraper should not share the same voxel size value. A very large object expects a larger voxel size value, otherwise performance and results fall apart.

Once the base setup behaves, voxel size becomes the main artistic lever. Smaller values create denser voxels. Larger values create chunkier results. That is where VOXIFY tries to feel like a production-friendly knob instead of a one-click filter.

Viewport choices and custom instances

VOXIFY includes controls for how the result displays in the viewport versus final render, switching the viewport representation to a point cloud for optimization, while keeping a voxel look for render. The modifier also supports custom voxel shapes. Instead of instancing cubes, you can instance a user supplied object as the voxel unit. Transparent areas get special handling. The setup includes masking transparent parts by enabling a mask with texture option and feeding an opacity map, so voxels do not fill areas that would never render.

Pruning, carving, and not paying for invisible cubes

Voxelization loves to create internal structure you never see, and VOXIFY exposes controls to deal with that. For transparent textures, the prune and mask controls help stop voxels from spawning in cutout regions. For solid objects, there is an option to remove internal voxels, reducing geometry that would sit inside the mesh and never contribute to the image. That internal removal matters both for render performance and for downstream conversion to a static mesh.

VOXIFY also brings pruning – carving out a more accurate outer shape. The prune section offers two carving methods: raycast and distance. Raycast is more accurate, while distance can help keep more vxoels where you need them. Tolerance controls how aggressively that carving behaves, and it often starts near the same value as voxel size.

Static mesh output, plus the part where topology bites back

VOXIFY includes a generate static mesh option, because internal volume matters here: without volume, the generated static mesh can end up with an unwanted inner wall. Keeping internal structure can provide the volume needed so the static mesh output produces a single outer shell rather than double walls.

Even with volume, a few stray points can remain visible. The cleanup uses a mesh selection workflow to isolate and delete unwanted vertices after generation. For leafy assets like a fern or a tree canopy, the volume approach can introduce unwanted voxels under thin surfaces. A distance tolerance control helps define how much thickness to assume, using a value that matches the thickest meaningful part of the object, such as a trunk when talking about trees (or strangely morphed elephants). Just give the algorithm enough thickness to produce a clean mesh while avoiding filling every thin sheet with junk geometry.

Fixed animation options for rigs and deformers

VOXIFY includes a fixed animation feature designed to avoid revoxelizing the mesh every frame. There is a contrast on an animated object: one mode voxelizes each frame, tracking the deforming shape. Fixed animation instead holds the shape of each voxel as it was first generated, while following the animation. There is a limitation when the animated object expands compared to the source mesh used for voxelization, which can produce gaps between cubes. A static mesh generation option can help close that visual gap, but at the cost of changing the nature of the result.

Fixed animation is especially suitable for animated characters, where deformation usually does not involve large expansion or compression. In practice, that makes it a tool for rigs where you want temporal stability, fewer recalculations, and less flicker from per-frame resampling.

Assembly animation, because everything must explode nicely now

VOXIFY includes assembly animation controls that animate voxels from a starting state into place. An animation factor control with keyframing it from 0 at the start frame to 1 at the end frame. It also flags a practical performance issue: changing the assembly value can be slow because the node graph recomputes upstream operations.

To speed that up, the tutorial demonstrates baking parts of the setup once you stop changing voxelization parameters like voxel size and maps. The idea is to freeze the heavy part of the graph so assembly animation updates closer to real time during iteration.

The assembly system includes a speed scale control that changes how fast each voxel moves from start to destination, affecting how much motion blur you might get. It also includes randomization options to avoid a layer by layer build, plus a distribution control that projects the assembled object onto a disc and uses radius and location to change where assembly starts.

Included is a progressive assembly option that tries to assemble the connected structure first, such as building the trunk before floating branches, or whatever the morphed elephant is made of. It has settings like iterations and selection controls, and the tutorial demonstrates debugging by inspecting selection masks in the viewport using standard node debugging interaction.

All of this remains a reminder that a modifier can feel like magic, until a shot needs determinism. Treat VOXIFY like any new procedural tool: test it on throwaway scenes and verify output stability before you use it in production.

Versions, requirements, storefront reality

VOXIFY requires Blender 5.1 or higher. Superhive has three tiers: Personal Use at 8 USD, Commercial Use at 25 USD, and Studio at 49 USD. The Studio tier is “team use” for up to 5 seats. Superhive also lists render engines used as Cycles and Eevee.

https://superhivemarket.com/products/voxify–mesh-to-voxel-modifier

https://www.artstation.com/marketplace/p/o5rnD/voxify-blender-mesh-to-voxel-modifier

The post VOXIFY turns Blender Meshes to Voxels and animates first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Silhouette 2026 lands with fewer steps between “I need a clean matte” and “shot approved”, without taking the steering wheel away from artists. The release updates multiple ML-driven matting tools that can detect, segment, propagate, and refine, while still keeping the workflow artist-controlled.

The additions cluster around three pain points that never die in production: edge stability over time, tracking that survives real-world footage, and pipeline plumbing that does not explode when you scale beyond a single workstation. Silhouette 2026 touches all three, and it does it in a very node-graph way: new models, new nodes, and more data moving through the graph instead of getting stranded in side files.

AI matting that thinks in objects, not in one mask at a time

The AI toolset gets updates across five ML nodes, with a focus on scalable multi-object workflows. Face ML gets a new model plus new Nose and Neck matte options, a full-face matte option, and deeper integration with ML masking and compositing workflows. Depth Map ML gets a new model aimed at more detail and improved temporal consistency.

Mask ML adds multi-object workflow features, including object list management, foreground and background refinement tools, and per-object Cryptomatte data. Matte Assist ML adds intermediate frame caching, improved propagation performance across long shots, and multi-object Cryptomatte output. Matte Refine ML adds a new Video Matting model for improved temporal consistency along edges, and it preserves Cryptomatte data after refinement.

Be wary: running many ML masking nodes can load multiple custom models onto the GPU and fill VRAM quickly, so the multi-object approach inside a single Mask ML node matters for both speed and sanity.

If you live in the land of shallow depth of field, it is simple: keep your IDs, then soften your edges with the model that holds up over time. The Video Matting model option in Matte Refine ML is a temporal-consistency favourite in the training material.

Head Track ML and the 3D Scene node get real

Silhouette’s 3D Scene node now pushes further into 3D-aware shot work. It is powered by SynthEyes technology, and Silhouette 2026 adds a new workflow centrepiece: Head Track ML.

Head Track ML uses ML to automatically build and track a full 3D head mesh, preserving facial motion and expressions for face-aware effects. The ML model loads onto the user’s graphics card, detects the head, and then Silhouette creates and tracks an aligned and scaled 3D head mesh.

From there, the new Unwrap and Rewrap nodes connect 3D to 2D UV space for roto, paint, and beauty work, and a Render Depth node can generate depth maps from Head Track ML meshes for beauty work or downstream VFX pipelines.

The training walk-through frames the workflow as a practical alternative to the classic “stabilize a patch, paint, reapply motion, repeat until retirement” approach. The point is to unwrap the tracked head into a stable 2D space, do the detail work, then rewrap it back onto the moving performance. It even comes with a candy-wrapper analogy, because every 3D workflow deserves at least one metaphor before it hits the studio floor.

There’s limits: For example, Head Track ML does not detect relative distance between multiple heads, and suggests using an “All render” option in the Render Depth node if a depth map for all heads is still needed.

On the camera side, Refine Solve is designed to let artists improve a camera solve without reprocessing the entire solve. It supports fixing bad frames and smoothing problem areas by deleting erratic or unnecessary 3D features, aiming for more stable solves and faster cleanups.

Tracking upgrades that target the annoying bits of reality

Silhouette 2026 gives love to two tracking tasks that tend to chew time: point tracks that fall apart when anything gets in the way, and repetitive object tracks for faces and license plates.

Point Track ML updates the long-running point tracker workflow with ML assistance aimed at motion blur, occlusions, objects going off-screen, and changing reference patterns. It includes three accuracy settings and Viewer Stabilisation to validate and lock the track. This is not a guaranteed fix, but it increases the chance of success in those failure cases that always show up right before delivery.

Object Tracker detects and creates layers for object classes, including faces and license plates, to reduce setup time, and tracker types support occlusion matte input. In the tutorial flow, it can automatically generate new layers and shapes when new faces enter a shot during a forward track.

This feature that works best when you treat it like a fast first pass – the result may not be 100 per cent perfect, but perfect for fast turnaround work. You don’t get “final shapes”, but points where you can attach additional Tracking data, and modify what needs to be cleaned.

Paint tools that aim for fewer clicks and fewer regrets

Silhouette’s paint system gets new tools and workflow changes aimed at cleanup and beauty work. A new Healing Brush supports cleanup and retouching with expanded colour sampling from any input. Brush controls add blend modes and pressure-sensitive sizes. Blur, Clone, and Drag brushes get more natural and flexible behaviour. Clone workflow updates add continuous mode and auto-grade locking. Resize Paint introduces a resolution-independent workflow that allows working in a lower-resolution session, then rebuilding strokes accurately on higher-resolution media.

Resize Paint is a way to work quickly at low resolution and later rebuild exact stroke replicas at high resolution, which is basically a polite way of saying your workstation fans can stop auditioning for a jet engine while you block in cleanup.

Cryptomatte, data ports, and fewer matte files to babysit

Silhouette 2026 deepens Cryptomatte-centric workflows, and the important bit is that it treats mattes as data that should travel with the graph, not as files that should multiply in folders.

Pipeline changes include passing filtered Cryptomatte data as alpha through nodes via an Matte input, enabling objects and layers to act as matte sources. A new Cryptomatte Mixer node can combine multiple Cryptomatte streams into a single output. ML and AI tools support multi-object outputs with improved viewer-based selection tools to speed up scene isolation and matte management.

Beware the workflow trap: do not build one Mask ML and one Matte Assist ML node per object, because each node loads its own model to the GPU and VRAM fills fast. Instead, multiple objects can live inside a single Mask ML node, and Cryptomatte over the data port can move reference data to Matte Assist ML even when reference keyframes are scattered along the timeline.

For OFX plugin users, there is a limitation: Cryptomatte data cannot simply be routed to an output node and expected to appear directly in the host application, due to how OFX plugins work. The workflow is to export to the file system instead, using an Output Multi node for Cryptomatte-generating nodes.

Export details matter, too. Cryptomatte needs EXR for multi-channel properties and uses only lossless compression, and it warns against lossy formats such as DWAA, DWAB, or PXR24. That is a lot of words to say: keep your IDs clean, keep them in one sequence, and do not turn your matte export into a science project with ten folders named “final_final_3_forreal_v02”. Unless you enjoy that sort of thing. Some people collect stamps, after all.

Performance, stability, and the stuff you notice at 2 a.m.

Silhouette 2026 includes performance and playback improvements through ML node caching for several ML nodes, plus predictive playback via pre-fetching and batched render jobs. Playback controls add optimisation options, including adjustable job queue size, preload frames, and threading settings.

Daily workflow improvements include advanced node search with category, intent, and data-type filtering, a Favourites node, an improved naming system, a context-sensitive HUD, and a Safe Mode troubleshooting workflow to enhance stability in demanding environments.

This is the kind of feature that helps the person who inherits your comp at the worst possible time. If your node tree looks like it was assembled during an earthquake, you still have to deliver, so better search and safer startup modes are not flashy, but deeply production-friendly. Yes, you should still test new tools and innovations before use in production, especially when ML models and GPU caching sit in the critical path.

Pipeline automation and AI assistants, now with actual plumbing

The most pipeline-forward change is a built-in JSON-RPC server and an MCP server. The JSON-RPC server allows studios to drive Silhouette remotely, execute Python code, run script files, and control the application via JSON-RPC.

A Python Package Manager manages third-party Python packages inside a directory in Silhouette and stays isolated from the system Python. This is powerful, and it is also the kind of feature that deserves a boring rollout plan. Build guardrails, keep permissions sane, and do not let the intern’s chatbot become the new show supervisor. The intern already has enough power.

The MCP server allows direct calls from AI assistants, which can inspect projects, build node trees, edit shapes and keyframes, and render frames. “ChatGPT, explain what I did there!” is now a valid question that can be answered. Not truthfully or understandably, because … LLMs, but still.

What to watch to get productive fast

If you want a training rabbit hole, the Silhouette training and tutorial ecosystem lives in the video library and training hub on the BorisFX-site, spanning both quick tips and longer courses on all packages and levels of experience.

Pricing and availability

Silhouette is available as a standalone application and as a plugin, with subscription, upgrade, support, and permanent license options. Subscriptions start at $ 545 per year or $ 103 per month. Silhouette supports macOS, Windows, and Linux. Supported host applications include Adobe After Effects, Adobe Premiere, Foundry Nuke, Blackmagic Resolve and Fusion, and Autodesk Flame.

Customers with an active Silhouette subscription, Boris FX Suite subscription, or an active Silhouette upgrade and support plan receive the 2026.5 release directly as a update.


https://borisfx.com/products/silhouette/

The post Silhouette 2026 gets smarter roto and 3D heads first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: DaVinci Resolve is an NLE plus color grading plus compositing and audio in one app, with Fusion tools and a Studio tier called DaVinci Resolve Studio.

Resolve Stills stop skating around

Blackmagic Design pushed DaVinci Resolve 21 Public Beta 4 with a fairly specific mission: make small things stop being annoying. On the Photo page, Resolve FX behave more reliably when you transform still images. Resize or reposition a photo with an effect applied, and the overlays and on screen controls now stay aligned so you can keep adjusting instead of chasing UI handles.

The update also improves transparency handling for effects on stills, remembers effect favourites between launches, and fixes warper tool behaviour on photos for more accurate reshaping and manipulation. Also in the stills corner, Canon CR2 and CR3 highlights now render more accurately. Bright areas should keep a more natural look and no longer appear darker than expected when grading or compositing.

Fusion keyframes, meet the timeline

On the Edit and Cut pages, the keyframe editor now supports Fusion motion paths and other modifiers. That means you can tweak animation curves, motion paths, and linked parameters from Fusion titles, effects and macros right next to timeline keyframes, instead of bouncing between editors and hoping you clicked the same parameter twice. It is a fiine quality of life win for anyone who lives on the keyframe lane.

Resolve Studio AI gets a cosmetic touch up

For DaVinci Resolve Studio users, AI CineFocus has improved visual quality for shallow depth of field simulation. Better and Faster modes now handle subtle blur more cleanly, with reductions in edge shimmer, stair stepping and halos so subjects separate more naturally from backgrounds.

AI beauty tools also get refinement. The blemish removal tool allows greater precision for facial area so corrections stay focused where needed, and the face refinement tool now better supports alpha layer workflows, helping isolate and track facial adjustments with less manual masking.

Immersive and raw handling: small, useful plumbing

Beta 4 adds support for Insta360 native colorspace, plus improved DNG decode handling with color value and profile look table support for more consistent image reproduction. DaVinci Resolve 21 Public Beta 4 is available as a free download. As always, test any new beta build on a copy of a project before you let it anywhere near a real delivery.

https://www.blackmagicdesign.com

The post DaVinci Resolve 21 Public Beta 4 is out first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Levels is a free browser utility for quick grayscale map prep that can feed any DCC or engine, with code hosted on GitHub by artofpilgrim.

A small tool for the most common annoyance

Levels positions itself as a texture alpha studio in the browser. You drop in an image, dial in a black and white channel mix, adjust brightness and contrast, shape the result with a levels curve, then finish with a perspective or rectangular crop. After that, you copy to clipboard or download a PNG. This kind of workflow hits daily production reality, especially when you need a quick mask for foliage, decals, grime breakup, or anything else that starts life as a photo and ends up as a grayscale control map for shading. It also pairs neatly with a texture painting pass later, when a rough mask graduates into something worth polishing.

Channel mixing, then levels, then stop touching it

The channel mixer in Levels offers six color sliders: reds, yellows, greens, cyans, blues, and magentas. It includes presets for Default, High contrast, Dark sky, Infrared, Red filter, and Stark grunge. The goal stays simple: separate subject from background quickly, then lock in contrast.

Brightness and contrast sit as a linear legacy Photoshop pre-stage applied before Levels. The levels panel shows a histogram and gives input shadow, midtone, and highlight handles plus output black and white handles. Keyboard navigation covers Tab to focus a handle, arrow keys to nudge, and Shift plus arrow for bigger steps.

If you need to keep colour instead of converting to black and white, colour mode bypasses the conversion and applies Levels, brightness and contrast per channel. Invert sits there too, because every mask workflow eventually asks you to flip it and see if your brain calms down.

Crop tools that fix your reference photo lies

Rectangular crop supports free or locked aspect ratios: 1:1, 4:5, 5:4, 16:9, 9:16, 3:2, and 2:3. Holding Shift while dragging forces 1:1. Perspective crop lets you drag four corners of a quad to deskew a region into a rectangle. It uses bilinear sampling, includes a rule of thirds alignment grid, shows live output size, and supports 1 pixel and 10 pixel keyboard nudging. It also composes with rectangular crop, and Reset preserves the pre perspective crop.

That combination makes Levels useful beyond the obvious leaf cutout. It is a quick way to extract alhpa style grayscale sources from angled reference shots that you would otherwise fix in a heavier editor, then stash into a texture library for reuse.

Shortcuts and export that respect your time

Levels supports a real time preview. Hold Space to compare against the original image before processing, after any crop or perspective. Inputs can arrive via drag and drop, paste from clipboard, or open from disk. Exports can go straight to clipboard or to a PNG download. Exports render from the current settings even when the preview defers for responsiveness.

Shortcuts include Space for compare, I to toggle invert, Ctrl or Command plus C to copy, and Ctrl or Command plus S to download PNG. Enter and Escape apply or cancel inside crop or perspective mode. Double click resets a slider to default.

The repository also states that inputs over 4096 pixels on the long edge get downscaled with a toast notice. That limit matters if you expect full resolution scan handling, so treat it as a deliberate constraint, not a surprise feature.

Under the hood, it stays refreshingly unprecious

The GitHub repository describes a no-build step setup. It loads React 18 and ReactDOM from a CDN, and keeps the rest as plain JavaScript split into three ordered script tags.

The file layout is a index.html as shell that links CSS and the three JS files, styles.css for styles, image.js for image processing functions and presets, components.js for UI components, and app.js for the app component and DOM boot. The three JS files communicate via a window.Levels namespace with image.js populating math and data first, then components.js reading it and adding panels, then app.js rendering.

Running locally opens index.html in a modern browser, with the file protocol working for sibling script files. For touch pointer and clipboard testing, serving over HTTP using python -m http.server from the repo root is advisable

This is the part that makes it easier to keep a known good utility around. The tool does not demand a build chain just to exist, which is exactly what you want from a graysacle helper app that should still run when the rest of your stack changes.

Thomas Pilgrim Butters released Levels this week, and describes it as a simpler alternative to opening Adobe Photoshop for alpha textures, with support for alpha masks, height or roughness maps, and stylised monochrome plates from photo references. Thomas Pilgrim Butters is Lead Weapon and Prop Artist at Facepunch and an instructor at Gnomon.

https://artofpilgrim.github.io/levels/

https://github.com/artofpilgrim/levels

The post Levels cleans up alpha maps fast first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

TL;DR: Node Ninja is a free plugin from School of Motion for Maxon Cinema 4D that builds Redshift materials from PBR texture folders.

The promise: stop wiring nodes, start rendering

Node Ninja targets a very specific kind of production friction: the endless, repetitive setup work that happens between downloading a texture set and having a usable Redshift material inside Cinema 4D.

A single PBR texture set can include 6 to 12 maps per material. The manual process is requiring a TextureSampler node per map, wiring each one to the right input on an RS Standard Material, and setting roughness, metalness, and normal maps to the correct color space so they render correctly. Also: the normal map format problem: if a texture set ships with a DirectX normal instead of an OpenGL normal, the mismatch can hide until the render looks wrong.

Node Ninja estimates that the manual approach takes about 4 minutes of node wiring per material and calls itself the one-click alternative. But, let’s be honest: 4 minutes is when you are quick. School of Motion offers Node Ninja as a free download, with no credit card, on Mac and Windows.

Install once, then find it where artists actually look

Installation follows the standard Cinema 4D plugin routine: open Preferences, jump to the Preferences folder, then drop the School of Motion folder into the plugins folder and restart Cinema 4D. After a correct install, Cinema 4D shows a School of Motion entry under Extensions, with Node Ninja and a companion tool called Node Surgeon available from the same menu.

Folder in, material out

Node Ninja works by pointing it at a texture folder, then building a full Redshift node graph based on filenames. It wires maps to expected inputs and sets color spaces. The plugin recognizes common PBR map naming patterns and can auto-handle albedo, roughness, metalness, normal, displacement, AO, emission, opacity, specular, and SSS, with a longer list in the manual. It also claims to composit AO into base color using a color layer and an appropriate blending mode. On normals, it states it can detect DirectX versus OpenGL normal maps and choose the correct type for Redshift, which it describes as using OpenGL normals.

Projection choices, plus an editor for after the fact

At import time, Node Ninja asks whether to use UV projection or world space Triplanar and wires the graph accordingly. If you change your mind later, the included Node Surgeon utility can edit existing materials to switch projection modes, and it can add or remove master controls for scale, offset, and rotation without rebuilding from scratch.

On newer Cinema 4D versions, Node Ninja uses the Redshift UV Context Projection node so tiling, offset, rotation, and pivot adjustments can happen in one place and propagate upstream through the graph.

Bulk import and duplicates, handled like an adult

Node Ninja includes a bulk import mode: point it at a parent folder and it can build one material per subfolder. When it detects a name collision, it offers three options: replace the existing material, duplicate with an auto-increment name, or skip it. That matters when you re-import a library mid-project and you want control over what gets overwritten.

A companion upgrade utility for existing materials

Node Ninja also ships with a second tool aimed at already built materials. The companion utility is included free with Node Ninja and targets existing Redshift materials built with standard PBR textures. There are three things the utility can do without starting over: switch projection modes, add or remove master controls, and upgrade legacy materials to Cinema 4D 2026’s modern UV Context format. It also scans the material first, pre-fills a dialogue to match what is already there, then rebuilds the graph with the requested changes. It CLAIMS it carries texture paths over automatically. There are limits – the utility is designed for standard PBR materials and is not a converter for complex procedural setups.

Cinema 4D versions, older graphs, and the practical bits

Node Ninja supports Cinema 4D 2024.5, 2025, and 2026 on Mac and Windows. If you run an older Cinema 4D version, Node Ninja uses an older style of control setup rather than the newer UV Context Projection workflow, and it can still build unified scale controls through value nodes.

Pricing is simple: free, with no license key and no trial. But nevertheless, new tools and innovations should be tested before use in production, ideally on a copy of a scene, because automation can propagate the same mistake across a whole library at the same speed it saves time.

https://www.schoolofmotion.com/node-ninja

The post Node Ninja builds Redshift materials from folders first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Maya is a core DCC from Autodesk for modeling, rigging, animation, and FX, with lookdev via LookdevX and node FX via Bifrost, plus pipeline handoff through USD.

The headline feature is editorial glue

Maya 2027.1 adds support for OpenTimelineIO in the Sequencer, enabling interchange of editorial cut data between DCC and timeline tools.

Sequencer gets editorial glue, not just buttons

Maya 2027.1 adds import and export support for OpenTimelineIO, with OTIO data being a standardised equivalent to XML for supported sequence, track, shot, audio, and file reference information. OTIO import preserves camera assignments and camera attributes, and reconstructs tracks from stored track information. The same workflow includes additional shot-level data such as labels, colors, thumbnails, and frame range information.

Sequencer also gets a round of editorial workflow updates beyond OTIO. Autodesk claims improvements to timeline exchange, shot editing, audio handling, playblast output controls, and scripting access. Shot creation now works directly on a selected track, or from a selected Time Slider range. Shot editing includes an updated hold workflow where hold frames come from a dedicated Hold mode while you drag shot edges. That sounds small until you try it on a cut with a dozen micro-trims and discover you do not need to invent a new swearing dialect.

Audio behavior becomes stricter. Sequencer uses only audio associated with the sequence. Audio not linked to Sequencer gets ignored, and Sequencer audio does not mix with Trax audio. A new Time Slider audio menu option called Use Sequencer Sounds controls that behavior. Playblast Shot Options adds Display Size controls for output resolution, with options listed as From Window, From Render Settings, Custom, and From Image Attributes. Output resolution depends on the chosen Display Size and Scale settings. Zooming in Sequencer now centers on the cursor when you use the mouse wheel, which helps the tiemline stop teleporting away from the thing you actually meant to inspect.

As always, new interchange formats look great in demos and get weird at 2 a.m. Test OTIO import and export on your real sequences before you bet a delivery on it.

MotionMaker focuses on editing clarity

Autodesk positions 2027.1 as a release with AI-powered tools and everyday workflow updates, and MotionMaker gets the everyday part this time. MotionMaker now shows frame ranges directly on clips and active windows. The stated goal is clearer timing feedback and behavior aligned with Sequencer.

Character naming gets a cleanup. Autodesk standard characters display simplified names in the UI, dropping the adsk_ prefix while keeping internal identifiers for compatibility. Character definitions also support a display name attribute used in the Create menu and character creation options.

New keyboard shortcuts navigate to the adjacent start frame before or after the current action clip in the timeline, aimed at faster clip-to-clip movement while editing. Updates to character registry handling also reduce redundant processing when creating MotionMaker registries.

Smart Bevel keeps hunting the ugly edge cases

Smart Bevel receives quality updates described as handling more complex geometry with fewer errors, with the practical promise of less manual cleanup on geometry with many intersecting edges.

Cutback relaxation improves to help prevent straight-edge segments from shifting, aimed at hard-surface models that mix linear and smooth forms. Smart Bevel also reduces spikes and jagged sawtooth corners in certain edge cases. Limiting works better across intersection types, with improvements intended to stop bevel results from crossing. Intersections previously missed are now detected.

Arc welding of new junctions becomes more thorough, and isolated arc removal becomes more reliable. Smart Bevel also improves handling of edge sequences that previously failed to bevel, with the result described as proper beveling and prevention of holes or missing faces at junctions along the sequence. Preset support expands so Smart Bevel presets can now save the Remove Isolated Arcs state.

Bifrost adds a search box and more sim and rig polish

Bifrost 3.1.0.8 adds a way to find where specific nodes are used in the graph, plus other new features and improvements. The same version lists updates for rigid body simulation, including per-instance colors, plus performance improvements for rigging and viewport drawing. New high-level compounds include deform_onto_mesh_UVs, wrap_deform_by_mesh, and wrap_deform_by_points. Rigs built with Bifrost now support Maya Cached Playback for improved performance, with a stated limitation that Cached Playback only works if the rig uses no feedback ports.

USD for Maya targets variants, and pins the manager

The USD plugin update listed as USD for Maya 0.36 adds support for targeting specific variants to receive edits, including changes to geometry and materials. The USD Variant Manager can now be pinned to its current display to prevent it from updating when you change selection. That is the kind of feature you only notice after it saves you from editing the wrong thing during a review.

LookdevX projects textures, searches graphs, and stays Arnold-friendly

LookdevX 2.1.0 adds texture projection nodes for mapping textures without UV coordinates. The workflow described uses the Node Library under Autodesk to add a projection node into the graph, connect a texture input, then connect the output to a material. Eight projection types are available: Planar, Spherical, Cylindrical, Ball, Cubic, Tri-Planar, Concentric, and Perspective. A Projection node combines all types into one node, with switching done inside the node so the texture updates on the object.

LookdevX also adds Graph Editor search to find nodes by name, aiming to reduce scrolling in larger graphs. Universal SRT manipulator support lands for the first matrix44 input port on LookdevX nodes, letting you edit that transform directly in the viewport via the usual manipulator workflow.

Arnold and Substance updates ride along

Autodesk lists Arnold for Maya 5.6.1.1 as part of the update, with changes since 2027 including a tech preview of Flow Render, custom AOVs for volume shaders, MIKKTSpace normal mapping support, and additional updates. Maya 2027.1 also includes Substance 3D 3.0.6.

Treat both as pipeline changes, even if you never touch a shader graph. Renderer and material tooling changes can break assumptions in templated scenes, and reliabel output beats exciting output when a client stares at a schedule.

Platforms and pricing

Maya 2027.1 is available for Windows 11, RHEL, and Rocky Linux 8.10 and 9.7, plus macOS 14.0 and later. The software is rental-only, with subscriptions listed as US$255 per month or US$2,010 per year. In many countries, artists earning under US$100,000 per year and working on projects valued under US$100,000 per year qualify for Maya Indie subscriptions, listed as US$330 per year. Maya Creative 2027.1 is also available, listed as pay-as-you-go with prices starting at US$3 per day and a minimum spend of US$300 per year. It has the same new features as Maya 2027.1, except for Bifrost.

New tools and innovations should always be tested before use in production, ideally on real shots and real assets, not a perfect demo cube that never gets a change request.

https://help.autodesk.com/view/MAYAUL/2027/ENU/?guid=GUID-F923AA68-6CE5-4292-88EA-292F5A786BA2

The post Maya 2027.1 adds OTIO to Sequencer first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Boris FX Sapphire is a multi host VFX plug-in suite for editors and compositors, used in After Effects, Premiere, Media Composer, and OpenFX hosts like Resolve, Flame, and Nuke.

Defocus that tries to behave like glass

Boris FX ships Sapphire 2026.5 with a new effect called Advanced Defocus, built to recreate lens blur character rather than just blur pixels. In Sapphire, artists can start from presets, including ones built from real-world lens references and more stylised options, then dial in Defocus Width plus relative width and height for anamorphic style stretching.

Advanced Defocus focuses on the lens kernel, where artists shape bokeh as circles, polygons with adjustable sides and roundness, or custom shapes. It also includes controls to introduce imperfections tied to aperture blades, such as adjustable blade notches, as well as options for colour fringing and noise. The tool targets everything from cheap, dirty glass to high-end primes, depending on how far you push those controls.

The lens vignette section adds classic edge darkening, but also an optcial vignette control that changes distortion toward the frame edges. A Matte Box control goes past soft cropping by simulating uneven light entry, slightly darkening one side while also clipping individual defocused highlights.

From grungy to clean

Advanced Defocus also includes lens textures that break up overly uniform bokeh, with parameters that range from subtle variation to grungy lens looks. Extra controls include highlight boosting, chromatic-style fringing, and grain management to match the foreground and background.

In Adobe After Effects, Advanced Defocus appears under Effect in the Sapphire Blur plus Sharpen category. The effect can work as a straight lens emulation pass, a stylised motion graphics treatment, or a transition building block. A workflow shown in Blackmagic DaVinci Resolve Fusion uses Advanced Defocus to soften a keyed background for more believable depth, then adds sensor-style grain to help match elements. Another workflow in After Effects links defocus controls across layers, uses Affect Alpha to defocus type with the background, and offsets values to keep the illusion that typography sits closer to camera.

For edits, Advanced Defocus can also drive transitions inside VEGAS Pro by building an S Transition in the Sapphire Builder variant designed for transitions. That approach ties animation to the transition length on the timeline rather than keyframing, and then applies the same peak values to both incoming and outgoing clips.

Glare gets a rebuild, and flares get louder

Sapphire 2026.5 reworks S_Glare with smoother rendering, richer spectral color, and updated parameters including highlight isolation, cleaner rays, and more natural falloff, plus new styles that widen the look range beyond traditional glare.

In Adobe After Effects, S_Glare sits under the Lighting category and behaves the same across Sapphire hosts. The first control to touch is Threshold: raise it for fewer glares, lower it for more, and expect wildly different results depending on the footage. Sapphire 2026.5 also changes what the defaults look like compared with older versions, so the same effect can start from a different baseline than legacy installs.

Presets matter a lot for S_Glare, but the preview can mislead. Results change with viewer zoom level, so checking at 100 percent gives a more reliable read before you commit. Presets also store Threshold, so loading a preset often means rebalancing Threshold right away to avoid either nothing happening or everything exploding.

If glares drift or slip onto areas you do not want, Threshold Blur becomes the other big lever. Lowering Threshold Blur picks up many more points of interest, which can reduce slippage but may add jitter. A practical balancing rule shown here is: when Blur comes down, Threshold goes up, then you fine-tune from there.

Sapphire includes integrated Mocha inside the effect for masking control. A workflow shown here uses an object brush and Mask ML to generate a mask, then inverts the Mocha mask so glare stays in the scene but stops emanating from a subject.

S_Glare also appears as an embedded component in S_NightSky, where you can open the glare editor, load glare presets, and adjust glare size to customise the look directly within the NightSky effect.

Procedural ridges, more presets, faster stacking

A new Texture Ridges effect generates ridge-like patterns from noise, with controls for octave scaling, speed, frequency, contrast, and layering to build animated surface detail and abstract motion design textures. Sapphire 2026.5 also adds more than 100 new and improved presets, including anime, sci-fi, and abstract fractal motion graphics looks.

Effect Builder gets an interface update aimed at faster custom effect and transition creation, plus new built-in Dots and Noise tools. If you build stacks for repeatable looks, this is the part worth a quiet test session before you let it touch client shots.

Pricing and updates

Sapphire ships as a plug-in collection with subscriptions, upgrade and support plans, and perpetual licenses. Subscriptions start at 545 US dollars per year or 80 US dollars per month. Customers with current Sapphire or Boris FX Suite subscriptions, or with Sapphire upgrade and support plans, get the 2026.5 release obviously as a free update. If you aren’t sure: get the free Trialversion. As always, test new tools and presets in your own pipeline before you rely on them in production.

https://borisfx.com/products/sapphire/#whats-new

The post Boris FX Sapphire 2026.5 adds Advanced Defocus first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: The Pixel Farm makes PFTrack, a node based matchmove and reconstruction tool that exports to DCCs like Autodesk Maya, Foundry Nuke, SideFX Houdini, Blender and Unreal Engine, with improved dense point clouds via OpenUSD.

Hero Cloud is a new reconstruction node

PFTrack Build 26.05.19 adds Hero Cloud, a node that generates a measured dense 3D point cloud from a single tracked plate. It sits in the Geometry category and runs downstream of a solved camera, turning an ordinary camera solve into spatial data you can actually measure against. Hero Cloud claims to be through-the-lens reconstruction, meaning it extracts depth from the camera movement in the shot rather than relying on a separate photogrammetry set or a LiDAR scan.

The node targets a familiar production reality: you get a brief that needs measured 3D, but the the on-set… people…. said “Fix it in Post, heheeheeh” and did not capture the extra data for cases like set extension, CG integration, lighting reference, forensic analysis, architectural measurement, and archival footage where you cannot go back and reshoot reference. If the plate is all you have, Hero Cloud aims to make that plate pull double duty.

Hero Cloud works on plates PFTrack can track and solve, and works footage sources that include cinema cameras, drones, body cams, dash cams, action cameras, mirrorless and DSLR cameras, CCTV, and archival film. Basically, every type of video. Camera metadata can help but it is not required, and the Camera Sensor Database can cover common cameras automatically, with the Camera Solver able to estimate parameters when metadata is missing.

There is a catch, and it is the same catch as every method that tries to infer depth from motion: the shot needs parallax. Locked off shots or shots with very little movement can produce sparse or unreliable results. Most production footage, including handheld stationary shots, can still have enough movement to produce usable reconstruction, while deliberate camera motion tends to produce richer results.

A cleaner route into splat training

PFTrack 26.05.19 adds a Postshot export option that writes Hero Cloud point clouds and associated tracked cameras in COLMAP format. In other words, matchmove and reconstruction can stay in the same app up to the point where you hand off to splat training.

If you already live in the Gaussian Splatting world, COLMAP is a common interchange format and COLMAP itself has both GUI and command line workflows. The practical value here is that you do not have to glue together separate tracking, reconstruction, and export steps before you ever open Jawset Postshot. You track the plate, generate the cloud, export in COLMAP format, then train the splat.

This is an artist friendly route into a workflow that has historically leaned on command line tooling. That is a reasonable and recommendable goal, but it still deserves the usual pipeline skepticism: try it on a real shot and verify your coordinate frames, scaling, and camera consistency before you let it anywhere near a deliverable.

USD point clouds now carry more than positions

The same build extends USD export to support dense point clouds with per point normal and colour data, because a point cloud that only carries XYZ positions often becomes a dumb scaffold the moment it leaves its origin app. Normals and colour help downstream tools treat the cloud as more than a vague spatial fog, and can make it easier to use for measurement, placement, modelling reference, and lookdev decisions.

Improved integration with USD aware tools including Unreal Engine, Maya, and Houdini. It also claims (!) improved FBX export reliability for very large dense point clouds, aimed at users who previously hit issues exporting big clouds via FBX.

If your pipeline already standardises on USD, this is the kind of unglamorous export detail that can decide whether a new feature becomes a daily tool or a demo-only party trick. Still, test it on your actual asset scale and on your actual DCC import settings. Export support is never a substitute for shot-based validation, and you only find the sharp edges when production hits them, much like furniture at night can only be found with toes and shins.

Photo Mesh gets a single shot input path

Studio and Enterprise editions receive an update to Photo Mesh that enables it to consume Hero Cloud point clouds as input. That creates an internal single-shot path from tracked plate to dense cloud to surfaced textured mesh, without leaving PFTrack. The Pixel Farm describes Photo Mesh as the highest fidelity route when you have a planned photo set, while Hero Cloud covers the case where you only have the hero plate.

In practical terms, this puts a reconstruction option closer to matchmove, and it reduces the number of handoffs in the middle of a cmaera tracking job. Whether it replaces any external reconstruction tooling depends on what you already trust for meshing, texturing, and scale fidelity, but the internal integration is at least a coherent story: generate the cloud, feed it into Photo Mesh, then export into the rest of your pipeline.

The viewport tweak you will actually use

26.05.19 also adds an Active Camera viewport option in viewer windows, with a snap to active clip toggle. It sounds minor, and it is, which is why it will get used: quick visual verification against the source plate tends to catch mistakes faster than hunting through node outputs. The release notes pitch it as useful for checking Hero Cloud reconstruction, but the feature applies anywhere you want a fast way to see what the tracked camera saw.

Trial and licensing notes

Solo trial mode now enables full export functionality for seven days. The release notes describe this as enough time to take a plate from track through Hero Cloud and out to Postshot or USD, rather than being limited to evaluating the toolset without export.

For Studio, the release notes state it is available on rent to buy for 5 or 30 days, or as a perpetual purchase. The PFTrack Creator Program page states PFTrack Solo licenses sell for £699. Treat that as a price reference for Solo licensing, not a promise of regional pricing or bundles.

What this changes in real work

Hero Cloud aims to shift PFTrack from a pure matchmove and survey friendly reconstruction hub toward a single shot scene reconstruction step that can be used even when the onset data plan fell apart. The strongest parts of the release are not flashy, they are connective tissue: COLMAP export for Postshot, denser USD point cloud payloads, and a meshing path that stays inside the same graph.

It is also a reminder that the industry has started to treat point clouds as a first class asset, not only a temporary byproduct. When point clouds export with colour and normals and survive the trip into USD aware DCCs, they become reusable poitn based reference that can support layout, set extension decisions, and reconstruction driven previs.

https://www.pftrack.com/post/pftrack-build-26-05-19-is-now-live

https://www.pftrack.com/post/hero-cloud-tutorial

The post PFTrack gets Hero Cloud first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Clip Studio Paint does illustration, comics, and 2D animation on desktop and mobile, and sits alongside the wider Clip Studio app and its cloud and asset ecosystem.

Version 5.0 is about speed and control

Celsys puts Clip Studio Paint 5.0 on iPad, iPhone, Android, Windows, and macOS as a new major release, updating drawing performance and workflow comfort, with new tools aimed at getting cleaner results without constantly switching modes.

If you spend your day in line work, the headline feature is Smart Shape. You draw with any pen or brush, then long press to tidy a line, curve, or shape without jumping to a separate figure tool. That idea reads small, but it targets the exact kind of micro friction that adds up over a hundred panels or a long day of design passes. It is also the kind of feature that can change muscle memory, so plan a short retraining window before you bet client work on it.

The 5.0 feature list also calls out faster rendering with large brushes using a new setting that trades quality for speed, and improved rendering speed for thick watercolor edge settings. Stroke previews can help reduce brush lag when you draw with high stabilization. The blur tool and brushes with Running Color also change blending behavior, so colors outside the brush cursor or selection stop blending in that mode.

Smart Shape wants cleaner lines without a new tool

Smart Shape lives in the same place as your usual brushes, and it tries to keep you there. Instead of switching away from your current drawing tool, you trigger the cleanup by holding your stylus down at the end of a storke, then let the app resolve it into a cleaner result. That matters most when you bounce between sketchy exploration and precise technical marks, where changing tools can feel like slamming the brakes every few seconds.

On the settings side, Smart Shape can be toggled in Preferences under Tool. That makes it easy to turn on for inking sessions and turn off when you want raw, messy exploration, without building separate workspaces just to keep it from interfering.

The update also introduces velocity as a new brush dynamic, with a velocity graph added to Pen Pressure Settings and Tilt Settings as an option for brush size and opacity input dynamics. In plain terms, you can push values higher the faster you draw, which is useful when you want quick flicks to behave differently from slow, controlled marks.

3D gets hands, fog, and more paintable surfaces

On the 3D side, Clip Studio Paint 5.0 adds a hand model to the 3D materials, positioned as a reference tool for drawing hands. The tool includes adjustable hand shapes, and it works with hand pose materials and a Hand Scanner for quick posing. That puts a dedicated hand reference directly in the same scene where you already stage characters and props, instead of forcing a second app or a browser tab for reference.

The 3D feature list also expands where you can draw directly on 3D objects, including UV mapped vertices plus 3D primitives and 3D drawing figures. It also adds the ability to group multiple 3D models into a folder and move or rotate them as one, which fits the way artists actually block scenes, especially when you want to keep a kitbash cluster behaving like a single prop.

Fog gets a specific upgrade too. You can set Fog type to Height on a 3D layer and define fog based on the height of the 3D space, including whether it starts from above or below. It is a simple knob, but it can help with depth cues in backgrounds, quick lighting mood boards, and concept paintovers.

For internal workflows, the EX edition gets batch export textures on 3D layers when you select them with the Object tool. That lets you export all textures of a custom material or model at once, which sounds mundane until you are the person who keeps getting asked to deliver “all the textures, please” five minutes before a handoff.

If you follow concept art workflows, the net effect is less time fighting reference and more time iterating on design.

Layer ops and UI cleanup aim at real work

A production painting app lives or dies by small operations, and 5.0 targets a few that show up constantly. Tonal correction commands can now apply to multiple layers at once, applying color corrections to each selected layer. That is useful when you keep values separated by material, pass, or shot element, but still need consistent global tweaks without flattening.

The Fill tool also gets a speed and accuracy improvement, pitched as faster processing with more accurate results. If your pipeline includes lots of flat color blocking for comics, animation layouts, or stylized game art, faster fill behavior is the kind of quiet win that saves real time.

Interface changes focus on reducing terminology and palette friction. Sub Tools get merged into Tools, and tool icons can pop up with related palettes. The Material palette gets a new History folder to show recently used materials, plus easier search and sorting.

In 5.0.4, image materials and template materials, including 3D hand model materials, can sync to the Clip Studio cloud and publish to Clip Studio Assets. That is a practical detail for teams, classrooms, or anyone jumping between machines, as long as you are comfortable with the asset management implications and you test your sync behavior before relying on it in a deadline week.

Licensing and

Celsys lays out multiple ways to get 5.0, depending on whether you subscribe or buy perpetual on Windows and macOS.

New perpetual licenses list at 63 Dollars for Clip Studio Paint PRO 5.0 and 277 Dollars for Clip Studio Paint EX 5.0 on Windows and macOS. Discounted perpetual upgrades from 4.0 to 5.0 list at 29 USD for PRO and 83 $ for EX, with a PRO to EX discounted upgrade to 5.0 listed at 243$

Update Pass pricing for 12 months on Windows and macOS lists at 11$ for PRO and 32$ for EX. Active subscribers and Update Pass users can update to 5.0 as part of their plan.

If your daily setup includes a pen display, a few of these changes will feel less like “new features” and more like fewer tiny interruptions between you and the canvas. Test Smart Shape with your usual brush presets, stabilization settings, and tablet drivers. Test the new blur behavior on the exact kind of painterly blends you rely on. Test 3D grouping and paint on model workflows with the kinds of assets you actually use, especially if you share files across machines or collaborators. New tools and innovations should be tested before use in production, even when the change looks small.

https://www.clipstudio.net/en/dl/release_note/latest/

https://www.clipstudio.net/en/news/202603/11_01/

The post Clip Studio Paint 5.0 with 3D hands first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: DroneSiteBuilder is a script for Autodesk 3ds Max that reads drone photo metadata to assemble terrain, map context, and matched cameras, bundling GeoBuild and CameraMatch and supporting handoff to Blender, SketchUp, and Autodesk Maya.

What DroneSiteBuilder is trying to fix

DroneSiteBuilder Enterprise turns a folder of drone photos into a full site context scene inside the 3ds Max ecosystem: terrain, aerial drape, buildings, roads, land cover features, points of interest, and one matched camera per photo.

The pipeline reads XMP metadata per image and uses it to place helpers at ground level and flight altitude, then creates a renderer-aware camera per photo and refines orientation using vanishing point detection. The tool targets 3ds Max 2020 or newer on Windows and uses Python 3.9 through 3.12 with NumPy and OpenCV, plus optional modules for the Google path.

First use, abbreviated

Install a standalone Python build and make sure Add Python to PATH is enabled during install, because the tool does not rely on the 3ds Max built-in Python. Place DroneSiteBuilder_Enterprise.ms and vp_detector.py in the same folder and do not install under Program Files, since Windows blocks writes there.

Launch 3ds Max and load the script via drag-and-drop into a viewport or via Scripting > Run Script. Paste your licence key into the activation dialogue and activate, with support for an Enterprise key format and existing CameraMatch Studio keys. After activation the key caches locally for thirty days and the rollout opens.

For the first build, keep original DNG or JPEG drone files in a single folder, keep filenames ending in digits, and keep an internet connection available for the auto fetch steps. Pick a terrain DEM source, keep NOAA GEOID18 enabled for continental US sites and disabled outside the US, then run Process Folder of Drone Photos and accept the summary dialogue. Inspect the result by comparing a matched camera view against the source photo.

The new checkbox: Google Photorealistic 3D Tiles

Enterprise v1.2 adds an opt in mode that fetches Google Photorealistic 3D Tiles and imports them into 3ds Max as a single merged glb, covering the photo bounding box. The intention is simple: pull a photogrammetric backdrop mesh with terrain, textures, and buildings baked into one continuous model, using the same dataset shown in Google Earth.

The Google path requires a Google Maps Platform project with billing enabled and the Map Tiles API enabled, plus a saved API key in the rollout. The manual describes 1,000 root tileset requests per month free and a per 1,000 price after that, with one DroneSiteBuilder run treated as one root tileset request. If the fetch fails, the tool reports common causes like missing API enablement, low coverage, EEA billed accounts being blocked for this endpoint, missing Python modules, and older 3ds Max builds needing a glTF importer.

This is also where the gaudrrails get real: the Google import produces mesh only content with baked textures, so you do not get separate terrain, buildings, roads, and features objects to isolate, re material, or hide by category.

The standard path is still the controllable one

If you leave the Google option off, the pipeline builds a layered context using public services. Terrain comes from USGS 3DEP in the US or OpenTopography worldwide, aerial imagery comes from Esri World Imagery as a single bounding box JPEG, and vector context comes from OpenStreetMap via Overpass.

The scene builds under a single root helper so you can move, rotate, or scale the entire site as one unit, while cameras intentionally sit outside that parent chain to support camera transplant between scenes. If buildings and roads fail to appear on a run, the manual provides a manual Overpass refetch button that rebuilds buildings, roads, and land features without disturbing terrain, drape, helpers, or cameras.

OpenStreetMap accuracy varies by location and that the resulting geometry accuracy for this context layer sits in the one to six meter range. It contrasts that with paid city model providers such as AccuCities when millimeter level detail matters.

Export and handoff from 3ds Max

DroneSiteBuilder does not change how 3ds Max exports, but it does influence what you export. The standard path creates distinct terrain, buildings, roads, and feature objects you can selectively include in deliverables, while the Google path imports a tile based mesh group that is already baked.

For broad DCC and engine handoffs, 3ds Max includes a built in exporter for glTF and supports export workflows for USD, with export options available through File export and USD and USDZ format selection when the USD tooling is installed. For USD pipelines, the official OpenUSD plugin for 3ds Max is published on GitHub, and Autodesk documentation describes supported USD content types including meshes and cameras.

If your downstream is realtime, glTF targets web and interactive use cases, and you can also push common interchange paths like FBX into engines such as Unity and Epic Unreal Engine, depending on your studio conventions. For camera and layout continuity between scenes, the bundle includes a camera transplant workflow that exports camera data to JSON and recreates it with full precision in another scene.

Practical reality check

This toolkit aims to comperss a traditional drone to 3D context workflow into a short unattended run. The promise stands or falls on your input photos keeping XMP metadata intact, on your site area having decent public map coverage, and on you verifying the result against the plate before trusting it.

We don’t know the price yet, but if you already own the camera match tool in the Studio version, you get it for free, apparently. Quoting: Existing CameraMatch Studio licence keys activate the full DroneSiteBuilder bundle. Studio holders do not pay twice. 

Try both context modes on a test job: the standard layered build when you need controllable components and re-lighting freedom, the Google mesh mode when you need a fast photogrammetry backdrop and can live with mesh-only content and licensing constraints.

https://jamiecardoso-mentalray.blogspot.com/2026/03/dronesitebuilder-enterprise-v12-one.html

https://jamiecardoso.gumroad.com/

The post DroneSiteBuilder adds Google 3D Tiles option first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

In this video we will explore how we can simulate realistic “kick up dust” from wind that is blowing over a surface in Maxons Cinema 4Ds internal Pyro simulation tool. The most likely use case is the effect you probably know from a helicopter taking of or landing.
As I learned yesterday, this effect is known as “downwash”.

Learn how to solve for air pressure and use the output of the moving airfield to automatically create and simulate dust picked up from the ground and carried away by the air movement realistically.

CHAPTERS

00:00 Intro

00:48 Tut Overview

01:31 C4D Scene Setup: Geometry

03:02 About Pyro Solvers

04:33 Setting up a Pyro Domain

08:26 Setting up the Downwash Wind

10:33 Setting up Vectors (Velocity)

14:57 Offsetting the Collision Landscape

15:57 Caching the 1st (Base) Simulation

16:30 Setting up the Dust Emitter Vertex Map

18:33 Simulation Scene Object

20:21 Field Force

20:49 Finalizing the Downwash Sim

23:00 Looking at the Results

Download the Tut Scene by becoming a Patreon member. No matter which tier!

VIDEO RELATED LINKS:
Maxon’s Official Website: https://www.maxon.net/
Octane C4D Otoy Official Website: https://render.otoy.com/forum/viewfor…

---

If you’ve ever wondered what happens when a VFX artist spends too much time obsessing over pixels and lighting, well, welcome to my world! You can find all my latest experiments, tutorials, and general nerdy shenanigans here:

Website: silverwing-vfx.de
Patreon: patreon.com/SilverwingVFX (Get scenefiles for all of my tutorial scenes also while supporting me)
Instagram: instagram.com/silverwingvfx (Finished 3D projects and engagement with the community)
YouTube: youtube.com/@SilverwingVFX (Updates and news about my work and what I am up to)

And if you’re into retro gaming and deep-dive nostalgia, check out the big article I wrote for this magazine: my love letter to the legendary Game Boy. Because nothing says “true love” like an 8-bit screen and a battery life that could outlast modern smartphones.

The post C4D Pyro Tutorial: Helicopter Kickup Dust first appeared on DIGITAL PRODUCTION and was written by Raphael Rau.

For those who don’t know the tool: Beeble builds AI relighting and video transformation tools for VFX, post, and virtual production, and Canvas is its very new node based environment that wires SwitchX and SwitchLight into repeatable shot workflows.

A node graph, but for AI outputs you can wrangle

Canvas lands as a node based AI compositing environment aimed at complex workflows across VFX, post, and virtual production. The pitch is straightforward: put AI video models, compositing utilities, and workflow automation into one visual system so teams can iterate across multiple shots without rebuilding the same logic over and over.

In practical terms, it targets the part of the job where you already juggle plates, masks, reference stills, and multiple look directions, then repeat that dance across a sequence.

What is actually in the box

Canvas presents itself as a node graph workflow editor for final render, with a catalog grouped into Input, AI Tools, Edit, and Utility. Input supports text prompts plus image files in PNG, JPEG, or WebP, and video files in MP4 or MOV. In other words, it starts where most editorial and comp workflows already start: media in, decisions next.

https://digitalproduction.com/2026/05/20/beeble-canvas

The AI Tools section includes a node for SwitchX, the same model as the standalone product, with source and alpha handled as video inputs. It also includes an LLM node that can generate files from a prompt with up to four media inputs, plus image generation and video generation nodes that can route to external models. For rotoscoping style work, Canvas includes a Video Matte node that outputs an alpha matte plus RGBA, with an automatic mode and an interactive selection mode, plus options aimed at general footage and green screen keys.

On the classic comp side, the Edit nodes cover the expected utility moves: extract a frame, trim, crop, resize, curves, invert, flip, and morphology operations like erode and dilate. Utility nodes cover housekeeping: sticky notes, routing for cleaner graphs, a viewer, side by side compare, and export. It’s not fully Nuke yet, but…

That combination matters because it lets artists keep the media prep and look development steps next to the model calls, instead of bouncing between separate tools and hoping filenames stay honest.

Relighting and PBR passes, now wired into the graph

The system includes access to SwitchLight for generating physically based rendering passes. In the Canvas node catalog, the VFX Pass Generator extracts PBR material maps including BaseColor, Normal, Depth, Roughness, Specular, and Metallic from image or video using SwitchLight 3.0.

That puts relgihting adjacent tasks into the same graph where you also assemble mattes, feed references, and generate variations. It also matches the stated intent of supporting controllable, iterative pipelines across multiple shots, not one off experiments.

Automation, batches, and the part everyone really wants

Canvas claims to be built around repeatability: build workflows once, apply them to shot sequences, and automate iteration without rebuilding node logic shot by shot. It also calls out batch processing and maintaining scene consistency across projects.

Those claims describe the correct pain point. Anyone who has ever reconnected the same five nodes fifty times will understand why a programmable layer matters. Still, treat the automation story like any new tool claim: test it in your own pipeline with your own edge cases before you bet any delivery on it.

The API angle: SwitchX in your pipeline, with pricing details

SwitchX API for video transformations in YOUR pipeline

Alongside Canvas, the SwitchX API is positioned for studios and developers who want to integrate video transformation and relighting capabilities directly into custom pipelines and software environments.

The developer portal offers a REST style workflow with uploads, job creation, and polling, and it explicitly supports 720p and 1080p output. It also has pay as you go credits in US Dollar, and pricing can start at $0.10 per generation. That pricing applies to the API offering as described there, while Canvas pricing is not specified, since it is part of Bebble Online.

Beeble Studio: 4K AI relighting on YOUR desktop

Availability, media assets, and credits

Canvas is available now via the Beeble platform, with a launch video hosted on YouTube (The Video we embedded above…) .

The boring but necessary reminder

New tools and innovations should be tested before use in production, especially when they touch shot consistency, automation, and delivery formats. Run a small sequence through, break it on purpose, and see how it fails before you trust it on a deadline.

https://docs.beeble.ai/beeble/canvas
https://docs.beeble.ai/beeble/overview

The post Beeble Canvas first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Dash runs inside Unreal Engine as an asset browser plus world-building toolkit. The Fab build ships the Content Browser only, while the website installer can also unlock the wider toolset with a paid license.

Two installs, one idea

Polygonflow now offers Dash in two distinct ways: as a free plugin on Fab and as the full Dash installer from the Polygonflow website.

The Fab listing calls the package “Dash – Advanced Asset Manager” and in this version, it is “just” a content browser that lets you search and drag and drop local assets into any UE5 project. It includes tagging for your own assets with a stated limit of up to 1,000 assets tagged per month, plus a Smart Collection System for organizing assets.

The website installer route matters more, because the Dash Content Browser itself has been available for free since Dash version 1.9.0, but the free license is limited to the Content Browser side of the toolset. The free license includes the supported libraries, the tagging system, and the centralized browsing experience across UE5 projects, but not other Dash tools such as Easy Scattering, Procedural Meshes, Physics Tools, or Material and Atmospheric Tools.

What is actually different between Fab and the website build

The Fab version includes the Content Browser only, and explicitly points to the website download if you want the full plugin toolset. The website build splits into two experiences. The free license stays content-only, meaning you use the Content Browser, library integrations, tagging, and centralized asset browsing. A paid license can unlock the other Dash tools, Easy Scattering, Procedural Meshes, Physics Tools, and Material / Atmospheric Tools. So the practical difference is not the content browser UI, it is how far you want to go beyond asset browsing once you are inside the same plugin shell.

Included libraries, and why that matters more than the tagline

Both the Fab listing and the Dash docs have the same core set of integrated libraries: Quixel Megascans via Fab or Quixel Bridge downloads, Amazon Berkeley Objects with 6,900 models, ambientCG with 2,300 textures plus HDRIs and decals, Poly Haven with 1,900 assets plus textures and HDRIs, The Base Mesh with 1,400 models, and the IES Library with 1,300 lighting presets.

On the website side, the Dash Asset Marketplace lives inside the Content Browser, with the Dekogon library and a Sierra library entry that includes one free pack.

Polygonflow also supports browsing and importing content across multiple UE projects from inside the project you are currently working in. The docs add a warning on version compatibility for external browsing: UE5 projects are forward compatible but not backward, so you can browse content from the same or older UE5 versions, not newer.

Custom assets, right now

In the Project Library tab, you can currently add your own static meshes, textures, and blueprints. The tagging flow focuses on making assets searchable beyond filenames and folder names, and the content browser adds collections for grouping assets into reusable sets.

Pricing and the usual production warning

On Fab, Dash – Advanced Asset Manager is free. Commercial pricing for paid Dash licenses is 8€ for students, 20€ per Month for professionals below the 250.000$ barrier, and 95€ per month for bigger studios. Test any new browser, tagging, or library workflow on a non-critical project before it touches production depots and shared team setups.

https://www.fab.com/listings/865301e9-2d26-425d-8f3c-e0aadf35da61
https://docs.polygonflow.io/advanced/free-content-browser

The post PolygoFlow Dash asset manager goes free on Fab first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Simple Tree Tools 3.0 targets artists who want tree and plant generation to behave like the rest of a Houdini graph: parameter driven, non-destructive, and easy to rewire when a shot brief changes at 6pm.

The toolset runs in Houdini 20.5 or later. The supported editions depend on the license tier and include FX, Core, Indie, Apprentice, and Education. In day-to-day use, the pitch is straightforward: generate species with controls that stay editable, shape plants with growth responses, and keep the whole thing inside a network you can hand to the next person without a sacred PDF explaining which button not to touch.

Procedural generation, but with plant brains

The feature list leans hard into procedural generation. The tools aim to generate any species of tree with non-destructive, parameter-driven controls, covering everything from small plants to large trees.

Plant shaping focuses on environmental response through tropisms. The named list includes Gravitropism, Phototropism, and Thigmotropism, with several others also mentioned. For art direction, growth can be guided using guide curves or vector fields.

If you live in the Houdini tag archive, this sits comfortably in the same mental drawer as other procedural effects tools: the value comes from staying editable until the last responsible moment, not from making a single perfect hero tree once.

Scan extension nodes for the trunk people

3.0 also includes scan extension tools aimed at hybrid workflows: scanned trunks, procedural branches, and a bridge between them.

Two nodes are important: Scan Initialize and Scan Stitch. The stated goal is to seamlessly extend scanned geometry and blend procedural branches onto high-resolution trunks with physical and UV-mapped transitions. That matters for asset teams that already keep a scan library but still need variation and shot-specific dressing without resculpting every new silhouette.

If your environment’s pipeline already leans on library assets and a sprinkle of procedural dressing, this positions the tool neatly inside CGI environments work, where consistency and iteration speed beat heroic one-offs. Test your scan handoff carefully, though, because any workflow that mixes geometry sources can surprise you in UVs, scale, and downstream exporting.

Wind, growth, and the licensing reality check

Licensing and commercial use come with unusually plain language. The toolset uses one-time purchase licensing with no subscriptions or recurring fees, and purchases cover all v3.x updates delivered automatically through Gumroad. Future major versions such as v4.0 may require a separate purchase, with a discounted upgrade price mentioned.

The FAQ states you can sell models, renders, asset packs, game assets, and film work created with the tools if you only hold a Limited Commercial license. You cannot redistribute the tool’s own HDA files. The Non-Commercial tier restricts use to personal learning and non-revenue work, and it ships as .hdanc files, which forces Houdini into non-commercial mode when those nodes exist in a project.

If you buy a paid license while staying on Houdini Apprentice, the FAQ states it does not remove export restrictions. The tool does not alter your Houdini license limitations, so you need to match your tool license to your Houdini license to avoid unpleasant surprises in prodution.

Support runs through email (nirfse3d at gmail.com) – refunds generally are not offered due to the digital nature of the product, with an invitation to reach out if a serious issue appears. As always, treat new tools like new plugins: build a small test scene, push it through your actual export path, and only then let it into a network that people depend on.

Pricing and tiers

Pricing has four tiers: The Non-Commercial tier is free and a good way to test the tools. The Limited Commercial tier costs $99 and targets hobbyists and freelancers with annual revenue under $100k USD. The Full Commercial tier costs $229 and targets hobbyists and freelancers with annual revenue above $100k USD. A Studio tier costs $1,299 and is described as a site-wide studio license. So, for the big players, not as little ones.

The plugin also has file type differences by tier. Non-Commercial uses .hdanc. Limited Commercial uses .hdalc. Full Commercial uses .hda. The Studio tier also lists .hda.

Individual licenses allow installation on up to two personal machines for a single user. The Studio license covers unlimited installs within a single facility.

https://simpletreetools.com
https://nwestfelt.gumroad.com/l/SimpleTreeTools-v3

The post Simple Tree Tools 3.0 goes procedural first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the Project: Blender Studio ships open movie assets, training, and production tooling built around the Blender DCC, including add-ons and pipeline workflows for animation and rendering, as well as battletesting the whole Blender Pipeline.

The film release, minus the fluff

Singularity is out as a short film in 4K HDR, framed as a painterly space adventure directed by Andy Goralczyk. It follows a small creature whose home gets destroyed by an ominous black hole, pushing it toward a group of luminous creatures and a mysterious celestial being.

The release matters less for the plot and more for what it packages with the movie. The singularity includes downloads of ALL production assets, frames, and high quality encodes under a Creative Commons Attribution license. That makes it usable as real-world test data for storage, conform, and review, not just a nice watch on a big screen.

Painterly look, procedural muscle

The production leans into a watercolor inspired style led by art director Vivien Lulkowski, mixing hand-crafted textures and brush strokes with generative effects. That combination aims for an organic look in the creatures while keeping the black hole graphic and geometric.

On the tool side, the film was created with the most recent in-development version of the DCC, and the team expanded the Brushstroke Tools library with new painterly assets. They also used Geometry Nodes to develop procedural “crowd animation” systems (The quotation marks are about the Crowds, not the system), which makes the project a handy reference if you want to compare node-based instancing logic against your own setups or caching strategy.

If you want a fast internal taxonomy for the kind of work this project touches, it sits squarely in animation and practical stylization, with enough proceduralism to interest anyone who keeps one eye on Geometry Nodes changes.

Story development, and what you can actually access

A dedicated story development “article “log” exists by director Andy Goralczyk, but the page requires a login to read the full content – you can support Blender Studio with a subscription for access to training.

HDR is the real production test here

The 4K HDR part is not a sticker, it is a workflow commitment. HDR delivery usually forces decisions about monitoring, transforms, and what you consider the master, especially when you also need an SDR version that holds up. The projectfocuses on watching it on a large screen, but for post teams the more interesting angle is that it gives you real files to validate ingest, grading, and export choices with.

If you are sanity-checking what HDR usually means in standards terms, ITU-R BT.2100 defines image parameter values for HDR television used in production and programme exchange. That is the kind of reference point that helps when your pipeline debates drift into vibes.

Practical take for production people

Treat the release like a compact pipeline exam. Download the encodes and frames, throw them at your review stack, test your HDR monitoring chain, and see what breaks first. If you plan to reuse any assets, read the license terms carefully, because attribution requirements can collide with real-world deliverable constraints.

https://studio.blender.org/projects/singularity/

The post Blender Singularity lands in 4K HDR first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Boris FX Continuum is a multi host VFX plugin set for editors and compositors in Adobe After Effects, Adobe Premiere Pro, Avid Media Composer, Apple Final Cut Pro and Apple Motion, Foundry Nuke, and DaVinci Resolve plus Fusion, with a shared FX Editor and Particle Illusion module.

Deinterlacing that does not feel like archaeology

Continuum 2026.5 adds an ML based deinterlacer called “BCC+ Deinterlace ML”. The idea is to take interlaced material (The bane of archived footage) and output progressive scan frames – the kind of footage you still get handed at the worst possible moment, including analog TV sources and VHS transfers, and it sits in the image restoration lane where you want it.

It also lands next to the classic, non ML deinterlacing option, BCC Deinterlace, which already covers interlaced to progressive conversion and includes options like TeleCine style pulldown and converting 29.97 fps NTSC to 24 fps film style frames. The takeaway: 2026.5 now offers two approaches in the toolbox, and you can pick based on what the clip does when it hits motion, fine detail, and compression.

Four ML models get a tune up, plus a GPU memory bouncer

Continuum updates four ML models: Face ML, License Plate ML (Yes, it’s a thing, and surprisingly useful!), Motion Blur ML, and UpRes ML. Face ML adds nose and neck segmentation, giving the face tool more regions to isolate for beauty work, stylised grading, or targeted fixes. Motion Blur ML adds a prismatic colored blur trails option, which pushes it from pure repair into a more obviously stylised look.

The release also introduces an ML model unload system that automatically removes an unused model from the GPU after a period of inactivity, then reloads it when needed. In day to day work, that aims to reduce the slow creep where multiple ML effects sit on a timeline and quietly claim VRAM, especially when you bounce between shots and forget what still has an ML node enabled. VRAM is too expensive these days to waste it on unused code.

If you rely on masking helpers for cleanup and selective looks, the best advice remains boring and true: test ML updates on your very, very worst footage first, not your demo reel footage. New models can change edges, temporal stability, and failure cases, so validate them before you bake them into a show pipeline.

FX Editor gets better at isolation and color sanity

Continuum’s FX Editor adds an integrated Pixel Chooser workflow for isolating effects within a single layer using shape masks, luminance keys, and AI-driven depth maps. The point is fewer stacked layers and fewer “why is this matte two precomps deep” moments. If your day involves lots of stylisation, glow stacks, lens effects, or targeted distortions, faster isolation saves time and makes revisions less error-prone.

The FX Editor also adds a colour management panel with OpenColorIO colour config presets, plus exposure and gamma sliders. That targets consistency when you jump between host apps or when a project uses a defined colour config, and you want the plugin preview to match the host viewing transform as closely as possible. The panel does not magically solve color management on its own, but it gives you one more place to keep settings aligned instead of eyeballing it.

An info panel provides live RGBA and pixel position readouts. That sounds small until you need to match a graphic element, verify a clamp, or confirm what the effect actually output at a pixel. It is the kind of utilitarian feature that rarely makes marketing art but regularly saves real time.

You will likely see these changes show up first in workflows already living on Pixel Chooser driven isolation, especially for masking heavy looks, selective blurs, and depth based focus tricks. One caution: more control panels also mean more places for mismatched settings, so build a quick checklist for the team and keep it consistent across shots.

Warps and displacements get rebuilt for more control

Continuum 2026.5 overhauls parts of the warp and displacement category. BCC+ Ripple now includes three independent ripples you can adjust separately or globally, plus new waveform shapes and perpendicular height options aimed at advanced distortion looks.

Displacement effects, including BCC+ Displacement Map, BCC+ Polar Displacement, and BCC+ Vector Displacement, gain access to over 1000 built-in displacement maps via the FX Editor, along with RGB separation controls. They also add built-in glitch animation and an integrated Beat Reactor that syncs animation to music. That combination signals an intent to make these effects more preset-friendly while still giving artists enough knobs to art-direct motion without keyframing every wobble.

If you have already used distortions as a finishing pass, the refresh should feel like less fighting for predictable behaviour and more time exploring variations. If you use them as a hero look, plan for a quick reapproval cycle on existing presets, because reworked effects can render slightly differently than older versions.

Wipes learn to take direction, literally

Three wipe transitions add a gradient control: BCC+ Smoke Wipe, BCC+ Texture Wipe, and BCC+ Depth Wipe. The gradient aims to guide direction, focus, and motion so the wipe does not have to hit the entire frame uniformly. Gradient types and radial direction changes live in the FX Editor, so the same place you audition presets becomes the place you shape the transition.

This is the kind of feature that can quietly improve editorial pacing. A wipe that starts where the viewer already looks often feels cleaner than a wipe that bulldozes the whole frame at once. It is also a practical tool for hiding cut pain when you need to blend shots that aaaalllllmoooooost (*Arrrgh*) match.

If you work in multiple hosts, the core appeal remains consistency: the same transition concept travels between apps, so you can rough it in the edit and refine it later without switching tools.

Particle Illusion gets parameter linking that actually helps in production

Particle Illusion inside Continuum, and in the standalone Particle Illusion Pro, gains several upgrades in 2026.5. Parameter linking lets you link parameters across particle nodes, so one change updates all linked nodes. That targets the common problem where a multi-node preset looks great until you tweak one emitter and everything falls out of alignment.

Colour mapping adds gradient mapping modes for more deliberate colour control, including angular, linear, and radial mapping, plus controls for offset and angle. The emphasis is non-random control, which helps when you need art direction rather than happy accidents.

Clone Particle Type links position-related parameters to keep multi-node effects aligned while you adjust looks. Link All Clone Parameters allows retroactive adjustments to existing presets, so you can modernise an older setup without rebuilding node by node.

For motion graphics and comp work, these features read like a direct attempt to make particle presets more editable without breaking. That matters because Particle Illusion thrives on presets, but production survives on revisions.

About one third into your tests, try pushing a complex preset harder than you normally would. If the links hold under aggressive changes, you can trust them in real jobs. If they break, you at least learn where the limits are before a client does.

Presets, performance, and the usual upgrade math

Continuum 2026.5 adds more than 150 new presets across categories, including Blur, Lens, Particle Illusion, Stylise, Title Studio, Transitions, and Warp. Several existing effects gain new parameters, including BCC+ Scanline and multiple dissolve variants tied to ripple and displacement. Beat Reactor also extends to more effects.

Title Studio receives improvements and adds 70 new drag-and-drop presets. If you rely on Title Studio as a fast title lane inside an NLE or comp host, more responsive performance and a refreshed library tend to matter more than a single marquee feature.

Pricing stays in the same model family: subscriptions, upgrade and support plans, and perpetual licenses. Subscriptions start at $325 per year or $48 per month. Customers on a Continuum subscription or upgrade and support plan, or the Boris FX Suite subscription, receive 2026.5 as a complimentary update.

As always, run a proper production-style bake-off before you roll it out. Test archival interlace conversions, stress the ML tools on tough edges, and verify that existing presets render consistently across your key hosts.

https://borisfx.com/products/continuum/

The post Boris FX Continuum 2026.5 tunes AI and FX Editor first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Unreal Engine is a realtime 3D engine and editor used for games, VFX, and virtual production, with tools like MetaHuman, Nanite, and procedural systems like PCG built in.

The preview nobody should install on Friday

Unreal Engine 5.8 Preview is available now to download via the Epic Games Launcher, GitHub, or for Linux. Epic Games positions this Preview around performance advancements and systems meant to feel more reliable, scalable, and intuitive.

That Preview label still means what it always means: The build is not quality tested, it remains under active development, and it can and propably will be unstable until the final release. Make a copy of your projects for testing rather than converting your mainline work.

Mesh Terrain goes full 3D, experimentally

The headline feature in 5.8 Preview is Mesh Terrain, flagged as Experimental. It uses a 3D mesh based architecture for building massive environments and it works natively with the Procedural Content Generation Framework. If your pipeline already leans on procedural layout, the idea is straightforward: terrain becomes part of the same graph driven worldbuilding conversation, instead of a separate special case that artists tiptoe around.

The practical impact depends on what you need out of terrain today. The announcement calls it a “novel architecture” (Scaaaary words) and keeps it at the overview level, so details like feature completeness, interchange expectations, and performance characteristics remain a guesswork.

PCG gets edits without losing the recipe

5.8 Preview also updates the PCG framework to allow manual edits directly on procedural output while keeping the underlying procedural logic intact. That matters because it targets a classic production pain: the moment an artist has to hand fix something and the whole setup turns into a one way bake.

In plain terms, you can push results around without instantly severing the link back to the graph. The sources describe this as an improvement alongside other iterative changes, but they do not specify which nodes, asset types, or editor workflows get the most love in this Preview.

Vegetation: more biology, more Nanite, more questions

The Procedural Vegetation Editor receives significant enhancements in 5.8 Preview. The goal here is building high quality, biologically correct, Nanite ready vegetation assets directly inside the editor. The sources also say you can import meshes from external DCC tools, which points at less time spent rebuilding base shapes just to satisfy an in engine authoring workflow.

Currently, we are about to get the following features:

• Growth Node
• Seed Generation
• Skeletal Extraction from 3D Mesh or 2D image/Atlas
• Foliage Grafting
• Object Avoidance and Carving
• Trimming- branch loops, displacement tessellation
• Mesher Improvements
• Visualization Modes
• Trunk Material Compositor

Real world artists will appreciate that this tool stays honest about what it is trying to do. It aims at fast iteration and authoring inside the editor, not at replacing dedicated plant tools overnight. The community replies in the same thread also report issues and broken behaviors in specific cases, which fits the Preview warning label. Treat it as a sandbox build, not as a deadline build.

MetaHumans scale up, and they get less picky about input meshes

Crowd work gets a bump through the MetaHuman Crowd plugin. The sources describe scaling from tens to thousands of characters for populating realtime worlds. If you have ever tried to sell a crowd shot without a crowd system, you already know why that matters.

On the creation side, the Preview also expands the ability to transform almost any human mesh into a MetaHuman, now with simultaneous head and body conforming. Epic Games calls this as a workflow improvement, but the current sources do not spell out constraints, quality expectations, or edge cases for stylized characters.

Lights, rigs, faces, and a grab bag of everything else

MegaLights reaches full production readiness in 5.8 Preview. Control Rig Physics moves to Beta, and the face rigging and morph target editing tools expand to support in editor sculpt driven facial workflows and shot sculpting. The sources describe this as strengthening blend shape authoring for stylized characters, custom skeletal meshes, and MetaHumans, plus pose corrections.

Rigging also gets Direct Mesh Controls, an Experimental system that lets Control Rig controls sit directly on sections of a skeletal mesh. If you like your controls where your hands are, that sentence probably reads like a small miracle.

Past the hero items, the Preview notes further work across production rendering and virtual production workflows, plus updates to Dataflow and Chaos Physics.
https://forums.unrealengine.com/t/unreal-engine-5-8-preview/2721597

The post Unreal Engine 5.8 Preview rolls in first appeared on DIGITAL PRODUCTION and was written by Bela Beier.