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.

dy Install Libs is built to make installing libraries smooth and simple, with the stated goal of avoiding manual edits and broken installs. It ships as a shelf toolset for Houdini, aimed at the everyday stuff artists actually do: bring in a library, make sure it loads, and move on with their lives. The headline feature in v1.3 is Library Manager, a custom UI tool to download, install, enable, and disable local libraries. Version v1.3 is dated March 24, 2026, with a follow up v1.3.1 dated March 26, 2026.

The part you came for: Library Manager

Library Manager adds a single interface for discovering, installing, and managing open-source and commercial Houdini libraries. That matters because library installs rarely fail in exciting ways. They fail in slow, petty ways, like a missing file, a wrong path, or a package file that loads everywhere except the one machine that counts.

This release frames Library Manager as an evolution and combination of the earlier toolkit tools. The idea is simple: fewer trips into the filesystem, fewer chances to fat finger a package entry, and more time spent actually using the tools you installed.

There is also an explicit caveat: it may not work for installing render engines, since they typically require a custom JSON package file to set up environment variables and paths. In other words, the tool targets the library side of life, while heavyweight integrations can still demand a hand-tuned setup.

What dy Install Libs does around the manager

The toolkit includes several functions that cover the library lifecycle, from bringing in data to keeping package files aligned with where the library lives. Library from JSON imports a downloaded library using its JSON file and automatically copies and updates the package file in your library folder. This is the one for when a library arrives with its own packaging info and you want it to just land cleanly.

Install Library generates a new JSON package from scratch tied to your library folder. That means you can start from nothing and still end up with a package file that points where it should. Library from GitHub clones and installs libraries straight from a GitHub URL, which is handy when the library lives as a repo instead of a zip. It also supports downloading repository releases. That support is listed in v1.1 dated August 5, 2025.

Create Library builds a library scaffold with templates and auto-generates the package file, which aims at standardizing how a library starts its life on disk. Restart Houdini to reload everything with one click, when you want the tool to do the classic on-and-off ritual for you.

GitHub reality: releases, missing packages, and relative paths

Git based libraries come with their own quirks. The release notes for v1.1 include a fix for cases where a repo does not have a package file, replacing an older path JSON variable with hpath. It also adds support for relative paths using the $HOUDINI_PACKAGE_PATH variable in installed package files.

That combo matters because repos vary wildly in structure. Some ship a tidy package file. Some ship nothing but hope. Tooling that acknowledges those differences tends to be more usable in real production setups, where you do not control every library you need to install.

Small fix, big impact

v1.3.1 lists support for the enable key from package files when it appears as a string, while it should be a boolean. It also lists a URL key fix for when a library from a database is installed manually as a standalone library, along with small fixes and improvements.

Pricing and the practical bit

The tool is free to download, with a Gumroad listing shown as $0+. Pricing beyond that is pay what you tink it is worth.

Pipeline advice that still counts

Even if Library Manager makes installs feel effortless, new tools and innovations should be tested before use in porudction. Try it in a clean preferences setup first, confirm your package behavior matches expectations, and then let it anywhere near a show.

https://cdordelly.gumroad.com/l/dy_install_libs

The post dy Install Libs adds Library Manager to Houdini first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Photomontage lives or dies on perspective. If the camera does not match the photograph, everything downstream becomes a negotiation with angles, scale, and taste. CameraMatch AutoSetup v6 targets that first domino by generating an aligned 3D camera from a single photo, then setting up supporting scene items that normally take a few manual passes.

What CameraMatch AutoSetup v6 does

CameraMatch AutoSetup v6 is an automated camera-matching tool for photomontage work. It detects vanishing points and lines in photographs and uses that information to create a 3D camera aligned to the plate, aimed at architectural visualisation and general 3D scene setup.

Once the camera alignment happens, the tool also covers a set of setup chores that tend to get skipped until they break a comp. It can calculate and display the horizon line. It can create a physical camera with an accurate field of view. It can match the render output resolution to the background image resolution. It can set a viewport background overlay that shows vanishing point lines and the horizon. It can also export cameras using the FBX format so the camera can travel to other applications.

The overall pitch reads like a checklist of common photomontage necessities, bundled into a single automated pass. That pitch also includes marketing claims about ease and straightforwardness, which remain marketing claims.

Host apps today, and what is promised next

The currently available versions work with 3ds Max and Blender. A version for Maya is described as planned, and additional host versions are described as coming next week.

Camera matching tools often stumble on the unglamorous details of units and output sizing, so it is notable that the material calls out unit setup dialogs and scene unit contexts as part of the broader setup conversation. That framing keeps the tool squarely in production reality rather than demo land.

