For those who don’t know the tool: Stylized Tree Asset Generator is a Blender Geometry Nodes based tree builder for stylized environments, with Eevee focused shading and toolsets that also run in Cycles.

Pines, at last, for people who hate needles

Stylized Tree Asset Generator now includes a dedicated Stylized Pine Tree Asset Generator as part of its 2.0 update. The new pine toolset comes with new assets, textures, shaders, and materials, and keeps the same general workflow as the original tree generator to stay consistent.

The update also targets speed and housekeeping. Version 2.0 replaces deprecated nodes from Blender 4.2, optimizes UV storage, and cleans up and optimizes the Geometry Nodes setup. It also adds directional control to the wind feature and ships an updated user guide.

If you were already using the original generator for quick background dressing, the pine addition is welcome because it expands the library beyond broadleaf shapes and lets you cover the classic stylized use case: conifers in midground forests, mountain ranges, and gamey dioramas without modeling individual branches by hand.

What it actually builds and how far you can push it

The core promise is a Geometry Nodes setup that lets you shape trees quickly, then dial resolution up or down depending on what you need. You can go from low poly silhouettes to more detailed results by adjusting resolution and density inputs, keeping a tighter leash on polygon count.

The tool generates automatic UVs so you can bake textures. That makes it easier to take a procedural look, commit it, and move on, whether you need a static asset for a library or a one-off hero tree that still has to survive export.

It also supports using your own mesh to shape the leaves. That is the escape hatch for people who like procedural trunks but want art-directed foliage shapes, or who already have leaf cards and want the generator to place them. There is also a Random Generator input intended to produce infinite variations with similar characteristics. In practice, that is the difference between a forest and a cloning accident, especially when you need dozens of trees that read as a family but do not look copied.

Some of the shading work targets Eevee. The product notes say the shading was designed in Eevee and may not work as intended in Cycles by default, while the rest of the tools work in both render engines. So if your pipeline leans on Cycles, expect to tweak materials rather than treating the lookdev as drop-in.

Presets, shaders, normals, and the parts you will actually notice

Stylized Tree Asset Generator includes preset textures and materials aimed at getting you to a usable look quickly. It lists 10 leaf texture presets, 16 trunk presets, and 12 hand-painted procedural leaf textures. Those sit alongside procedural textures that remain adjustable, so you can keep the preset as a starting point rather than a locked style.

For shading, it includes a custom toon shader for the trunk and two shading groups for leaves, one designed for simpler use and one offering deeper controls. It also includes four sets of custom normals meant to help you land the shading style you want and to keep shading stable when you animate wind and use the scatter tool.

The update also keeps the wind feature in the toolbox, and adds direction control. That matters because wind without direction tends to look like your trees are trying to shake off a bad rig. Directional control lets you line up motion with camera moves or scene beats, instead of getting random flapping.

This is also where teh usual production advice applies: test it in a real shot, with your real render settings, before you roll it into a template file and wonder why the farm hates you.

Compatibility and versions

The newest versions of the tool are made for Blender 4.2 and newer, while still including older versions of the tools as far back as Blender 3.3. If your studio sits on a locked version for a show, that matters, because it suggests you can still run a supported variant without forcing an upgrade mid-production. The 2.0 update specifically calls out node maintenance aligned with Blender 4.2, including replacing deprecated nodes and cleaning up the node graphs. That kind of update tends to be invisible until it is missing, at which point your node tree becomes an archeological dig.

Pricing and the temporary deal situation

Pricing is tiered on Superhive Market. A Standard License is listed at $12.50 and includes textures, shading nodes, geometry nodes, and tools. An Asset Pack Standard License is listed at $16.50 and adds the full asset pack. A Commercial Use option is listed at $42 and includes the asset pack while allowing commercial use.

If you are evaluating it for production, the practical move is to grab it, build a handful of trees that match your show style, bake what you need, and push them through your actual export and render path. Then decide whether it becomes a staple, a one-off, or a neat toy that lives in a personal toolkit.

https://superhivemarket.com/products/stylized-tree-generator

The post If you yearn for the pines, go Blender 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: 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.

For those who don’t know the tool: MoonRay is a production path tracer with a USD Hydra render delegate for tools using OpenUSD, positioned in rendering and lookdev next to ASWF staples like OpenColorIO.

The Academy Software Foundation has added MoonRay as a hosted project, keeping the renderer under foundation governance while opening contributions to a broader community. DreamWorks Animation developed MoonRay as an open source production path tracing renderer and has used it on every one of its feature films since 2019, including The Wild Robot and The Bad Guys 2. The project uses the Apache 2.0 license and is developed in C++.

MoonRay includes support for distributed rendering and a pixel matching XPU mode that processes bundles of rays on the GPU as well as the CPU. It also includes bundled path tracing and a USD Hydra render delegate for integration into content creation tools that support the OpenUSD standard, which should make interactive preview workflows less of a custom science project in teh average pipeline.

The ASWF angle

MoonRay now sits alongside other hosted efforts in the ASWF roster, including OpenEXR, OpenVDB, OpenTimelineIO, and Open Shading Language. If your facility already treats OpenColorIO as plumbing, this is the same neighborhood.

For contributors, the project points developers to openmoonray.org and to the ASWF Slack workspace for a MoonRay channel at slack.aswf.io. Documentation is published at docs.openmoonray.org, and the source repository lives under the OpenMoonRay organization on GitHub.

Keynote season meets SIGGRAPH season

ASWF Open Source Days runs in Los Angeles on July 19 to 20, 2026, and the schedule aligns with SIGGRAPH 2026 timing. The keynote comes from DreamWorks Animation CTO Bill Ballew, with a talk titled How to Train Your Renderer: MoonRay’s Journey from DreamWorks’ Dragons to the ASWF.

The event listing describes July 19 as the main program day in Los Angeles, followed by July 20 as a full day of open source Birds of a Feather sessions within SIGGRAPH. The Call for Proposals remains open through May 24, 2026, via the Open Source Days event site.

As always, test new tools and new governance setups before you bet a production schedule on them, even when the feautres list looks exactly like what your render wranglers asked for.

https://openmoonray.org/

https://www.aswf.io/

The post MoonRay Renderer joins ASWF as hosted project first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Scene Auditor Pro is an add-on for Blender scenes that inspects datablocks and dependencies, then supports cleanup before export to Unreal Engine or Unity.

The Outliner is fine until it is not

Big productions rarely die from a single catastrophic mistake. They usually drown in tiny leftovers. Unused meshes that never got purged. Materials duplicated by imports. Textures that ballooned from sensible to cinematic for no reason. A scene that used to open instantly now takes a long sip of coffee before it even shows you a viewport.

Scene Auditor Pro positions itself as a response to that slow creep. The add-on builds a logical dependency graph from scratch rather than relying solely on the Outliner. It aims to show how objects, meshes, materials, textures, collections, and datablocks connect, so cleanup stops being a guessing game and becomes a decision.

A dependency graph that treats everything as suspicious

Scene Auditor Pro puts dependency visualization at the center: The add-on visualizes relationships across core Blender elements and linked datablocks. The point is not another pretty node view. The point is to make it obvious what is actually connected to what, and what sits alone, because orphaned and semi-orphaned data rarely announces itself. It hides in files as technical debt, and then turns up later as longer load times, higher memory use, and render slowdowns that feel impossible to diagnose.

Orphans, duplicates, and the usual suspects

The add-on includes orphan datablock detection. It calls out hidden unused meshes, materials, textures, actions, node groups, and datablocks as targets for discovery before they inflate file size and memory usage. That matters, because Blender files often accumulate leftovers in those categories during iteration.