Why this matters for post and VFX

A good plate match is not just about placing geometry. It is about making every downstream decision cheaper. When the camera and horizon are consistent, the layout behaves. Lighting behaves. Shadow direction behaves. Reflections behave. Even simple matte work becomes more predictable because perspective lines agree across layers.

For photomontage-heavy teams, the time sink is usually not the final render. It is the first 20 minutes of making sure the camera is believable, the frame matches the plate, and the viewport does not lie. CameraMatch AutoSetup v6 positions itself as a shortcut through exactly that part of the day, with its strongest promise being camera alignment plus the surrounding setup steps in one go. If you have ever watched a project drift because two artists picked two slightly different horizons, you already know whcih argument this tool wants to prevent.

Availability, docs, and pricing reality

Documentation exists as a free manual hosted on Google Drive. The manual is covering the script for 3ds Max, Blender, and Maya. Distribution is offered through two storefront channels: Gumroad and Patreon. A one off purchase option for the Gumroad of 45USD, or through a

The download description also references a full script with files for 3ds Max and Blender, and it mentions direct contact as an option. The complete contents of the downloadable package are not listed in the provided material beyond that.

Practical notes before you point it at a deadline

Automation shines when you can trust the inputs. This tool relies on reading vanishing points and lines from photographs, so images with heavy lens distortion, weak straight line cues, or ambiguous architecture may still need human judgment and cleanup.

As always, new tools and innovations should be tested before use in production. Run it against known plates, compare results to your established camera match method, and confirm the exported camera behaves as expected in your pipeline before you bet a delivery on it. And yes, it can be both fast and correct, but only after teh boring validation pass that everyone wishes they could skip.

https://jamiecardoso.gumroad.com/l/boqjtv?layout=profile

The post CameraMatch AutoSetup v6 speeds photo matches first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

3D artist and motion designer Jörg Grubmüller has released LimbKit, a procedural tool for generating 3D hands and feet in Blender. It is described as Geometry Nodes-based and intended to help artists block out hands and feet quickly, including paw-like variants for creatures, with an emphasis on stylised work.

The core idea is simple: instead of sculpting extremities from scratch, the workflow centres on placing readymade fingers and toes onto a palm or base mesh, then generating a merged result that can be adjusted via controls for finger length, spacing, orientation, and overall shape. The promise is not “perfect hands”, but “hands that exist”, which is often the bigger scheduling problem. LimbKit includes realistically proportioned base models for hands and feet that can be refined manually, even if the tool’s stated sweet spot is stylised characters for illustration or animation.

What it does, and what it does not claim

LimbKit’s stated function is procedural generation and adjustment of hands and feet inside Blneder using Geometry Nodes, with the output merged into a single mesh that you can further tweak via parameters. That positions it as a fast starting point for modelling and lookdev, particularly when you need to iterate on silhouette and proportions without burning hours on knuckles.

There are no stated guarantees in the provided sources about rigging readiness, deformation behaviour, UV layout, subdivision performance, or downstream interchange. If you need clean edge loops that match a house rig, consistent joint placement, or predictable deformation under extreme poses, you still have to test the generated meshes and decide whether LimbKit is a blocker, a base, or a throwaway placeholder.

Grubmüller’s background is leaning towards cartoon-style character work, including prior work as a Senior 3D Character Modeler at animation and VFX studio arx anima. That does not limit what the tool can be used for, but it does explain why the initial framing is stylisation-first: it is aimed at readable shapes and fast iteration, not forensic anatomy.

Download and library workflow

LimbKit is a free download hosted on Gumroad and is stated to be compatible with Blender 4.5+. The available walkthrough information describes a “pay what you want” style flow where entering a zero value enables a free download, followed by an email-based download step.

Setting it up as an asset library is done by pointing Blender’s Preferences File Paths to a folder containing LimbKit assets, switching an import method setting from “pack” to “appended”, then accessing the assets from the Asset Browser drop-down. From there, the described interaction is drag-and-drop: pull hand and foot assets into the scene and start adjusting parameters.

Controls, gizmos, and the “procedural bits”

The supplied walkthrough description goes further into how LimbKit presents itself once assets are in the scene. It describes procedural controls in the modifier stack, including a primary control labelled “Digim Master” and scaling tools for global and per-finger adjustment. It also describes an optional gizmo-based control mode that allows moving individual finger elements forward or backwards.

Additional controls include adjustable bending styles and colour parameters that apply across the assets, including separate options for stylised variants that can alter finger length and pointiness. The walkthrough also mentions parameters described as controlling the bend tip and the bend centre.

Practical pipeline fit