Scene Auditor Pro also includes duplicate material and texture detection. The feature is a way to detect repeated assets across large scenes and identify opportunities to reduce unnecessary duplication. This targets common scenarios like kitbash heavy scenes, imported ArchViz content, and large environment work where the same texture set can show up under slightly different names and quietly waste memory.

The tool also looks for oversized texture maps and texture heavy materials as slowdowns – to surface the heavy hitters fast, including visibility into the largest assets and memory heavy elements. One of the claims is that it helps identify the real reasons scenes become slow or bloated, which stays in the realm of a marketing claim until you validate it on your own scenes.

Some parts read like a checklist of production annoyances, including unknown dependencies that make cleanup risky and heavy scenes with unclear bottlenecks. That is a pretty accurate description of Tuesday in many studios.

Export prep for engine pipelines

Scene Auditor Pro is part of pipeline and export validation duties, for Unreal Engine pipelines and Unity exports, plus ArchViz workflows, production cleanup, and scene handoff preparation. The theme here is less about pure Blender housekeeping and more about making sure scene data stays sane when it leaves Blender.

It also looks for missing UV maps or oversized textures as issues that can break game pipelines. If you do a lot of handoffs, the idea of seeing dependencies and unused datablocks before export can save time, or at least give you a clearer explanation for why a scene behaves badly.

Auto optimization, with a lot of caution tape

The add-on offers a step by step auto optimization approach with backup, emphasizing asset safety. It advises running auto optimization multiple times for best results. It also says that the tool will not touch data without explicit user action, and it describes multiple safety nets, transparency about what will happen, and reversibility through undo methods.

Those safety statements set expectations properly. Cleanup tools can be the fastest route to a broken scene if they run without restraint (Almost as bad as letting an AI agent loose). Here, the add-on leans into a safety first posture as a design goal, even if you will still want to test it thoroughly on duplicates of real production files.

Availability and pricing

Scene Auditor Pro is offered via Gumroad for 15 USD.

https://tarulahsanbd.gumroad.com/l/SceneAuditorPro

The post Scene Auditor Pro targets Blender bloat 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 topic: Blender is a DCC with the Cycles renderer. The new texture cache sits in Cycles rendering performance, alongside existing memory and render speed controls.

The problem it aims to fix

Texture-heavy scenes can burn memory fast, even before you hit your sample count. The new texture cache in Cycles targets that pressure by changing what gets loaded at render time, and how. The core idea: instead of pulling full image textures into memory, the system loads only the tiles and resolutions actually needed for the render. That means the renderer can avoid carrying the entire source image when the shot only uses a fraction of it, or when the texture resolves to a smaller mip level in-frame.

This is a straight-up memory efficiency play for scenes that rely on lots of image textures. Claims about the size of the improvement exist, but specific benchmark numbers and test conditions are very difficult, because it wholly depends on your scene – so test before using it in production!

.tx files, generated next to your textures

Cycles Texture Cache generates a matching .tx file for each image texture and places it in a blender_tx folder next to the source image. The .tx file stores the texture in a form optimized for tiled access and multi-resolution loading, so the renderer can pull only the tiles and mip levels it needs.

# Generate tx files for all images in a blend file.
blender scene.blend --command maketx
# Generate tx file for a specific image file.
blender --command maketx image.png --colorspace sRGB

The workflow aims to stay mostly invisible. The .tx files regenerate automatically when the source image changes. Cycles also infers settings such as color space and filtering based on how the image gets used in shader nodes, rather than forcing artists to maintain a parallel set of cache settings by hand. That last part matters for production sanity: texutre caching that requires constant babysitting tends to get switched off right before deadline.

CPU, GPU, and the day-to-day reality check

The feature is working across CPU rendering and all GPU backends. It is also already available in daily builds, with additional improvements planned for render farms and production pipeline use.

If you manage shared storage, you will care about where those .tx files live, who writes them, and when. The currently accessible details do not fully spell out a studio-grade policy story for cache location, locking, or multi-user coordination. Still, the direction is clear: get memory use under control without turning texture management into another job title.

Schedule, availability, and pricing

Blender 5.2 LTS is in alpha, with a full release expected in July. Pricing is the same as always for Blender – free and Open Source. Before you roll this into a show, test it on your own shots, your own storage, and your own farm tooling, because new caching systems love to surface edge cases at the worst possible time.

https://code.blender.org/2026/05/cycles-texture-cache/

https://developer.blender.org/docs/release_notes/5.2/

The post Blender 5.2 LTS targets texture-heavy renders first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Character Control Rig targets a very specific pain point: imported MetaHuman bodies inside Blender look like a rig, feel like a rig, and still do not behave like an animator-friendly rig. The add-on generates a Rigify control rig for an existing MetaHuman skeleton in Blender. The workflow starts with a generated metarig that snaps to the source skeleton using an automatic matching process, then moves to a one-click control rig generation step that binds the controls to the original skeleton and hooks into the existing MetaHuman evaluation stack. In other words, it tries to turn a MetaHuman import into something you can actually pose without getting another carpal tunnel.

Requirements

There are three requirements: Blender 4.5.0 or later (tested through 5.1), the Character DNA add on installed and enabled, and Rigify enabled in Blender preferences. If your studio-standard build is earlier than Blender 4.5, that becomes the first pipeline discussion. If Rigify stays disabled in your templates, the add on does not magically enable it for you.

The UE 5.7 detour is the retargeting trick

The workflow takes motion-capture-style animation from Mixamo, retargets it onto MetaHumans in Unreal Engine 5.7, then moves the results into Blender to animate on top of FK controls. Unreal Engine 5.7 matters here because the workflow uses retargeting features new to 5.7, including templates for popular skeletons. Unreal is basically selecting a Mixamo template for the source skeleton by reading bone names and matching them to the template, then retargeting it to each MetaHuman body.

The tutorial creates two MetaHuman characters with slightly different skeletal proportions, retargets the same animations onto each, and exports per character animation assets. This is the part where you should assume nothing and verify everything, especially if your show already standardized on a different Unreal point release.

Blender side, you get a metarig first and control rig second

Once the MetaHuman DNA files exist, the tutorial imports the characters into Blender via the Character DNA add on, then uses Character Control Rig to generate Rigify rigs per character. The add on exposes view options that let you turn off rig logic evaluation on head and body components and toggle related elements like RBFs, texture masks, shape keys, and bone transforms. It then lets you choose a rig framework. The tutorial states that it currently supports Rigify only, while the design leaves room for other rig frameworks later.

From there, the add on generates a metarig on the selected rig instance. It is snapped into position and fitted to the bones, with manual adjustment available before committing. After that, generate control rig produces a functioning control rig that updates while RigLogic evaluation runs. That is the core pitch: two clicks and you are ready to animate. Yes, that is a marketing claim, and you should still budget time for checking deformation, constraints, and naming collisions.

The multi-character part matters too. The developer says each rig is namespaced to avoid collisions, and the tutorial demonstrates generating separate rigs for two characters with different proportions using an auto snapping algorithm. Somewhere around here, your anmiation lead will ask if the rig behaves predictably under shot specific scale hacks. The only honest answer is to test your own worst habits.

Getting motion onto the FK controls

The tutorial imports body animations from Unreal into Blender and bakes them onto FK controls for the Rigify rig, using the Rigify tools for FK IK switching and baking from FK to IK in actions.

Animation support includes face board import from Unreal to Blender, face board export from Blender to Unreal, and body FK import and export in both directions. It also lists body FK auto retargeting from animation marketplaces, but that feature does not appear in the material we could find.

The add on also positions face board animation export as a direct path from Blender to the MetaHuman Control Rig in Unreal Engine. If you live in Sequencer, this is the part you will care about: you can keep your final runtime character in Unreal while still doing keyframing and clean-up work in Blender, then round-trip the result.

Pricing

An individual perpetual license is at $29.99 and team licenses starting at $99.99. The Character DNA Addon page does provide specific pricing. Since you also need the Blender Character DNA Addon, you’ll also need an Individual license at $79 one time and an Indie Dev Team license at $259 one time, with platform support for Windows, ARM MacOS, and Linux. The code for the addon is available on GitHub, while separately describing a purchasable build tool workflow and a compiled module related to the bone auto fitting algorithm. Depending on how you want to add all of it to your specific pipeline.

So plan for two purchases if you start from zero, and confirm licensing terms in your legal review before you roll it into a studio wide tools image.

What to test before you trust it on a deadline

Rig generation pipelines fail in predictable ways, and none of them care about your delivery date. Test how the generated Rigify controls behave under layered animation, constraints, and shot specific offsets. Test export and re import with your exact Unreal project settings. Test a multi character scene with your usual naming conventions and collection layout. Test any facial workflow claims with your real range of motion, not a polite demo clip.

https://www.polyhammer.com/character-control-rig-addon

The post Poly Hammer brings MetaHumans to Blender Rigify first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Project Falcon is a free, browser-based 3D modeling tool built around kitbashing, meaning you assemble models from a library of parts instead of building everything from scratch. It targets fast, hard-surface blockouts like vehicles, spaceships, and furniture and all sorts of blocking-relevant greeblies and assets, and it keeps the barrier low with no local install.

Autodesk positions it as a technology preview and frames it as an easy on-ramp for first-time creators, while still offering a path into professional pipelines through export. The tool runs in a web browser and saves work to a dedicated cloud space tied to your account. You need an account to use it, and the best browser experience comes with Google Chrome.

Thousands of parts, plus snap, mirror, rescale, and booleans

The core workflow starts with dragging parts from a built-in library into the viewport, then snapping them together. The library spans thousands of parts, from simple forms to detail pieces like bolts and wheels. You can mirror and rescale parts, and you can use parts to perform simple Boolean operations on the model.

This keeps the tool focused on fast shape exploration rather than slow final-topology chores. You can rough out a silhouette, punch vents, and keep iterating without worrying about building a full modelling stack inside the browser. At this stage, Project Falcon stays firmly in modelling, not surfacing. Though you can color the result, and apply a few basic materials and shaders. Making it pretty enough for the Art Director, so to speak. Bonus Points if you only use Pantone Colour of the Year shades, and wear a beret during dailies.

USD and STL: the handoff story

Project Falcon exports models in USD for use in other 3D content creation tools, and it also exports STL for 3D printing. The export angle aims at handing off a kitbashed blockout into a more traditional DCC for refinement and look development.

The Autodesk messaging is this: Project Falcon focuses on assembling geometry, while traditional tools provide full manual control. It also states that look development does not happen inside Project Falcon, so you export to another tool if you want to shade and light properly.

In practical terms, USD export goes for workflows where you want to keep the blockout moving: concept design, early asset ideation, and quick geometry bases that you might later rebuild or retopologize for games. If your pipeline already leans on USD interchange, the export choice keeps the door open.

What it is not, yet

Project Falcon currently does not include look development. The exported result is geometry, and the tool stays centered on kitbashing and basic assembly operations.

As a technology preview, it also comes with the usual realities: the scope targets defined supported workflows, it may change over time, and there are no commitments or warranties stated for this phase. Autodesk also points users to an ideas forum for feedback and feature requests. Still: Project Falcon is free. Access happens through a browser with an account, and no installation is required.

Production reality check

Even when a tool is free and fast, test it before you let it anywhere near a real prdouction schedule, especially if your handoff depends on specific USD conventions, naming rules, or downstream shading expectations.

https://www.autodesk.com/solutions/media-entertainment/project-falcon

The post Autodesk launches Project Falcon first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: KitBash3D sells themed 3D asset kits and delivers them through Cargo, with downloads for DCCs like Blender and engines like Unreal Engine.

A set dressing kit that actually knows set dressing

KitBash3D just shipped Lights, Camera, Action!, a 3D asset kit built around the behind the scenes world of filmmkaing. You get sound stages, grip gear, light stands, sandbags, and monitors intended to sell the idea that something got shot here, even if it was just your previz. The kit has 139 models, 112 PBR materials, and a total poly count of 6.3 million. If your scene still feels empty, you can now add more stuff that looks expensive, without having to explain why your hero prop budget went to folding tables.

Here’s part of the set:

• Apple Box: The ancient on-set unit of measure. Also the quickest way to “fix” an eyeline without touching your camera solve. Actor ego not included.
• Dark Apple Box: Same apple box, but in “this has seen things” edition.
• Bathroom Toilet: For those hero shots where the realism budget includes plumbing. Also useful for sim reference when compositing a bad day.
• Boom Microphone: The object your roto artist will definitely have to paint out, no matter how many times someone promised “it’s out of frame.”
• Box Truss Scaffolding: Because every virtual set needs at least one structure that screams “temporary,” even when it will live forever in a master scene.
• Camera Tripod High: The “we swear it’s locked off” rig that still mysteriously jitters just enough to ruin your matchmove.

• Chroma Stage: Your favourite shade of green, now available in “why is the spill that colour” format.
• Clapperboard: Classic clapperboards, which the onset personnel always mark in unintelligible handwriting, and VFX always tries to read like it’s a 20-times AI-translated-OCR-enhanced ancient manuscript.
• Coffee Cup: Continuity’s greatest enemy and the comp team’s most common set extension.
• Coffee Trailer: The real production hub. Put it in your scene and everyone instantly believes there was crew there.
• Dolly Rails: For that smooth move you will still stabilize because somebody stepped near the track.

• Extended Camera Crane: When the shot needs to feel expensive, even if the environment is still a greybox.
• Film Light: A two-lamp unit that screams “stage,” and whispers “watch your speculars.”
• Foam Core Boards: The poor person’s bounce, now available as a rich person’s render asset.
• Frosted Donut: The snack that disappears between cuts. Perfect for continuity tests you will fail on purpose.

• Frosted Donut B: A second donut, because the first one was “too pink in the grade.”
• Gray and Chrome Ball Rig: VFX’s emotional support spheres. Put them anywhere and suddenly you’re doing “proper” on-set reference.
• Macbeth Chart: The colour chart that politely reminds everyone that “we’ll fix it in post” still starts on set.
• Production Slate: The clean slate version, for when you want the prop without the handwriting crimes.

Unreal gets the game ready treatment

For Unreal Engine, the kit gets a Gameplay Ready variant with full Nanite support, custom collisions, Packed Level Instancing, and modular runtime ready assets. If you have been building virtual sets and thinking, this needs more realistic cable chaos, congratulations, you have found your people.

In practical terms, it is also a tidy addition to any kitbash workflow where you want believable production context around your hero environment, not just more neon signs and wet asphalt.

Formats, DCCs, and the inevitable renderer bingo

The supported software list includes Blender, Unity, Cinema 4D, Maya, 3ds Max, and Houdini. On the interchange side it calls out FBX, OpenUSD, and MaterialX. Renderer logos shown include Arnold, Cycles, Karma MatX on Houdini, OctaneRender, Redshift, and V-Ray.

Pricing, licensing, and the fine print you should still read

The product page lists a price of $95 and a current price of $47.50. It also shows three license tiers: Individual License for self-employed artists, Small Business License for companies with 50 or fewer employees, and an Enterprise License tier for companies with 51 or more employees. So far, we can see now discounts when you own some of the stuff in real life.