LimbKit sits comfortably in the rough modelling stage when the goal is speed and iteration: building a hand silhouette that reads, matching proportions across a character set, or getting something into layout, previs, or a stylised render without dedicating half a day to digits. The workflow can be useful for motion designers and generalists who are allergic to sculpting but still need convincing extremities on screen.

What it should not be assumed to replace is the careful part: production topology, deformation testing, UV standards, and the inevitable “why does the thumb do that” notes once animation starts. LimbKit looks like a practical way to get to a first pass quickly. Whether it becomes your base mesh generator or your temporary placeholder depends entirely on your worlflow and your tolerance for procedural geometry in hero assets.

Fact check reminder: New tools and innovations should be tested before use in production.

https://joergsla.gumroad.com/l/limbkit

The post Neat LimbKit gives Blender a hand, literally first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Damjan Minovski, has released OmniStep 2.0, a major update to the interactive animation and prototyping tool for Blender. OmniStep provides a scriptable first person controller that runs directly inside Blender scenes. Instead of manually placing keyframes to animate cameras, users can move through a scene in real time while recording camera motion and interactions. The result can be used for walkthroughs, fly-throughs, previs shots, or rapid prototyping of interactive environments.

The add-on includes a built-in game loop, movement system, and collision handling. It can operate without scripting, but also allows users to extend functionality through custom scripts written directly within the scene. Version 2.0 introduces several architectural changes, including a new module system and improvements to collision behaviour. The update also integrates many previously external scripts directly into the add-on.

OmniStep is designed for scene exploration and interactive animation. Users can move through a scene using first person controls, with parameters such as speed, gravity, friction, and acceleration adjustable in the add-on settings. Walk and fly modes are available, allowing either grounded navigation or fully physics-based flight through the environment.

Camera motion can be recorded during navigation. This makes it possible to create continuous shots that would otherwise require extensive manual keyframing. The system can also interact with Blender physics and camera rigs, including constraints and other rig components.

Because the add-on includes a built-in scripting system and game loop, it can be extended to support custom interactions. Documentation for the tool notes that user-written scripts can be embedded directly in Blender scenes as text blocks and edited during development.

Modules replace scattered scripts

A central change in OmniStep 2.0 is a new module system that reorganises how extensions are handled. Earlier versions relied on external UserScripts that had to be managed individually. In the new release, most of these scripts are integrated into the add-on itself and can be accessed from a single interface. Users can selectively enable or disable them depending on their needs. The module system parses files stored in a designated module directory when Blender starts. This allows users to add new modules or modify existing ones without rebuilding or reinstalling the add-on.

Animated objects as dynamic colliders

Another change in OmniStep 2.0 is support for dynamic collisions. Any object in a Blender scene can now act as a collider, including animated objects and entire hierarchies driven by keyframes. This allows moving elements such as platforms or mechanical components to interact with the controller during runtime. The add-on already uses a capsule-based collision system backed by a BVH tree structure, which allows collision detection against complex geometry with large triangle counts. With the new dynamic collision support, animated geometry can participate in these interactions. In practical terms this means that moving obstacles, elevators, or other animated props can influence the player movement during recorded walkthroughs.

The underlying collision detection and physics integration rely on Blender’s existing physics systems. The exact internal implementation of the dynamic collision update has not been described in publicly available documentation.

Cursor warp and reshoot workflow

The update also introduces several workflow improvements aimed at interactive recording. One of them is the Start at Current Frame option. This allows users to restart OmniStep recording from the current timeline frame rather than the beginning of the animation. According to the developer, the feature simplifies re-shooting specific parts of an animation without re-recording the entire sequence. Another addition is Cursor Warp, a feature intended for multi-monitor setups. When moving the camera quickly, the system can automatically reposition the cursor so it does not reach the screen edge and lose focus from the Blender window. Cursor Warp replaces an earlier option called Center Cursor.

Compatibility and availability

OmniStep 2.x is compatible with Blender 4.5 and later. The developer states that the add-on has been tested on Windows, macOS, and Linux systems. The update is free for existing users of the add-on. New users can purchase OmniStep via the marketplaces (Name a fair price :D ) listed on the project website, including Superhive ()15$ and Gumroad(Name a fair price).

As with any add-on that modifies core animation workflows or introduces runtime interaction inside production scenes, artists should evaluate the tool in controlled test projects before deploying it in production pipelines.

// https://omnistep.atair.cc/index.html
// https://omnistep.atair.cc/Resources/DemoFiles.html

The post OmniStep 2.0 adds modules and dynamic collisions first appeared on DIGITAL PRODUCTION and was written by Bela Beier.