As always, test any new tools and assets in your pipeline before you let them anywhere near a real delivery, especially if your project depends on strict naming, instancing, and performance budgets.
https://kitbash3d.com/products/lights-camera-action

The post FilmSet kit lands in KitBash3D first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Raffael Kloten has released Tire Rig Generator, a free Blender plug-in designed to automate one of those vehicle-rigging jobs that everyone needs and nobody sane wants to do manually: making tires deform under load. The tool automatically creates and skins a complex tire rig that can handle pressure and surface deformation for almost any tire.

The workflow is built around three inputs. Users provide the plug-in with the tire mesh, a low-poly deformer mesh and a ground mesh. Tire Rig Generator then generates a rigging solution adjusted to the tire. In practical terms, the tool targets vehicle setups where contact deformation, weight and pressure response help sell the object as something with mass, rather than a decorative rubber doughnut spinning through space in heroic denial of physics.

Single Empty control and radial rig design

The generated tire rig is controlled via a single Empty, which keeps the main animation control compact instead of scattering handles across the rig like someone lost a toolbox in Blender’s outliner. The setup also provides easy access to the control meshes, so artists can inspect or adjust the deformation system without digging through a rig structure designed by a sleep-deprived octopus.

The rig is radially designed, matching the circular structure of a tire rather than forcing a linear rigging setup onto a round object. It is also prepared for ground deformation and tire pivoting, which makes it relevant for shots where the wheel needs to compress against a surface, rotate believably around its contact area or react to vehicle weight.

Pressure, contact and deformation

The main feature is automatic rig creation and skinning for tire deformation. Kloten describes the tool as capable of handling pressure and surface deformation.

This matters because tires are a small detail until they are wrong, at which point the entire vehicle suddenly looks like it is hovering on four decorative bagels. For shots involving cars, trucks, tanks, sci-fi vehicles, off-road setups or stylized mechanical animation, believable contact deformation can add weight without forcing artists to build a custom rig for every wheel.

Availability

Tire Rig Generator is available as a free download via Gumroad. The available public information says the download includes documentation.

Tire Rig Generator on Gumroad

The post Free Tire Rig Generator for Blender Automates Tire Deformation first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The pitch: graphs, not layers

ArcBrush builds images in a node graph. You wire inputs into operations and wire the result into exports. The app focuses on non-destructive editing, with parameters staying live so you can adjust a pipeline long after the first export. The core editor is free to download and use, and it does not require an account for non-AI work (Oh, blessed 2026, when this is a mention-worthy feature of a software….) . It runs as a native desktop app written in C++ and works on Windows and macOS. Linux coming soon.

If you live in node land already, the concept will feel familiar. The difference here is that the output target is mostly 2D deliverables: icons, sprites, UI variants, texture maps, and piles of formats that someone will ask you to regenerate five minutes before lock.

Node count, node types, and the day job stuff

The app has 75 composable node types and type-safe connections that prevent invalid wiring. It also brings five pin types, separating images, masks, palettes, and variants so the graph can validate what you connect.

A lot of the feature list reads like it came from someone who has rebuilt the same export stack too many times. There is auto save with crash recovery. There is a minimap, node search, undo and redo, node groups, per node notes, and sticky notes.

The preview tooling targets production rather than marketing . You can lock the preview to any node output, zoom deep with a pixel grid, inspect RGBA values, isolate channels, and view a live histogram overlay. For monitoring consistency, the app reads your monitor ICC profile and applies correction so the display matches exports via display color management using the monitor profile from the International Color Consortium. Test that on your own display chain, especially if you work across multiple calibrated panels, because colour surprises are lovely… .

On the output side, there are single-image exports and batch exports. Export Batch can produce named files per palette variant, or pack variants into a single sprite sheet PNG while also writing a TexturePacker compatible JSON manifest. Export nodes also support relative paths, and the app can create directories automatically when exporting.

Pixel art and texture helpers, without pretending to be a full DCC

The feature goes for game art and texture workflows, but it stays in 2D territory. There are pixel art oriented nodes like Pixelate, Outline, Dither, Quantize, Palette Remap, and sprite sheet export. Dither lists Floyd Steinberg, ordered, and blue noise options.

For texture work, the app includes Seamless Blend to make images tileable, Noise and Pattern nodes for procedural bases, Tile Preview to check repetition, and a Normal Map node that generates lighting maps from grayscale. This is not a replacement for a full material authoring suite, but it covers the everyday prep-and-iteration loop where you need quick variants, quick tiling fixes, and quick exports without babysitting layers.

If you spend time in texture painting or material prep, the most interesting claim is the pipeline idea: build the graph once, then regenerate every variant and export target when the source changes. That includes a Watch File toggle on input nodes that reloads when the source file changes on disk. The page even spells out a simple case: edit in Photoshop and see the result live in ArcBrush. That makes it less of a walled garden and more of a graph-driven post station for assets.

OpenCV processes images on CPU and GPU, and OpenGL renders previews. For SVG import, it rasterizes via ThorVG. None of that guarantees performance on your particular workstation, but it does clarify that the app aims for native processing rather than another browser wrapper.

Optional AI nodes: credits, cloud, and knobs you can count

AI features are optional. The app has AI cloud based nodes that only reach out when you use them, while the rest of the graph runs locally. There are nodes for text to image, image edit with text instructions, background removal, and 4x upscale powered by AuraSR. It also has differnet models, including FLUX variants and Nano Banana 2 for text to image and editing.

Pricing for AI is a one time credit packs with no subscription and credits that never expire. The packs listed are Starter at $10 for 350 credits, Plus at $20 for 800 credits, and Pro at $40 for 1800 credits. The site also states 10 free credits on signup. Credit costs vary per model and task, and at standard resolution up to 1024 by 1024.

That setup makes it easy to budget AI usage as a production expense, but it also adds a network dependency for those nodes. Treat it like any other external service: check availability, latency, and whether cloud processing fits your client and studio rules. Or if the bubble already burst, and you need to rewire things to the little Docker Server you have in your Cupboard that replaces all the Hype…. If you only want the node graph editor, you can ignore AI completely and still use the full non AI toolset.

Where it fits if you already have node tools

Node based workflows already dominate compositing and lookdev, so the real question is whether a dedicated 2D node graph editor reduces friction compared to existing tools. ArcBrush positions itself as a build once and export everything machine: variants, palettes, batch exports, sprite sheets, and texture prep steps chained together so you can re run them on demand.

First, when you need to ship a lot of consistent variants, like tiered item icons, UI colorways, or platform specific asset sets. Second, when you need to keep a process editable after the first deliverable, because late changes rarely arrive in a neat package.

Reality check before you bet a deliverable on it

ArcBrush looks designed for artists who want node graph control for 2D assets and textures without living inside a heavyweight suite. The free core editor and the explicit credit pricing for AI lower the barrier to testing (Which we’ll do after FMX) , and the node count and export features cover a lot of common production chores.

Still, new tools and innovations should be tested before use . Put it on a few real assets, run it through your team review loop, and see whether teh graph model actually reduces mistakes compared to your current wokrflow.

ArcBrush is available as a free download from the product site, with documentation hosted on the docs portal and community links including Discord.

https://arcbrush.com/

The post ArcBrush turns image editing into a node graph first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: KeenTools makes tracking plugins for Nuke, Blender, and Adobe After Effects. The new GeoTracker for SideFX Houdini sits between matchmove and FX layout, and it runs as a SOP node in OBJ and Solaris.

Houdini gets geometry first tracking

GeoTracker for Houdini runs as a native SOP node inside Houdini and works in both OBJ and Solaris contexts. The tool targets geometry based object tracking and camera tracking from 2D footage, with the goal of keeping the full workflow in the Houdini scene rather than bouncing to a separate tracking app.

The core interaction stays intentionally direct. You align an imported or scene built 3D model to the filmed object, then use viewport pinning to keep that object stuck to the plate while the tool reconstructs motion across the shot. That tracked geometry can then feed downstream Houdini work where it actually matters, like driving FX timing, layout, and interactions.

If you already treat layout as the first FX department, this kind of geometry tracked handoff can save a lot of back and forth. It also means you can keep shot scale, scene units, and the rest of your Houdini context consistent, instead of trying to trcak down why a solve looks fine in one app and wrong in another.

Camera solves, lens guesses, and the boring parts

Alongside object motion, the Houdini beta supports camera tracking by aligning static objects or environment models, including LiDAR style environment meshes. It also includes focal length estimation for cases where camera parameters are unknown, plus zoom tracking to follow focal length changes over time.

The Houdini integration also calls out camera import and export in both OBJ and Solaris contexts. That matters because camera plumbing can become the silent time sink, especially when a show uses Solaris for USD centric lighting and layout but still relies on OBJ context for parts of the FX build.

GeoTracker remains geometry based, so you need a 3D model to start tracking. That model can be anything you import or create in the Houdini scene. More detail can help, but extremely dense meshes can get heavy. The beta also includes Surface Masks to exclude parts of the model from tracking when occlusions or reflections would otherwise pollute the solve.

Beta reality check, installs, and pricing

The plugin ships as an open beta and it is free during that beta period. Each beta version stays valid for 30 days, with regular updates planned until a stable release is ready.

Installation stays old school by design. You drop the extracted package into your Houdini packages directory on Windows, macOS, or Linux, and Houdini picks it up. Updates and removal work the same way: delete the old files, replace with new ones, or remove them entirely. There is no auto updater for the beta yet, so you own the housekeeping.

System requirements keep the target clear: Houdini 20.5 or newer on 64 bit Windows, macOS on Intel or Apple Silicon, or Linux. The guidance for graphics hardware stays refreshingly unromantic: a decent GPU that can handle Houdini.

As always, treat new tools like you treat new render builds: test in a controlled setup before you bet a delivery on it, even if the demo looks clean.

https://keentools.io

https://keentools.io/products/geotracker-for-houdini

The post KeenTools GeoTracker enters Houdini open beta first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: VirtuCamera is a mobile virtual camera for realtime camera motion capture into DCCs via plug-ins for Blender, Autodesk Maya, Autodesk 3ds Max, SideFX Houdini, and Maxon Cinema 4D.

What VirtuCamera 2 actually is

VirtuCamera 2 turns an Apple or Android device into a six degrees of freedom controller for a camera inside supported DCC software. The app captures device motion and sends it to the host plug-in over a network connection, then records the move into keyframes when you hit record. It also streams the DCC viewport back to the device for framing while you operate.

The new release includes a redesigned user interface and a full screen viewport. It also adds an Android version alongside iOS, with live viewport streaming over Wi-Fi, capture and streaming at up to 60 frames per second, on device controls for playback and camera switching, focal length sliders, and the ability to scale camera movement for longer travel.

Supported DCCs and versions, now with fewer workarounds

The current plug-ins list the following versions: Blender 5.1, 5.0, and LTS 4.5, Autodesk Maya 2027 and 2026, Autodesk 3ds Max 2027 and 2026, SideFX Houdini 21, and Maxon Cinema 4D 2026.

If you live in mixed DCC land, this is the rare case where one handheld capture app claims first-party plug-ins for five major platforms at once. You still need to validate the exact DCC build and pipeline constraints in your environment, but at least the compatibility targets are stated clearly.

Viewport streaming, latency, and why tethering exists

VirtuCamera 2 streams the viewport to the device so you can frame from the phone or tablet. On paper, that reduces the whole remote monitor dance. In practice, the network decides how cinematic your day will be.

The tethering documentation spells out why. Wi-Fi can drop packets, jitter, or kill long connections due to congestion, roaming, power saving, and network restrictions even when normal browsing looks fine. The guide recommends tethering as a way to make the computer treat the phone as a wired network interface, avoiding Wi-Fi variability and often improving latency. USB tethering also commonly keeps the phone charging during use. If you have ever watched a handheld take turn into a stuttering mess at the exact moment the director liked it, you already know why this section exists.

There is also Ethernet tethering, described as plug and play across macOS, Windows, and Linux, assuming you use a USB to Ethernet adapter compatible with the phone so the device recognizes it as a network interface. Also, test this stuff before you trust it in production. Network quirks love showing up when they shouldn’t be there.

Scale settings, because meters are not a suggestion

VirtuCamera 2 includes a scale setting designed to map real world movement to DCC units. You need to establish how much 3D software units equal real world units. In the app settings, you set a value so that one meter in the real world matches the software units you choose.

That sounds simple, but it solves a recurring problem in virtual workflows: a physically reasonable move can become a microscopic nudge or a teleport depending on scene scale. Making this an explicit setting in the app puts the responsibility in the right place. You calibrate once per scene scale, then operate like you mean it.

If you work across projects with different unit conventions, write the chosen mapping into your show notes and keep it consistent. Otherwise you will spend an afternoon wondering why yesterday’s operator feels like they had longer arms.

Plug-ins, Python, and rolling your own integration

VirtuCamera’s official site shared the underlying Python module. VirtuCamera plug-ins for Maya, Blender, Houdini, Cinema 4D, and 3ds Max are based on the PyVirtuCamera module, and PyVirtuCamera uses FFmpeg for video encoding. PyVirtuCamera exists as a public repository on GitHub and a Python module API to create VirtuCamera plug-ins, with downloadable releases and a wiki for usage details.

This matters for two audiences. If you are a pipeline TD, a published API reduces the risk of being blocked by missing official plug-ins for your in house toolset. If you are a plugin developer, a shared module means feature parity across host DCCs depends on the same core, not five separate implementations drifting apart.

Somebody will ask whether this means you can jam it into anything. The official site says you can create your own plugin with the PyVirtuCamera Python API and that it does not need to be a DCC.

Pricing and availability

On the German Apple App Store and on the Google Play listing, VirtuCamera 2 is priced at 18€ currentl. On the US App Store listing, it is priced at $20. If you are evaluating total cost, also account for the time cost of validating networking, device mounting, and scene scale conventions. The app cost is rarely the expensive part.

https://virtucamera.com/

https://apps.apple.com/de/app/virtucamera-2/id6761327593

https://play.google.com/store/apps/details?hl=en&id=com.theweirdbyte.virtucamera2

https://github.com/theweirdbyte/PyVirtuCamera

The post VirtuCamera 2: The Weird Byte goes Android first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The pitch: stop keyframing the math

Physics-style motion looks simple right up until you try to animate it by hand. You want an object to arc, spin, fall, and land with a believable rhythm. Then you end up nudging curves, correcting timing, and trying to keep the rotation from looking like it came from a different universe than the translation.

NodeMonkey built Inertia around the idea that artists should steer intent, not equations. The tool targets Blender 5.1 and is a Geometry Nodes-powered add-on that handles the math and generates trajectories, rotations, and gravity-based motion. The claim is workflow first: fewer clicks, fewer editors, and less time spent hand-authoring the same ballistic arc for the hundredth time.

A free version is available, alongside a paid edition. Pricing is shown as €0+ so you can name your own price, and pay what you think is fair.

Three systems, three kinds of pain relief

The core of Inertia is three built-in systems, each aimed at a familiar animation task that tends to spiral into curve surgery.

Projectile Inertia focuses on launched objects. The tool includes an auto-aim function intended to help consistently hit targets. Think arrows, thrown props, or anything that needs to land where art direction says it must land, while still pretending physics had a say.

Orbital Inertia targets celestial mechanics. If you ever tried to keyframe orbital paths and keep speed and curvature consistent, you already know why a dedicated system exists for it.

Curve Inertia keeps objects locked to paths with gravity-like behavior. The examples called out include jet fighters and roller coasters, which is another way of saying motion that must follow a path but still feel like weight and momentum exist.

All three systems sit inside Blender 5.1 and lean on Geometry Nodes rather than external solvers or custom simulation frameworks. About a third of the way in, here is the small gotcha you should keep in mind: any tool that generates motion procedurally can hide complexity behind friendly UI. That is great until you need to debug. Test early, test with your real scene scale, and test with the constraints you actually ship, not the demo that came in the download.

Viewport prediction: the part you will actually use

The most practical feature is a real-time predictive curve drawn directly in the viewport. The idea is simple: see the path before you press Play. That means you can adjust aim and motion direction with visual feedback instead of running the timeline like a slot machine.

The same preview concept applies to both projectile arcs and orbital paths, displayed as a live line in the viewport. It is a small change that can save a lot of micro-iterations, especially when you work under direction that changes its mind three times before lunch.

The Sources also claim you do not need to know Geometry Nodes to use the tool. Instead, you adjust sliders for Gravity, Friction, and Speed without opening the node editor. That is the classic adoption strategy for node-based power features: give artists a clean control surface first, let the curious dig deeper later.

Practical notes for production brains

If you plan to use Inertia for shots, treat it like any new procedural motion system. Run a few stress tests with your real frame ranges and scene scale. Check whether the motion remains stable when you change FPS, time-warp, or hand off to another artist who needs to tweak the result without breaking the rig. Verify how the generated motion behaves when you render on the farm or upgrade Blender mid-project.

https://nodemonkey.gumroad.com/l/inertia

The post Inertia brings clicky physics to Blender first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Anthropic joined the Blender Development Fund as a Corporate Patron and the focus sits on Blender core development, specifically foundational work like the Blender Python API. Quoting: This support will be dedicated towards Blender core development, to maintain and continuously improve foundational features like the Blender Python API, which enables developers and artists alike to extend and improve the software for custom workflows.

Community reaction and the corporate reality check. E.a. Breathe, everybody.

This is the part worth re-reading when the next debate starts, because it will. Blender stays open-source. Donors do not own the code. The Foundation is still in charge of planning and review. And as far as Connectors and Corporate sponsors go, would you rather have Anthropic or TwitterAI?

Claude gets a Blender connector

And there is other news: The new Claude connector for Blender provides a natural-language interface to Blender’s Python API. It is positioned for scene analysis and debugging, generating scripts, and batch-applying changes to objects in a scene. It can also add tools directly to Blender’s interface by using the Python API.

This is also where the sarcasm is unsuppressible. The pitch sounds like a polite AI intern who reads the manual, writes your first draft of a script, and does not ask for access to your Perforce depot. In practice, it will do exactly what any code generator does: it will be useful right up until it makes one confident, catastrophic mistake that turns your perfectly fine scene into modern art. Test it before you let it anywhere near a deliverable.

Let’s test this together!

Digital Production author Alexander Richter will put the new connector through a first-look livestream on Thursday, the same day this news lands. The session runs at 2 PM UTC and leans into a raw test rather than a polished demo, with a quick install walkthrough using the uv package manager and then straight into hands-on scene work.

The stream title is I Let Claude AI Control Blender (Is it actually good?). Expect real-world poking at scene manipulation, lighting setups, and Python scripting, plus a TD-flavored sanity check on batch renaming, material assignments, and scene cleanup: where it saves time, where it trips, where it fucks up and where Python knowledge still separates a clean result from a slow-motion cleanup job.

MCP, or how to share the plumbing

The Blender connector is built on Model Context Protocol, an open standard for connecting AI models to external data. The connector built on MCP is designed to be accessible to other large language models, not just Claude. For pipeline folks, that is the important sentence. It frames the connector as infrastructure rather than a one-off plugin, making the integration story feel less like a lock-in play and more like a set of pipes you can reuse. Or at least, that is the marketing claim. Reality will show how it works.

Connectors everywhere, all at once

The same announcement releases “connectors” as a broader creative-work push. Listed integrations include Adobe Creative Cloud apps, Ableton documentation grounding for Live and Push, Autodesk Fusion, SketchUp, and live visual tools like Resolume.

In other words, the assistant wants to sit in the middle of your toolchain, translate between apps, and automate the stuff you do not put on your reel. Or, just, you know, read the documentation for you. If that sounds like an attempt to emrbace the creative industries, yes, that is the point. And if you already feel tired, also yes.

And if you think: “Oh, well, someone is running from the Trumpish-Industrialist grasps into the warm embrace of the creative world”, yes, that is what it looks like. Funny that the discussion about where the training data came from is not included in the messaging at all. But let’s see how Anthropic does on this side of the Copyright divide.

Pricing and availability

The sources describe the Blender connector as officially available for Claude and available now for Blender 5.1, with installation instructions hosted by Blender.

As always, treat new automation as a tool, not a teammate. Put it in a sandbox, throw ugly production scenes at it, and see whether it helps you ship faster or just helps you generate new kinds of bugs in new and exciting industreis.

https://www.blender.org/press/anthropic-joins-the-blender-development-fund-as-corporate-patron/

https://www.anthropic.com/news/claude-for-creative-work

The post Anthropic funds Blender, ships Claude connector first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: OctaneRender is a GPU renderer with DCC plugins like Blender, Cinema 4D, and Houdini. It ships via Studio+ and has a macOS stepsibling called Octane X.

Virtual textures, now allowed on the farm

OTOY shipped OctaneRender 2026.3 with a headline change that matters to anyone who has ever watched a heavy lookdev scene bully a GPU: network rendering now supports virtual textures. Virtual textures arrived earlier in the 2026 cycle, and 2026.3 extends that system beyond the local box so you can run the same approach in distributed jobs instead of treating it like a workstation-only party trick.

If your pipeline leans on huge texture sets, this is the kind of change that can reduce the amount of manual babysitting around what fits where. It does not magically fix bad asset hygiene, but it can remove one common excuse for why a scene behaves differently on an artist’s machine versus a render node. The release notes also call out a reduction in time to first sample in render nodes when scenes contain large image counts, which pairs naturally with the idea of texture-heavy shots that take too long just to begin doing anything visible.

One practical footnote: the release notes explicitly say that virtual textures are not supported for texture displacement. That line sits inside a crash fix description, but the constraint itself matters. If your assets rely on displacement driven by high-resolution maps, you still need to plan for the old reality there, even while the rest of the texture stack gets more flexible.

Trace sets, shadow catchers, and other production glue

2026.3 continues to sand down workflow edges around features introduced earlier in the 2026 line. Trace set visibility rules can now also apply to shadow catchers, which sounds small until you are trying to art-direct what reflects in what while keeping plate integration sane. Shadow catchers often sit at the intersection of lighting cheats and comp expectations, so anything that reduces the number of special cases usually pays back quickly.

There is also an update to USD import preferences: you can override point instances so they can be used to instance other external geometries. That is a very specific knob, but pipelines that move a lot of set dressing through USD tend to accumulate a lot of “why does this instance not behave like that instance” questions. Having an explicit override in the import preferences at least gives TDs another lever that lives in the tool instead of in an external patch script.

The same release adds support for importing float and colour primvars from USD curves, and it fixes an issue where motion blur was not visible when using USD curves. If you push curves for hair, cables, trails, or procedural motion guides, this is the kind of boring detail that stops being boring the moment it breaks a shot.

For readers tracking platform standards, this is another reminder that renderer updates are increasingly about interchange stability as much as raw features. You still want speed, but you also want fewer surprises when assets cross DCC borders.

MaterialX displacement support gets more real

The 2026.3 release adds MaterialX import support for displacement shader sub graphs. It also fixes a handful of MaterialX-related issues, including proper operation for TransformNormal and TransformPoint, errors when loading scenes with Time and Frame nodes, alpha blending in HexTiledImage for color4 outputs, and import issues around bi-tangent inputs that could break normal mapping.

If your studio has been treating MaterialX as “great in theory, wobbly in practice”, this is a concrete step toward the practical side. A step, not the finish line! Not even for Scandinavian Studios! It does not claim perfect parity with every other tool, but it does show attention to the unglamorous parts: node correctness, error spam, and consistent interpretation of common transforms. A separate behavior tweak affects anisotropy: rotation in Standard Surface now matches OpenPBR and other renderers, and existing scenes are not affected. Hopefully

NRC memory use drops, plus a grab bag of fixes

OTOY says memory usage has been reduced when using the Neural Radiance Cache, referred to as NRC. The same notes mention fixes for render artifacts when using volume media in combination with NRC, plus a crash fix when rendering starts while virtual textures compile and are used in texture displacement, with the earlier reminder that virtual textures do not support texture displacement.

There is also a long list of resolved issues touching a lot of interchange formats and stability landmines: fixes for Alembic loading with materials saved as non-constant FaceSet objects, multiple FBX importer and exporter issues around vertex attributes and vertex animations, crashes on unsupported or invalid SPZ files, and potential application crashes upon initialisation on Windows and Linux.

A small but very real quality-of-life fix: empty file name nodes no longer get replaced with the directory of the containing OCS file, and they stay empty. That is the sort of bug that creates invisible path issues that only show up in a farm run at 3 a.m. on a Saturday night, while you are trying to remember what these things called “Weekends” were, the strange people in the group called “Friends” on Discord are blabbing about. Random example.

Drivers, OS baselines, and what your IT team will ask

The release notes list two explicit minimums. The minimum NVIDIA driver version required is R555, and it is R572 for GeForce RTX50 series. The minimum version of macOS required is 14.5.

Lua API tweaks for pipeline tinkerers

2026.3 includes Lua API changes that target data handling and introspection. Several octane.node functions now accept raw C arrays for cases where the API expects an array, and there are new helpers for querying animator types and retrieving animator data as a raw C array. It also states that for non-array attributes, you are allowed to set animators with different channel counts from that of the attribute type.

If your facility uses Lua to automate scene setup, tool integration, or pipeline hooks, or just is full of Autohotkey-Nerds (My People!) these are the kind of changes that can reduce wrapper code and make scripts less fragile. It is not the most glamorous section , but it is often where studios quietly win back hours.

Pricing and availability

OctaneRender 2026.3 is available via downloads linked from the release notes, including standalone builds for Windows, Linux, and macOS, plus node builds for Windows and Linux, and demo downloads for Windows and Linux.

Pricing is subscription-based via Studio+. The OctaneRender Studio+ subscription is 24€ per month billed monthly, and 20€ per month billed yearly for an annual subscription. There is also an OctaneRender Offline USB Dongle for 49 euros.

Even if the feature list sounds perfect for your exact setup, treat it like any other renderer update: test it on your own scenes, with your own texutres, on your own farm, before you let it anywhere near a delivery schedule.
https://render.otoy.com/forum/viewtopic.php?t=85624

The post OctaneRender 2026.3 adds virtual texture netrender first appeared on DIGITAL PRODUCTION and was written by Manuel Kotulla.

For those who do not know the tool: Flow Studio is Autodesk’s current platform for AI-assisted character work and live-action integration, which was previously called Wonder Studio. In production terms, it sits somewhere between character generation, animation, and shot finishing. The idea is to let users bring CG characters into live-action footage with less manual prep than a conventional VFX workflow usually demands.

Autodesk has added AI Rigging and Neural Layer to Flow Studio, pushing the platform further from AI-assisted asset work toward a broader character performance pipeline. AI Rigging is available across all tiers, while Neural Layer is limited to paid tiers. Both features are used within Live Action projects and are meant to reduce the amount of technical wrestling required between “nice model” and “usable shot.”

That gap is where many AI workflows become oddly quiet (And it is a serious challenge not to link three dozen “AI driven startups” that are flodding our inboxes…) . Generating a 3D asset is relatively easy. Turning it into something that can move, light well, hold up in a close-up, and survive a handoff to the rest of the pipeline is where the actual labor starts charging rent.

Autodesk’s answer is to bundle rigging, motion transfer, neural enhancement, and export into a single workflow that promises speed without removing artist control. As usual, the practical question is not whether it works in a launch demo, but how much cleanup it causes five minutes later.

AI Rigging: automated setup for 3D characters

According to Autodesk, AI Rigging automates one of the more technical parts of character production by preparing 3D characters for animation with minimal setup. The company says users can turn 3D models into animation-ready characters in minutes rather than building or refining rigs manually through a traditional setup process.

Autodesk also says the resulting characters can be driven directly from video inputs, positioning the feature as a bridge between static 3D assets and motion-driven character performance. Once prepared, rigged assets can be exported to Maya, Blender, and Unreal for more advanced downstream work. Autodesk is making AI Rigging available across all tiers of Flow Studio.

Neural Layer: a neural rendering and enhancement stage

Neural Layer is Autodesk’s new rendering and enhancement component inside Flow Studio. While AI Rigging is aimed at character preparation and motion, Neural Layer is aimed at the look of the result. Autodesk describes it as a “faster and more accessible way” to push characters closer to cinematic output without having to leave the platform immediately.

The feature is intended to enhance realistic skin, hair, fur, and materials, while also adding more dynamic film-style lighting. Autodesk further says Neural Layer supports nuanced facial performance and micro-expressions, more grounded motion through improved AI mocap, and natural physics, cloth simulation, and compositing. Neural Layer is available only in the paid tiers of Flow Studio.

From asset generation to performance

Autodesk presents this release as the next step after Wonder 3D, shifting from static character creation toward animated performances. That matters because it changes how Flow Studio should be read in a production context. The platform is no longer being pitched mainly as a tool for generating a character asset or dropping a CG character into footage. It is increasingly becoming a character performance system that tries to cover more of the route from concept to finished shot in one place.

The company says users can still export scenes to their preferred DCC tools for manual refinement, or stay inside Flow Studio and use Neural Layer to accelerate the process. Autodesk wants the product to appeal both to experienced artists who still want Maya, Blender, or Unreal in the loop, and to users with less 3D experience who want a faster route to a somewhat polished result. Whether that balance holds up under production pressure is another matter, but at least the escape hatch is there.

Still, the technical direction is clear. Flow Studio now combines AI-assisted character preparation, video-driven animation, neural visual enhancement, and export to standard downstream tools in one package. For smaller teams and fast-turnaround productions, that is useful. For larger facilities, the more relevant questions remain the boring ones, which is usually a good sign: rig quality, cleanup time, motion consistency, interoperability, and how controllable the neural stage remains once a sequence stops.

Autodesk Flow Studio

The post Autodesk Flow Studio adds AI Rigging and Neural Layer for character workflows first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Headshot is a plug-in inside Character Creator 5 for turning photos or head meshes into rigged CC characters that can move on to Autodesk Maya, Blender, Unreal Engine, and Unity.

Two ways in: photo or mesh

Headshot now sits at version 3 and requires Character Creator 5. The tool targets digital humans built from either a single portrait or an existing 3D head model, with both paths ending in a fully rigged CC character ready for animation work.

The image workflow starts from a facial photo and runs through automatic 3D head generation plus topology and shape refinement, camera lens correction, normal map creation, and texture reprojection. The mesh workflow targets static head models and runs automatic head wrapping, mesh refinement, and texture baking. The same product page frames the mesh workflow as optimized for photogrammetry, sculpted assets, and mobile scanned models.

Both workflows chase the same goal: convert reference into a character that stays on CC topology so facial animation and downstream retargeting behave predictably. That matters more than the marketing word salad, because your rig cares about edge flow, not adjectives.

Image workflow: faster first pass, more knobs after

The image workflow focuses on building a likeness from a single portrait. Headshot 3 adds AI Image Enhancement tools described as head leveling, expression neutralization, lighting correction, stray hair removal, and 4K upscaling, all applied to source photo material used for the head build.

Headshot 3 also adds AI Image Generation, (text to image generation) with portrait images up to 4K resolution and side or full body images up to 2K resolution. AI Image Generation is powered by Google Nano Banana and requires credits for each generation. The same ecosystem also promises you can swap or replace textures after mesh changes, with texture reprojection that updates after mesh modifications.

For anyone who has ever tried to fix a face by nudging ten sliders and then regretted it on frame 180, Headshot 3 adds preset driven morphing on top. The version has 58 facial presets intended to enhance depth and highlight unique features, with an adjustable slider for fine tuning per applied preset. This is the part to pressure test early. New tools and innovations should be tested before use in production, especially when your deliverable lives or dies on a tight closeup.

Mesh workflow: wrap, sculpt, and keep topology honest

The mesh workflow centers on converting a static head model into a fully rigged CC character using head wrapping, refinement, and baking. It is positioned for turning scans and sculpts into animation ready characters while keeping CC topology.

Headshot 3 adds a spline based reshaper that supports portrait and profile views for alignment of features such as double eyelids and nasolabial folds, described as enabling more accurate facial animation. As well as Bezier controls for refining front and side profiles, with granular adjustment aimed at eyelid structures, mouth curves, and the flow of laugh lines when used with CC5 characters.

Texture work also gets more explicit tooling. The forum post describes a De light function that removes shadows and highlights to produce a clean albedo texture and can generate roughness and normal maps automatically for a full PBR texture set. It also brings a 3D mask brush for removing unwanted blemishes and photo artifacts such as stray hair or eyelashes, with edits on selected texture channels or across all channels at once.

Body matching and the bigger character pipeline

Headshot 3 pushes beyond the head with body matching. The launch post describes using full body reference photos so the AI automatically generates a matching body shape to complement the face, producing a cohesive character build that is fully rigged and ready for animation within the Character Creator 5 ecosystem.

On the promo side, that means a single workflow aims to move from reference to a complete character rather than a floating head. On the pipeline side, it means you still need to verify your own handoff points like shading conventions, texture packing, and how far the exported result matches your studio standards for facial rigs and blendshape naming.

If you are tracking internal workflow topics, this release lands squarely in character animation and the places where facial rigs meet real production schedules. It also sits close to mocap cleanup, since a fast character build only helps if the face holds up once you start driving it.

Again, new tools and innovations should be tested before use in production. Do the boring tests now so you do not do the expensive ones later.

Pricing, promos, and what is actually specified

There is an Early Bird Offer running April 27 through May 31 and it includes Headshot Morphs 1400 plus valued at $99 and 100 AI Image Gen Credits valued at $30. It lists a starter package for Character Creator 5 at $329 from $498, Headshot 3 at $129 from $199 as a member special, and an upgrade price of $99 for Headshot 2 customers.All prices are for Windows perpetual licenses.

New users can purchase Headshot 2 for $129 as a special offer and get Headshot 3 free at launch, and that Headshot 1 and 2 owners can upgrade to Headshot 3 for $99 starting on launch day. The early bird offer runs until May 31st, 2026.

If you plan to lean on AI Image Generation, remember the product page also states it requires credits for each generation. Test the workflow, confirm what consumes credits in your actual use, and validate liekness under your lighting and animation range before you commit it to a client deliverable.

https://www.reallusion.com/character-creator/headshot/

https://discussions.reallusion.com/t/headshot-3-is-coming-pre-launch-offer-live-now/16736

The post Reallusion ships Headshot 3 for CC5 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Drivers is a Blender rigging and animation add-on that builds driver setups for shape keys, adds viewport control panels, and manages action constraints, all from one sidebar so you can stop spelunking in editors.

What Drivers 2.0 is actually shipping

Drivers 2.0 is a paid Blender add-on that groups three ideas into one place: shape key drivers, viewport control panels, and action constraint management. The pitch stays practical. You pick a mesh, select a bone, set min and max, then wire a shape key to a bone transform with one click. The product explicitly calls out “No graph editor, no scripting.” That alone will make some riggers cheer and others quietly back up their files.

Drivers also frames itself as a workflow organizer for animators and riggers, with a focus on keeping controls in a clean N-panel interface. That is the part that usually gets messy first once a rig grows beyond a face and two hands.

Shape keys without the ceremony

The Drivers tab centers on instant shape key automation. Shape key values can follow bone rotation, location, or scale in real time, and the listing includes support claims for Rigify, Auto-Rig Pro, and custom rigs.

That makes it a tool for people who build facial systems, create corrective shapes, or apply quick pose-based deformations and want the setup to feel less like a spreadsheet and more like an actual rigging task. The appeal is speed, and also staying orgnaized once there are dozens of relationships to maintain.

Drivers 2.0 also bundles bone highlighting and bone colour management into the same UI, so the rig can communicate what is what without relying on naming discipline alone.

Viewport panels that behave like controllers

The Panels tab focuses on in-viewport control panels. It can spawn custom-shape bone panels in the viewport, with square, horizontal, and vertical control styles, and the idea is simple: drag a controller to blend shape keys without leaving the 3D view.

Text labels can be attached to panel bones via font objects, with type, scale, and offset controls exposed in the N-panel. That makes the UI layer explicit, which matters when a rig gets handed off to someone who did not build it.

There is also a master control option that adds a master bone to reposition every panel as one group, with offsets baking automatically when you hit Done. On top of that, a global lock can freeze panels to prevent accidental movement or edits before delivery.

If you have ever watched a control panel drift two pixels per shot because someone grabbed the wrong thing, you already know why that lock button exists.

Actions get their own manager

Drivers 2.0 includes an Action Constraint Manager in an Actions tab. It can assign directional action constraints to any control bone and uses a viewport glow highlight to show which bone is being edited live. The product page also lists compatibility notes that mention Blender 5.x layered actions alongside rig systems like Rigify and Auto-Rig Pro. In the same listing, the details section lists a Blender version range of 5.0 to 5.1, while another compatibility line states Blender 5.1+.

Pricing, license, and where it lives

Drivers 2.0 sells for $30 on Superhive, on a GPL license. The add-on is developed by Weybec,and remember: New tools should earn their keep the boring way: install, stress test, version-check, and only then let them near production rigs.

https://superhivemarket.com/products/drivers
https://weybec.com/

The post Drivers 2.0 cleans up Blender rigs first appeared on DIGITAL PRODUCTION and was written by Bela Beier.