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

Free, but not aimless

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

What you actually get day one

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

Installation is refreshingly old-school

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

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

Licensing: one machine, one account, bring patience

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

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

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

Support: community-first, by design

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

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

Export and pipeline limits you should treat carefully

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

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

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

Compatibility and pricing, as stated

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

Where this fits with your current crowd toolbox

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

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

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

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

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

Most character work starts the same way. You open reference files, squint, and interrogate the footage frame by frame. How low do the hips drop. Where is the apex of the arc. How long does the hangtime last. You scrub, pause, scrub again, and yes, sometimes you cry a little.

KZ_Tracker exists because that manual extraction feels absurdly slow when the goal is just a first pass with honest timing. The developer built it to grab motion information directly from video and get a quick blocking pass moving, without turning the process into a full motion capture production.

KZ_Tracker wants to convert tracked movement into something animators can push around in a scene, edit aggressively, and treat as a starting point rather than a finished performance.

What KZ_Tracker actually does in Maya

KZ_Tracker lets you track points in video footage and convert them into usable animation curves inside Maya. It generates TX and TY curves depending on perspective and extracts real timing and rough spacing from the footage, so you get immediate motion data you can work with in your shot.

That matters because it keeps the output in animator territory. Curves live where the rest of your work lives. You can reshape timing, adjust spacing, smooth noise, exaggerate arcs, and keep polishing until it reads.

The tool targets the same moment in the workflow where you normally switch from analysis to keys. Instead of manually estimating where a hand peaks or when a prop changes direction, you can track the point and get curves that already contain that motion shape.

A workflow built around clicks, caches, and locators

The intended workflow starts with loading your video and caching it. You then create tracking points by clicking directly on the footage and track them through the sequence. After that, you generate curves onto locators, apply the result, and refine.

The result will still contain a healthy amount of realism. The curves are not perfect, and the tool does not try to replace animation. It tries to replace the nothingness that happens before animatino has any structure, when you are still guessing timing and spacing from a scrub bar.

That approach also makes the tool usable beyond bipeds. Creatures, props, and random objects are the targets that fall outside classic performance capture expectations, where you still want reference-driven motion but do not want to build a full capture setup.

Not mocap, not magic, still useful

KZ_Tracker is simpler and faster 2D mocap, primarily for quick blocking and motion reference rather than final mocap output or even polished animation. You are not getting a solved skeleton. You are not getting a retarget pass. You are getting tracked point motion turned into editable curves that can guide your keys.

In production terms, that can buy real time. A rough pass that nails timing early often beats a clean pass that moves wrong or late or both. Curves from tracked reference can also preserve subtle accelerations and decelerations that are easy to miss when your spacing is done by eyeball.

Layered animation workflows get the spotlight

KZ_Tracker is presented is effective in layered animation workflows, which is how many Maya animators already work, because it lets you treat the tracked motion as a base layer, then build intent and performance on top.

If the track is noisy, you can smooth it. If it is too literal, you can stylize. If it only gets you sixty percent of the way there, that is still sixty percent you did not have to manually reconstruct. You still need taste, cleanup, and shot context. KZ_Tracker just moves the first mile closer.

Compatibility, licensing, and the short film angle

KZ_Tracker is compatible with Microsoft Windows and Maya 2023 and later. It is available as a one-time purchase with no subscription required. The developer says the release aims to help fund the next short film. That is not a feature, but it does explain why the tool ships as a paid product rather than a free experiment.

https://kzanim.gumroad.com/l/KZtracker

The post KZ_Tracker turns video into Maya curves first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

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

A small tool for the most common annoyance

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

Channel mixing, then levels, then stop touching it

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

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

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

Crop tools that fix your reference photo lies

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

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

Shortcuts and export that respect your time

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

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

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

Under the hood, it stays refreshingly unprecious

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

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

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

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

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

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

https://github.com/artofpilgrim/levels

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

TL;DR: meshController is a C++ plug-in for Autodesk Maya that adds surface pinning, mesh-driven controls, and VP2 viewport tooling for character and facial rigging.

What shipped, and what it targets

meshController is a free C++ plug-in for Autodesk Maya that focuses on surface pinning, mesh surface binding, and VP2 viewport controls for production facial and character rigs. It comes with six node types and five commands, plus an example Maya scene file with a face rig and textures. Pricing is simple: free in the sources.

The core idea borrows from the DreamWorks Animation Premo approach: controls that sit on the character surface instead of floating curve shapes. For artists, that means you interact directly with mesh-based controls that feel visually welded to the character, while still behaving like standard Maya controls for selection and manipulation.

If you live in the rigging trenches, the important part is not the concept. It is whether the nodes solve daily problems cleanly, evaluate fast, and fail predictably when you do something dumb at 3 a.m.

The plug-in in plain technical terms

The documentation calls meshController a “production-grade” toolset for Maya 2023 and later on Windows, with parallel evaluation via oneTBB and viewport interaction using Qt. The compiled plug-in registers as meshController.mll and loads through Maya Plug-in Manager or via a loadPlugin call.

First, Surface Pin. The surfacePin node binds rig controls to a deforming mesh so they track position, orientation, and twist. The workflow binds at a chosen pose, stores bind data, and then reads deformed mesh positions at runtime. surfacePinBind handles binding and supports undo and redo. A key feature is a localInverseMatrix input intended to solve double transforms inline when the pin drives offset controls in a facial hierarchy. The docs also state the node preserves the current transform offset at bind time so controls keep their authored pose.

There is also surfaceUVPin, a UV space variant. Pins store UV coordinates so they can survive topology changes as long as the UV layout stays stable. That is particularly relevant to facial rig work, where meshes evolve mid-show while UVs sometimes remain the one stable thing everyone agrees not to touch.

Second, vertexWrap. This is a lightweight deformer designed to snap split or matching topology meshes to a driver mesh via one-to-one vertex mapping. The docs describe it as avoiding proximity search at evaluation time. It computes a mapping at bind time, then directly copies driver vertex positions to the driven meshes at eval time. The intended use case is lots of small control shapes that must stick to a deforming face.

Sprinkled on top are viewport tools. The docs list shapeControl as a VP2 custom locator with mesh or curve display and hover highlighting. They also list meshControlOverlay, which draws an overlay and hover marker, and meshControlMode, an interactive placement mode that uses Qt mouse move hit testing and viewport overlay feedback. The docs include a comparison table explaining when to prefer shapeControl versus meshControlMode, including a warning to avoid large numbers of live shape controls and to use the overlay path for big sets.

Somewhere around here you will want to resist the urge to replace every curve controller with a mesh. The sources themselves recommend using these controls selectively for main controls rather than replacing everything. But where is the fun in that.

Requirements, downloads, and what you actually get

The download page lists meshController v1.0.0 for Windows and Maya 2023 or later. It also lists a Linux version as “not available yet”. It recommends an NVIDIA GPU for GPU override.

For installation, meshController loads through the plug-in manager or by loading the plug-in by name. Once loaded, all nodes and commands become available immediately.

Licensing, pricing, and the boring bits

meshController is free to download, with documentation and an example scene. They do not specify a commercial license in the sources provided here.

Versioning in the sources: the docs label meshController v1.0 and Maya 2023+, and the download page lists meshController v1.0.0.

If you want to test it properly, build a small facial sandbox scene, swap a couple of core controls to mesh-based shapes, and watch evaluation and selection behavior under your usual shot workflows. Do not start by rewiring the whole face. That is how you end up with a sufrace pin node you love and a manpiulators bug you cannot explain to production.

https://www.cgdzg.com/mesh-controls-for-maya/

The post DreamWorks style mesh controls land in Maya first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

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

The headline feature is editorial glue

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

Sequencer gets editorial glue, not just buttons

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

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

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

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

MotionMaker focuses on editing clarity

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

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

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

Smart Bevel keeps hunting the ugly edge cases

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

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

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

Bifrost adds a search box and more sim and rig polish

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

USD for Maya targets variants, and pins the manager

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

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

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

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

Arnold and Substance updates ride along

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

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

Platforms and pricing

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

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

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

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

For those who don’t know the tool: 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: Flair is a stylized renderer inside Autodesk Maya, focused on NPR looks in the viewport and rendering, with style shaders, materials, and line effects that sit upstream of comp and delivery.

macOS arrives, and it is not a footnote

Flair 1.2 adds macOS support for Maya 2024 and newer. The supported operating systems now cover Windows, Linux (Rocky), and macOS, with macOS builds on Apple Silicon only. The setup requirements are macOS 14 as minimum and macOS 26 as recommended, alongside Windows 10 and 11 and RHEL based Linux options. Linux availability is tied to specific license tiers.

Proxies stop being special materials and start being a toggle

A core workflow change in 1.2 is how proxies work. Any flairShader material can now double as a proxy with a single toggle, replacing the old ShaderFX proxy material. The new proxy behavior supports Wobble, Offsets, and multiple NoiseFX types. That matters because the proxy no longer needs to be a separate shaded thing you babysit, it becomes a mode of the same material you already use.

This is a practical fix for hard-shell proxy intersections and visible component lines when proxy geometry overlaps other geometry. With the proxy living inside the same shader, you can apply effects like Wobble Blur to introduce diffusion and gradients rather than accepting a hard boundary.Using proxy offsets to localise line thresholds, so a region can show only depth-based silhouettes while the rest of the scene keeps different line logic. That kind of localised override can be the difference between a clean frame and a late night of per-shot hacks.

You still want to test this carefully in production. Even when an update says it is seamless, changes to proxy behaviour can alter look dev deltas in ways that only show up once animation starts doing unpleasant things.

Lines get more controllable and more mischievous

Flair 1.2 adds a set of line features that target a classic pain point: outlines and inlines are not the same thing, so stop treating them as if they are. A new Canvas Override global attribute can replace the beauty pass with the canvas colour. In practice, this lets you inspect what Flair effects and line work contribute, without the underlying shaded colours distracting you. The attribute appears in the globals documentation and in the release notes as a new global control.

For outlines specifically, the update adds Outline Width Offset, letting you modify line width for outlines relative to inlines. In the video, this becomes a look-dev lever for graphic styles in which the silhouette reads as bold while interior lines stay subtle, or where outlines disappear entirely, leaving only internal structure.

Light response also gets split. There are new controls over Outline and Inline Light Response for both clean and rough lines. That separation enables a sharper art direction trick: negative light response. Negative light response shows lines in shaded parts of the scene, which the update calls out as a “noir-style” option. In the demo, that produces lines where you would otherwise get pure darkness. It is a neat tool for stylized lighting setups where you want form to read in the shadows without repainting the entire grade.

Depth based sketchiness control arrives too, via Sketchiness Depth Range and Sketchiness Depth Factor. This lets sketchiness increase or decrease along scene depth, and it is presented as a global control that works across scenes, rather than relying only on placing proxy planes at different distances. For facilities that build reusable style presets across sequences, this is the sort of knob that can save time when layout changes the scale of a set and your line breakup suddenly looks wrong.

Licensing grows up: subscription, plus options studios actually ask for

Flair 1.2 expands licensing beyond subscription to include perpetual and floating licenses, and it introduces a licensing server to manage floating seats. Online licenses can be migrated to a new machine six hours after the previous activation. The release log also calls out fixes for activation on new Windows machines where wmic is missing, and an installer fix when an older install folder path no longer exists.

Activation for floating licensing occurs by entering a hostname or IP address for the license server, after which the client fetches available licenses and activates the first one that is free. That maps cleanly to typical facility patterns where artists should not care which workstation holds a seat today, only whether the pool has one left.

Performance and saving: fewer reasons to stare at a frozen UI

The Sequence Renderer gets asynchronous saving of images to speed up rendering, with image writes moved to a separate process so they do not interfere with rendering. It also gains continuous improvement for anti-aliasing beyond 32 TAA samples up to 254 samples, and the camera list can now be unlimited.

Material handling gets several workflow improvements. Keyed attributes in flairShader materials now work in Parallel and Serial evaluation modes. All material attributes appear in the Channel Box and the Attribute Spreadsheet. There are fixes for a GPU memory leak tied to assigning materials to components while scrubbing the timeline, and several other fixes around AOV blending, vertex baking, and material conversion.

There is also a new “Sanitize Flair” button in the toolbox that unloads the plugin and tries to remove all traces of Flair from an open scene, with a confirmation dialog and no undo. That is the sort of scorched earth tool that you hope you never need, until the day you really need it.

Unreal Engine enters the chat, via beta testing

Alongside the Maya 1.2 release, the newsletter announces beta testing for Flair for Unreal Engine. The team received an Epic MegaGrant last year and that it led to a major roadmap overhaul and a late Maya update, while enabling focus on bringing Flair to Unreal Engine.

The Unreal version is not nearly as feature-rich as the Maya version yet, but it is completely modular. The modular approach is a way to mix and match different effects to create a custom style. Beta testers are recruited by replying to the email, with testing planned for April and a questionnaire at the end of the month to help prioritize features and guide future development. If you live in a pipeline where Unreal Engine sits in previs, virtual production, or realtime look dev, a modular stylized renderer could be very useful. It could also be a moving target, because beta testing exists for a reason.

One last reminder before you install anything on the main machine: validate look changes on a copy of your scene library, because even small line and proxy changes can ripple through a show. And yes, the nori lines look great in a demo, but your shots will still find a way to be difficult.

https://docs.artineering.io/flair/release-log/

https://artineering.io/

The post Artineering Flair 1.2 for Maya hits macOS 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.

Read more: Autodesk launches Project Falcon

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.

Fallout Season 2 asked for more scale and less forgiveness. Rise delivered 244 shots across seven episodes, with the heaviest work landing early, and kept two sites moving as one crew. The playbook stayed familiar, but the demands went feral: closer cameras, heavier mechanical interaction, city-wide procedural destruction, and sand-driven reveals that punished every shortcut.

Fallout!

Andreas Giesen is a Rise VFX Supervisor with a Houdini-heavy background and a track record on FX-intensive shows. He is credited by the Television Academy for a 2024 Primetime Emmy nomination for Fallout in “Outstanding Special Visual Effects in a Season or a Movie”. His Rise FX credits include serving as the studio VFX Supervisor on The Matrix Resurrections, as well as work on has worked on X-Men, The Matrix, The Last of Us and the various entries in the Marvel universe, among others.

DP: When we last spoke about Fallout Season 1, you worked on a show that combined large-scale environments, destruction, Vertibirds, Power Armour, and complex integration work. On Season 2, where did the challenge shift?

Andreas Giesen: The challenge shifted purely to massive scale and extreme scrutiny. In Season 1, we were establishing the rules. In Season 2, we took those rules and stress-tested the pipeline. We had a huge jump in scale, like procedurally destroying the entirety of Los Angeles or dealing with the multi-layered sand reveals of Area 51, but we were operating with roughly the same core team size. Brute forcing was not an option. We had to lean heavily on our procedural setups and the USD foundation we built in Season 1 just to survive the shot count.

DP: Did Season 2 feel like a continuation of an established visual language, or more like a technical reset because the demands had changed so much?

Andreas Giesen: Artistically, it was a continuation. We already had that shorthand with Jay Worth and Jonathan Nolan, so we knew what that tactile, grounded Fallout look felt like.

Technically, though, it was a massive upgrade. We did not throw everything away, but we had to rebuild or upgrade many assets because the camera was suddenly much closer or the interactions were much more complex. The Vertibird docking with the Caswennan, for instance, required a whole new level of mechanical detailing that just was not necessary in Season 1.

DP: RISE delivered work across several episodes, with particularly dense work in some of the early ones. How did that affect the structure of the production on your side?

Andreas Giesen: We delivered 244 shots spread across seven episodes, but the bulk of the heavy lifting hit right in episodes 2 and 3. To keep the chaos in check across our Berlin and Stuttgart offices, we operated as one unified team. We ran single VFX dailies so it never felt like two separate facilities. We relied heavily on our in-house production management tool, risebase 3, to keep the sites synced.

Honestly, a massive shoutout to our VFX Producer Annelie Dangel , Production Manager Scott Kunysz, and the coordination team. They were the real firewall keeping the production structured while the artists dealt with the pixel pushing.

DP: You mentioned that the work was divided into more specialised teams. How exactly did that division work in practice?

Andreas Giesen: Instead of splitting the work purely by department, where an asset just gets tossed over the wall, we built small, cross-functional strike teams dedicated to specific sequences. For example, we had a dedicated Area 51 team and a completely separate Caswennan team.

Each of these pods basically consisted of one layout artist, one lighting artist, and an FX artist if the sequence required it. This meant the artists became absolute experts on the continuity, lighting setups, and specific technical hurdles of their assigned sequence, rather than constantly context switching between different environments.

DP: The Caswennan ship has become even more important in Season 2. At what point does a hero asset like that stop being “just a vehicle”?

Andreas Giesen: When you get that close, it absolutely stops being just a vehicle and becomes a massive flying set. The layout has to treat it like a static environment just to block the shots, especially when we are tracking complex character animation and heavy mechanical interactions, like the Vertibird docking, directly onto the hull.

DP: What were the rebuild decisions under the hood?

Andreas Giesen: It was actually a really interesting round-trip process. Since the flight deck scenes were shot on a virtual stage, we received the Unreal Engine asset from production as our starting point. Funny enough, that Unreal asset was originally based on our own Season 1 dirigible model!

So, our CG team, led by Jenny Leupold , took the updated proportions from the virtual stage, brought the asset back into our pipeline, and completely re-engineered all the high-res cinematic details and shading quality.

DP: How did you approach balancing a highly detailed close-up asset with practicality for layout, lighting, and shot iteration?

Andreas Giesen: We relied heavily on our USD workflows and instancing. We had to design functional heavy hydraulics and complex mechanical joints so the lifting arm physically made sense up close, but we could strip that back or use lighter variants for wider layout tasks so the scene would not grind to a halt in the viewport.

DP: In Season 2, there seems to have been a stronger overlap between physical production, virtual production, scans, and final CG. How did that affect the pipeline in concrete terms?

Andreas Giesen: It meant we lived and breathed LIDAR. For the Area 51 reveal and the hangar sequences, production gave us incredible plates and highly accurate scan data. Having that precise spatial data was the only way to guarantee a seamless transition from the practical sets into our massive digital extensions. Once that data enters production, it locks in your scale, distance, and speed, which were crucial for making the flight dynamics feel grounded in reality.

DP: There was also mention of Unreal-based virtual production material related to the airship. How did you manage the relationship between real-time assets, scanned set data, and final cinematic assets?

Andreas Giesen: Again, USD was the bridge. We took the Unreal assets, which gave us the exact scale and spatial relationships from the LED volume, and used them as the spatial framework to build our final pixel cinematic assets over the top. It ensured that when we integrated the final CG back into the live action plates, all the contact points and lighting references matched the physical set pieces perfectly.

DP: Was the biggest benefit from USD technical elegance, or simply that it stopped artists from stepping on each other’s work?

Andreas Giesen: Ha, a little bit of both, but honestly, stopping the file overwrites is worth its weight in gold. On a more technical level, the real elegance was how flawlessly it let us bridge the gap between Maya and Houdini.

For the Shady Sands environment, our Layout Lead Karin Wolf and her team built the pristine, non-destroyed city parts in Maya. We then brought that via USD straight into Houdini to scatter all the granular details and endless cornfields. Being able to mix and match layouts without friction meant artists could just stay in the tool they were fastest in.

DP: The Vertibird work in Fallout has always been interesting because it needs to feel stylised and believable at the same time. What were the challenges for it in Season 2?

Andreas Giesen: The challenge is that it is a massive, lumbering vehicle, but it still needs personality. For Xander Harkness arriving at Area 51, he is a fantastic, slightly cocky pilot, so we had to inject this aggressive precision and specific swagger into the flight path and mechanical braking.

The integration challenge, especially during the Caswennan docking, was finding that fine balance of heavy momentum. We had to ease the mass and simulate procedural micro vibrations to show it buffeting in the air currents. The hardest part was nailing the exact frame where the mechanical arm takes over the full weight and the rotors power down.

DP: How much of selling a vehicle like that comes from animation, and how much from camera language, editorial rhythm, and integration into atmosphere and environment?

Andreas Giesen: Animation gets you the weight and the performance, but the environment integration is what sells the lie. In the hangar landing, the plate was dramatically backlit. Our lighters had to introduce specific light sources to shape the geometry nicely and match the foreground. Then the FX rotor wash tied everything together. We simulated heavy CG dust and debris blowing right past the lens, matching the practical wind from the live-action plate to physically anchor the digital ship into the real set.

DP: For sequences involving scanned practical sets, such as hangar or landing environments, what are the biggest pitfalls once the scan data actually enters production?

Andreas Giesen: The biggest pitfall is that the scan data and the live action plate lock you into absolute physical reality. If the plate has a specific wind direction or interactive lighting, absolutely every piece of CG vegetation, dust, or vehicle integration has to physically react to that exact same environmental energy, or the illusion breaks immediately.

DP: Fallout still has this very specific balance: it is heightened and absurd in places, but the world still needs physical credibility. How does that affect VFX decisions in review?

Andreas Giesen: You have to ground the absurdity in absolute, boring physical reality. For the dramatic dirigible crash, which is inherently a heightened, spectacular moment, we went straight to historical footage of the Hindenburg. We ran intense, clustered simulations starting with plastic deformation for the metal bending, triggering RBD sims for the hull ripping apart, and feeding that into multiple layers of pyro for flames, smoke, and contact sand. If the physics are incredibly strict, the audience will buy into the universe’s stylised madness.

DP: On a show like this, where does proceduralism genuinely save time, and where does it still need a heavy layer of manual art direction to become production-ready?

Andreas Giesen: Proceduralism saves you on the sheer volume, but art direction saves the shot. For the destroyed Los Angeles, we started with basic map data, literally just cubes and planes. Our brilliant TD, Kilian Baur , built a Houdini tool that procedurally converted those cubes into heavily detailed, destroyed buildings. It generated massive amounts of geometry. But you cannot just hit simulate and walk away. We had to manually paint the degree of destruction across different zones for compositional reasons. The tool does the heavy lifting, but the artist still has to compose the frame.

DP: Was there a particular sequence in Season 2 where the real constraint was neither the creative idea nor the client feedback, but simply scene complexity, cache weight, or iteration cost?

Andreas Giesen: The dirigible crash and the Area 51 reveal were absolute beasts for cache weight. For Area 51, we were blending volumetric dust, suspended sand particles, and contact sand actively swirling off the geometry. The dirigible had even more interactive layers, expertly managed by FX TD Arnaud Malherbe under Jens Martensson .

We survived by heavily clustering the sims for faster turnarounds and by relying on deep compositing workflows in Nuke. Our Compositing Supervisor Michael Lankes , Comp Lead Kader Bagli , and Comp Lead Jannik Walzer did incredible work taking those massive datasets and balancing them without bringing the farm to its knees.

DP: What became easier on Season 2?

Andreas Giesen: Things like lookdev for the energy signatures became easier. We reused the core effect for the cold fusion and diode glows from Season 1. But because we had to scale it up to so many more shots, we had to build highly efficient setups in Nuke involving heavy rotomation and complex relighting, since that blue glow affects every shiny metal surface around it. The look was established, but the volume and the necessary integration were significantly harder.

DP: Was there a shot or sequence this season that looks deceptively simple in the final cut, but was technically far more difficult than most viewers would ever suspect?

Andreas Giesen: It has to be the Power Armor enhancements. Production has this absolutely incredible practical suit that a stunt performer wears on set. However, because it is a physical, wearable suit, sometimes individual parts will naturally jiggle or bounce a bit too much during heavy action, which breaks the illusion of solid, heavy metal armor.

In the shot where the massive dirigible is coming down and exploding in the background, we actually had to completely replace the shoulders of the Power Armor while the character is running away. Everyone in the audience is obviously staring at the massive fiery airship crash taking up the sky, but there we are, meticulously tracking and doing invisible CG replacement on shoulder pads just to make sure the suit feels appropriately heavy.

DP: And conversely, was there a shot that looked terrifying at first but became manageable once the right structure or workflow was in place?

Andreas Giesen: Definitely the procedural destruction of Los Angeles. The idea of destroying a city of that scale is terrifying. But once Kilian’s tool was in place, and we utilised our USD pipeline to block the shots with simple geometry while the high-res destruction updated seamlessly in the background, it actually became a highly manageable, iterative process. We could instance the endless piles of rubble and rusted cars, which kept the massive scale from becoming unrenderable.

DP: What is a technical lesson from Fallout Season 2 that would transfer well to other large episodic shows?

Andreas Giesen: The absolute golden rule is to keep everything as procedural as humanly possible so you can actually survive rapid client changes. That, combined with establishing those small expert strike teams we talked about, is how you manage the chaos. But the real lifesaver that transfers to any heavy show is aggressive pipeline automation. For sequences with massive shot counts, we utilised our proprietary riseflow tools to completely automate the heavy lifting.

We could submit CG renders from one principal master scene across 50 different shots before leaving the studio. By the next morning, the pipeline had automatically generated 50 temporary composites, already perfectly combining the new CG with the live-action plates using deep learning. Waking up to 50 ready to review temp comps instead of a massive rendering bottleneck is the only way to deliver a show of this scale.

DP: What is the next project you are working on, insofar as you can already talk about it, and is there anything from Fallout Season 2 that you are taking with you into that next production?

Andreas Giesen: I am currently working on something very exciting, but unfortunately, it is strictly under wraps right now, so I cannot speak about it just yet. But I am absolutely taking the USD workflows and the procedural pipeline strategies we refined on Fallout straight into this next challenge!

The post RISE: Fallout Destroys LA, Politely first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

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: Redshift is a production renderer that plugs into DCCs like Cinema 4D, Autodesk Maya, SideFX Houdini, Autodesk 3ds Max, Foundry Katana, and Blender, so lighting TDs can argue about samples in the app they already love.

The night shift arrives everywhere

So, after sorting through the heap, it is time to talk about Redshift, specifically. Redshift 2026.5.0 adds a night sky representation to the Sun and Sky system across hosts, including stars, moon, and Milky Way, with time and location controls.

That matters less for hero closeups and more for the boring shots that still need to ship: wide establishing frames, background domes, and lighting continuity on sequences that bounce between day and night. And also, to keep the internet sleuths ansd “Actually-s…” at bay.

The same update also includes a fix for the Physical Sun and Sky light where the milky way could render in flipped coordinates. It is the kind of bug that makes you doubt your compass and your life choices at the same time.

OpenPBR takes the default seat in Cinema 4D

For Cinema 4D, OpenPBR becomes the default material, and the default material list in preferences gets updated. The shader model itself comes from OpenPBR, the OpenPBR Surface specification hosted under the Academy Software Foundation umbrella.

In practical terms, the change means new scenes in that host start from OpenPBR unless a user switches the preference. It also comes with a cleaned up material menu that puts OpenPBR up front and pushes older options out of the spotlight.

If your pipeline has older material libraries, this is the moment to check how presets migrate, how template scenes behave, and whether old lookdev assumptions still hold. New tools and innovations should always be tested before use in production.

Texture Displacement gets smarter and less picky

Texture Displacement continues to expand, building on the system introduced earlier as an alternative to vertex displacement. In 2026.5.0, texture-based displacement gains preliminary UDIM and UVTILE support. It also gets mirror repeat mode when smart baking is enabled, plus improved quality when displacement is driven by UV projections.

There is also enhanced auto bump mapping support meant to improve bump mapping quality when used with displacement nodes. This addresses a common pain point where displacement and bump interplay can get noisy or fight each other in shading.

A set of fixes targets stability and interactivity too. The release notes list multiple cases where texture displacement could disappear or show artefacts in interactive preview rendering when using bucket mode, and those issues have received fixes.

One more fix calls out self-shadowing artefacts on objects with extremely high polygon angles when using Texture Displacement. If you have ever seen displacement turn into a crunchy self-shadowed mess on near-planar geometry, that line will feel oddly personal.

Some Cinema 4D specific fixes also land here, including a bug where UDIMs were not correctly rendered when using Team Render, plus a bug that could cause random black images when rendering heavy meshes with deformation blur enabled. Redshift 2026.5.0 also sets a minimum plugin requirement of Cinema 4D 2026.2.

In the middle of all that, one of the most important workflow wins is banal: fewer special cases. The more often displacement works the same way across UV layouts, projections, and preview modes, the less time artists spend building around the renderer instead of using it. Also, please rmember that displacement tends to be the first place where a scene crosses from fine to on fire, so keep an eye on memory and subdiv settings when you roll this out.

AMD ray tracing via HIP RT, marked experimental

Redshift 2026.5.0 adds experimental support for HIP Hardware Ray Tracing, also known as HIP RT. HIP RT itself is an AMD HIP RT ray tracing library designed for applications using HIP.

The release notes call the feature experimental. That is a polite way of saying you should not bet a deadline on it without testing it on your actual scenes, drivers, and farm images.

The same build also mentions improved render startup performance in scenes with high primitive counts when using Hardware Ray Tracing. Together, those notes make a clear point: hardware ray tracing paths continue to expand, and more of the heavy lifting is expected to land in that codepath over time.

Windows on Arm joins the CPU party

Redshift 2026.5.0 adds native Windows Arm64 support for Redshift CPU in Cinema 4D, ZBrush, and via the command line renderer. That is specifically CPU rendering, not GPU rendering. For the broader platform context, Windows on Arm covers Arm64 devices running Windows, including systems where native Arm apps run without emulation while other binaries may run under emulation.

If you are eyeing Arm based Windows laptops for travel kits or lightweight previs work, this change removes at least one hard block for CPU rendering workflows in those supported routes. It does not magically turn an ultraportable into a render node, but it does make it a more honest option for tests, turntables, and emergency output.

Bottom line for production

None of that removes the usual responsibility from leads and TDs. Update one step at a time, validate looks against show frames, and test your farm and plugin versions before you flip defaults for everyone. That advice feels boring, right up until it saves your weekend.

https://www.maxon.net/en/redshift

The post Maxon ships Redshift 2026.5 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Phoenix plugs into Autodesk 3ds Max and Maya for fire, smoke, and liquids, and it also ships inside V-Ray and Corona subscription bundles.

End of support, officially

Chaos has moved Phoenix to End-of-Support status. The software will continue to function as it does today, but no further feature development, compatibility updates, bug fixes, or security updates are planned. New standalone Phoenix subscriptions are no longer available for purchase. Phoenix simulation nodes are not affected by the change. Users can continue using existing nodes or purchase additional ones as needed.

Existing subscriptions: renewal rules

Existing Phoenix licenses continue to function normally, and users can keep using Phoenix as long as they continue renewing their subcsription. Renewals are processed at the applicable list price at the time of renewal, regardless of any discounts applied to the original purchase. If the subscription expires at any point, it cannot be reactivated again.

Seats: a time-limited window

Users can add seats to an existing Phoenix subscription during a 42-day grace period from the date of communication, until 14 May 2026. After that period, no additional seats can be added.

Bundles: still included, still end of support

Phoenix will remain available within the V-Ray Premium, V-Ray Collection, Corona Premium, and Corona Collection subscriptions, in the same End-of-Support state.

Switching options and pricing note

A support option exists to transition from Phoenix to V-Ray Premium or Corona Premium via MyChaos or a reseller.

The post Phoenix moves to end of support first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Cargo is a desktop asset browser that connects to Blender, Unreal Engine, Cinema 4D, and more, so you can browse, download, and send models and materials straight into scenes without spreadsheet cosplay.

One app, two libraries, fewer tabs

KitBash3D made the app as the “front door” for discovering and importing its kits, with the bundled library concept now expanded to cover both catalogs.

Two previously separate collections now live side by side inside the same interface, with one sign-in and one search. The combined catalogue includes kits and models alongside scan-based materials, textures, and surface imperfections, all presented as a single system meant to keep structure and surface close together.

That unification also shows up in how content gets packaged. The app emphasizes a consistent pipeline based on OpenUUSDSD and MaterialX, aiming to keep hierarchies and instances intact while translating materials into native shader setups for the target renderer. This is a foundation-level rebuild rather than a cosmetic refresh.

The free starter pack is not tiny

A free account includes a curated set of assets you can browse and download without a credit card. That free set is described as 100 plus assets, and an independent count lists 483 total free items. Its a start :)

245 models, largely building and vehicle parts from two free kits plus a set of semi-abstract biomorphic forms. There are also 189 materials, including fabric, brick, and tile options, plus 44 textures of mostly geometric grids with additional bokeh and dirt textures.

If your day job involves pitching lookdev choices at 9am and shipping frames at 6pm, the free selection matters because it lets you test the pipeline end-to-end. You can confirm how the importer behaves, how instances land, how shader graphs translate, and how your render engine reacts to the material schema before you commit budget.

Search got smarter, and also weirder in a good way

The browsing experience leans hard on discovery features designed to reduce the number of times you type a noun and get punished for it. Smart Search supports natural-language descriptions like “dark industrial”, interpreting intent rather than matching exact keywords. Image Search lets you drop in a reference image and find assets that match its visual style. Show Similar pulls results that share visual DNA with the currently selected asset, encouraging variation hunting without restarting the search. Random Roll reshuffles results within your active filters to push controlled surprise when your brain has gone full beige.

On the surface, these read like creature comforts as they target the most annoying part of asset libraries: you know what you want, but you do not know what the library decided to call it. Natural language and visual matching try to bridge that gap, and the similar and random tools try to keep you moving when the first pick is close but not quite it.

This is also where the unified catalog changes behavior. Similarity searches and random rolls can traverse the combined library rather than staying fenced within a single vendor silo, so discovery sessions can jump between hard-surface set dressing and material detail work without switching apps or accounts.

One click import, persistent connections, and fewer ritual steps

The workflow pitch is straightforward: select an asset, then send it to your scene. The importer is organizing geometry into clean hierarchies and instances, reusing existing assets automatically, and translating materials directly into the native format of the chosen renderer based on render settings. The goal is predictable structure on arrival, so your outliner does not turn into a haunted attic.

The connection model matters as much as the importer. The app supports connecting to installed DCCs and then sending assets through a targeted connector, rather than relying on manual export and import steps for each move. A desktop-based app is available on Windows and macOS including Apple Silicon machines.

Supported host applications and versions are listed in current documentation. The app supports Autodesk 3ds Max versions 2021 through 2024 using a non-USD legacy plugin workflow. It supports Autodesk Maya versions 2024 through 2026. It supports SideFX Houdini versions 20 through 21, including render paths that reference MaterialX. It supports Unreal Engine versions 5.2 through 5.7 using official Epic Games Launcher builds, and it supports Blender versions 4.2 through 5.0 when downloaded from blender.org.

Render engine support is Redshift, OctaneRender, V-Ray, and Arnold. Blender is listed with Cycles and Eevee. Maya is listed with Arnold and Redshift. Houdini is listed with Karma, Mantra, Arnold, and V-Ray.

The practical takeaway is that the connectors and supported versions are specific, not vibes-based. If you live on a source-built Unreal branch or a newer 3ds Max version outside the supported range, you should expect friction and plan your testing accordingly. Also: USD is king here – it might be time to get on the train.

Pricing and membership tiers

Cargo 3.0 is free to download. Subscriptions are three main individual plans and a teams option.
Greyscalegorilla Library plan at $39 per month or $468 billed yearly, which includes 3,500 plus scanned and procedural materials, 1,000 plus models, 650 plus textures, and 600 plus HDRIs.
The KitBash3D Library plan at $59 per month or $708 billed yearly, and includes 20,000 plus textured models, 2,000 plus game ready assets, 300 plus hero props and vehicles, and 200 plus Substance Source materials.
And an Everything Bundle at $79 per month or $948 billed yearly. The Everything Bundle includes full access to every new release from both libraries under one subscription.

There are also Team plans at $99 per user per month billed annually with a four-seat minimum.

What to actually do with this on a deadline

Start with the free assets and run a full pipeline pass in a throwaway project. Test search with a mood phrase, then test Image Search with a real reference frame from your show bible. Send a small cluster of assets into your primary DCC, then verify the resulting hierarchy, instances, and material graphs. Render a quick turntable in your production renderer, then repeat the same asset in a second host app if your studio straddles multiple tools.

If you rely on 3ds Max, treat the legacy plugin note as a sign to double-check compatibility before you promise anything to your producer. If you rely on Unity, the end-of-life date for the older integration means you should map out alternatives now, not when the build breaks the night before a milestone.

Cargo 3.0 sells itself on momentum. The real win is not that it can download assets, every library can do that. The win is whether it reudces the number of tiny interruptions that burn your attention budget. Install, connect, search, send, render, repeat. Then decide if the time saved is real enough to justify the subscription tier you need.

https://kitbash3d.com/pages/cargo

https://kitbash3d.com/pages/pricing
// Quoted info
https://help.kitbash3d.com/en/articles/7833635-cargo-3-0-supported-3d-software-and-render-engines

The post Cargo 3.0 merges two asset libraries first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

KeyPro replaces the idea that a timeline has to be a thin row of ticks and regret. It adds a compact strip beneath Maya‘s native timeline and renders four separate data layers in the same horizontal space. The core promise is density without clutter. The strip keeps the same broad job as a classic time slider, but it packs in readouts that normally live in separate editors, separate overlays, or separate moments where you sigh and zoom in again.

KeyPro – An advanced timeline for animators. https://t.co/tM44wbldud

Somebody said "Better than AnimBot". I don't know if that's true but it's certainly cheaper and has a killer timeline UI.

Excited to share this one. #characteranimation #maya pic.twitter.com/Mo5MKtvGG1

— Long Winter (@Long_Winter) April 8, 2026

Four layers, one strip, zero panel flipping

KeyPro renders four independently updated layers in the strip, and they update in real time as you work.

One layer draws an audio waveform. It uses cached RMS waveform rendering and draws per pixel at any zoom level. It also automatically reads Maya’s audio node when a scene loads, so the waveform appears without manual hunting.

Another layer shows key density. Every keyframe on every selected node renders as a tick. The ticks change colour based on density across a three-stop ramp that goes from blue to orange to hot pink. The point is fast visual triage for where animation gets heavy.

A third layer is a heat bar. It is a 2-pixel chromatic bar at the top of the strip that encodes how deep your current view span sits relative to the master range. Red indicates you are zoomed deep in, and blue indicates you are at full master scale.

The fourth layer is a master range that persists with the scene as a JSON file. Cyan markers show the start and end, and handles can extend the range for ease and out frames.

If you have ever lost track of whether you are looking at the full shot, the trimmed shot, the shot plus handles, or the shot you swore you would retime later, this combination aims to make that state visible at all times.

Rig-aware tools on top, not hidden in a drawer

Above the strip, KeyPro includes an animator toolbox. It includes tween presets and stepped keys. It also includes eight tools designed around constraint chains, space switching, and rig conventions.

Those rig-focused targets matter because a timeline feature only helps if it respects the reality of production rigs. Key changes often ripple through constraint setups, and space switching workflows can create keys that look simple until you touch them.

The toolset positions itself as production-grade key management, and that phrasing is a marketing claim. Still, the specific focus on constraint chains and space switching describes the kind of problems it intends to solve inside the timeline instead of pushing you out to separate editors.

Interaction that tries to feel native

KeyPro also leans on direct manipulation. Left drag scrubs. Scrolling zooms. Middle drag moves keys. The stated goal is muscle memory. The idea is that the tiemline should feel like it always belonged there, even while it shows you more than the stock UI does.

Who built it and why that matters

KeyPro was made by developer Andrew Conroy. His credits include work as an animator on Ice Age, Life of Pi, and Love Death &Robots. That background does not guarantee anything about your specific rig, your studio pipeline, or your scene scale. But it does set expectations about intent: the tool targets animator pain points inside the daily grind of key management and timing.

Pricing and licensing in plain English

KeyPro sells for 49 US dollars as a one time purchase. The price is a single purchase that you keep. No subscription.

Why this is interesting right now

Timeline UX is one of those corners of animation software that everyone touches and almost nobody talks about until it hurts. KeyPro targets that pressure point directly by compressing multiple kinds of feedback into a single strip and pairing it with a toolbox aimed at everyday rig behaviors. If it lands in your workflow, the win is not a flashy new solver. It is fewer context switches, fewer blind scrubs, and faster decisions about where to spend your cleanup time.

And if it does not land, at least it is a reminder that the most valuable tool upgrades sometimes live in the least glamorous UI row in the room, right under the playhead.

Spec	Detail
Maya Compatibility	Maya 2020 – 2025+ (PySide2 & PySide6 auto-detected)
Integration Method	workspaceControl, docks natively below Maya’s timeline
API Layer	Maya OpenMaya / OpenMayaAnim (MFnAnimCurve for live key drag)
Audio Analysis	Fully cached RMS waveform per-pixel resolution at any zoom
Undo Safety	All key operations wrapped in named undo chunks
Master Range	JSON persisted alongside .ma / .mb scene file
Auto Frame	Graph Editor zoom tracks strip view on SelectionChanged + view pan
Jump to Key	Timeline follows Graph Editor selection (aTools-style behaviour)
Installation	Drag-and-drop installer · token license tied to your purchase
Design System	Consistent with full AXE Suite (Bebas Neue · DM Mono · orange/cyan/green)

The post KeyPro revamps Maya 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.

For those who don’t know the tool: tamga is a quick sculpt plus vertex paint sketchpad that hands off via Wavefront OBJ to heavier DCCs like Blender when your scene stops being cute.

Small app, big get-it-done energy

tamga runs in a web browser, on desktop, and as an iPad app. The web version targets browsers with WebGPU. The iPad version requires iPadOS 26.0 or later. The design goes for minimal UI and a low friction workflow. There are no accounts, no subscriptions, and no ads stated for the tool. The tool is also described as offline by choice, with work staying on the device. This makes tamga a handy place to rough shapes, do quick paint passes, and spit out something presentable before you move to the usual monsters.

Sculpting that stays out of your way

Brushes include Clay, Smooth, Inflate, Flatten, and Drag. A modifier flips brush behavior into an alternate mode, and there is a smooth override that temporarily switches to the smooth brush at the same size. Dynamic topology is available per brush and is described as auto-splitting and simplifying as you sculpt. Remeshing rebuilds uniform topology at a chosen voxel density, and version notes mention a Close Holes button in the Remesh pop-up.

Symmetry support includes mirror sculpting across an axis, plus a symmetrize operation that applies symmetry to existing geometry. There are desktop shortcuts for undo and redo, and gesture based undo and redo on iPad.

Masks, booleans, and posing without the drama

You can paint masks to protect areas from other brushes, with an unmask action via the modifier concept. Masks also feed mesh creation. Extract Masked creates a new mesh from the masked region, and Extract Shell creates a thin shell from the mask boundary.

For fast shape bashing, there are primitives with boolean operations: union, subtract, and intersect. A smoothness slider controls how soft the boolean blend is. Positioning uses a gizmo, snapping is on by default, and a modifier disables snapping.

There is also a pose workflow built around placing anchors and dragging to deform, with options to remove anchors, freeze to bake deformation, and clear anchors. tamga comes from galata.ink, and it is a weekend project created outside professional VFX work.

Vertex paint, plus ink lines for style passes

Painting is vertex based, so paint lives on the mesh rather than in UV mapped textures. Channels listed include albedo, roughness, and metallic, with per channel toggles for painting, filling, and clearing.

Ink mode lets you draw ink like strokes on the 3D surface. View styles listed include paper mode, matcap, and PBR. Paper mode has controls such as valleys, peaks, chisel, and a mix control that blends between standard rendering and full paper mode. Render export formats listed are PNG, JPEG, and OpenEXR.

Export, pricing, and the reality check

Import and export uses Wavefront OBJ, so you can hand off to tools like Autodesk Maya or ZBrush when you need deeper pipelines. There is also export to a tamga format, plus auto recovery that saves work and restores after crashes, hopefully. Personal use is free, and personal, educational, and non profit use is free on most platforms. Commercial use requires one time payment of 12.99 USD.

A final note for people who ship frames for a living: test new tools and innovations before you rely on them in production, especially around OBJ round trips and vertex paint persistence. Do one quick scuplt, export it, reimport it, and check if the alebdo channel survives. If it does, you just bought yourself a nimble little idea machine.

https://tamga.galata.ink/

The post Galata.ink Ships Tamga Sculpt and Paint for Browsers first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Maya is a core DCC for modeling, rigging, animation, FX, and rendering, with Maya Creative as a leaner sibling. It plugs into USD workflows, Arnold rendering, and FX via Bifrost, with a shortcut out to Flow Studio when you need the cloud.

The 2027 drop hits modeling, animation, FX, and pipeline

Autodesk has released Maya 2027 and Maya Creative 2027, with updates spanning modeling, character work, animation, simulation, rendering, and interoperability. Maya Creative gets the same new features as Maya except for Bifrost 3.0. A tech preview of an in-product help chatbot called Autodesk Assistant ships in this release. It searches product documentation and answers workflow questions inside the app.

Smart Bevel wants your Booleans to calm down

A new modeling feature called Smart Bevel (Also available in 3ds Max) generates bevels by following the surface shape rather than the underlying topology. That matters most when topology gets uneven, especially after Boolean modeling. The tool is positioned as producing more predictable results on irregular meshes, including at Boolean intersections, where classic bevel workflows often demand extra cleanup.

It is also non-destructive, keeping construction history so you can continue to refine the result. That makes it easier to treat beveling as part of the modeling flow, not a final bake-and-pray step.

MotionMaker teaches horses new tricks

A new horse archetype lands in MotionMaker, aimed at one of animation’s oldest time sinks: believable quadruped locomotion. The horse archetype can generate a believable base motion for horses in seconds. It covers core gait work, including trots and gallops, and it can generate transitions between them. The point is not just getting a loop, but getting the in-between that usually eats hours of tweaking, like moving from trot to catner without the rhythm falling apart. And since we only heard the phrase, but don’t know what it is: The special island Pony gait of “Tölt” isn’t covered, as far as we can see. But considering we all don’t know what that exactly is, we shouldn’t be too annoyed.

The horse joins existing motion styles for bipeds and canines inside the growing MotionMaker library. The workflow framing stays consistent: generate a base, then push performance choices yourself, like changing speed while keeping a natural gait, or adjusting action beats without rebuilding the whole setup from scratch.

If you have ever watched a horse walk cycle drift into floating-hoof limbo, you already know why this matters. Still, treat it like any new tool: test thier output on real shots before you bet a delivery on it.

Sequencer gets rebuilt for shot work, not nostalgia

The Sequencer has been modernized, with changes aimed at previs and layout artists cutting multi-shot sequences. Shot trimming and time scaling are now edge-driven interactions. You drag a shot edge to trim, and you use a time scale mode to scale by dragging the edge. The interface adds custom labels, color coding, automatic thumbnails, and smarter grouping behavior.

Playblasting gets its own menu and supports playblasting selected shots, all shots on a track, or the entire sequence. There is also a re-playblast option for a selected shot. File naming templates add support for a Scene keyword, and unsupported filename characters get replaced with underscores. A dedicated Sequencer workspace ships as well, and playblast output is described as improved with viewport-matching results, scene names, and full audio.

Bifrost 3.0 adds surface tension and scalable destruction tooling

Bifrost 3.0 introduces surface tension settings for liquid simulations, aimed at more realistic droplets and splashes at high resolution. Rigid Body Dynamics workflows also get attention, with performance improvements and a push toward procedural iteration. The destruction workflow is described as fully procedural, with the ability to adjust physics, tweak constraints, refine fractures, and re-simulate without rebuilding the setup. There is also a cloud option called Flow Wedging that can generate multiple variations in parallel directly from Bifrost.

OpenUSD authoring gets more guided inside the DCC

The release adds tools intended to simplify asset authoring for OpenUSD pipelines, where correctness and consistency matter as much as creativity. A guided workflow called Component Creator can build USD components through an interface designed to help structure assets properly from the start. A related Variant Manager helps define and manage asset variations.

On the 3ds Max side, an Asset Resolver is described as helping keep asset resolution stable by giving more control and visibility over how assets resolve and how paths map. It is framed as a way to reduce guesswork when something fails to load or appears changed. But more on Max tomorrow, it’s late.

Rendering and lookdev: speed, style, and portable graphs

Rendering updates focus on speed and creative control in Arnold, with improvements described for complex scenes and volumes like smoke or clouds, including GPU and volume rendering areas.

New shading tools include a stylised line option and a nearest points shader for point-based effects and data-driven shading. Hair is described as looking more natural in close-ups, and bloom rendering is described as more refined for realistic and stylised lens effects.

On the lookdev side, there is support for plugging third-party solutions into LookdevX for AI-driven generative texturing. This is presented as a workflow connection rather than a single locked-in generator. For interchange and portability, MaterialX workflows in LookdevX add support for relative paths in documents, with options to make paths relative to the scene file or workspace, and tools to toggle between relative and absolute paths.

Flow Studio gets a front door inside Maya

A new button in the Status Line can open Flow Studio directly from inside Maya. The release notes also call out Wonder 3D in Flow Studio, described as a generative AI model that can quickly generate 3D characters or objects from a text prompt or reference image, with export paths to Maya, 3ds Max, Blender, and Unreal Engine.

Pricing and system requirements

Maya is rental-only, with subscriptions listed at US$255 per month or US$2,010 per year. Maya Indie is listed as priced at US$330 per year for qualifying artists earning under US$100,000 per year and working on projects valued under US$100,000 per year. Maya Creative is pay-as-you-go, with pricing starting at US$3 per day and a minimum spend of US$300 per year.

Maya 2027.0 is available for Windows 11, macOS 14.0 or later, and Linux distributions including RHEL and Rocky Linux. Whatever part of the pipeline you touch, put the new features through your usual validation before they enter production, especially anything that changes core geometry, rig weighting, USD structure, or render outputs.

https://blogs.autodesk.com/media-and-entertainment/2026/03/25/whats-new-in-maya-and-3ds-max/

The post Autodesk ships Maya 2027 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

If your modeling flow depends on lining up a mesh to photos, you already know the usual pain points inside Autodesk Maya. You set up a camera, attach a reference image, tweak focal length and framing, then bounce across panels and settings while your brain tries not to forget what the likeness looked like two clicks ago. Handy RefTool aims straight at that friction by collecting the controls for reference matching into a single interface. The practical target is portrait modelling, but the same camera to image alignment problem shows up everywhere you match a 3D model to reference images. That includes creature design and hard surface work when you want the model to sit cleanly against a specific plate or photo set.

Classic mode, fewer context switches

RefTool includes a Classic mode that sets up reference cameras by automatically creating a camera in a scene and assigning a reference image to it. From there, the workflow focuses on fast iteration. You can adjust camera settings via slider controls, rotate around the model, zoom in for alignment checks, and scrub the opacity of the reference image to see how closely the sculpt lines up.

That opacity scrubbing matters more than it sounds. It turns the usual on-off flipping of an image plane into a continuous check, so you can keep your eye on silhouette, landmarks, and proportions without turning the viewport into a strobe light.

Once you have a camera setup you like, RefTool can export it as a JSON file, allowing you to reuse it in future projects. That reuse angle fits neatly with production reality, where you do not want to rebuild the same camera matching scaffolding every time a new head variant or costume pass drops into the scene.

RefBoard mode turns cameras into a wall of thumbnails

When you have multiple reference views, the real time sink is not creating them. It is switching between them in a way that keeps you oriented. RefTool includes a RefBoard mode that lets you arrange camera views like an image board and switch between them by clicking on thumbnails. That thumbnail switching also plays nicely with the way artists actually work on likeness. You rarely stay married to one image. You bounce between angles, you cross-check, you sanity test, and you keep moving. A board of camera views makes that bounce less disruptive than hunting through the outliner or viewport menus for the right camrea at the wrong moment.

Install notes, plus a very specific graphics requirement

There are two tracks here, and the install experience differs. For the free RefTool v2.1, installation runs through the Script Editor inside Autodesk Maya. You open the Script Editor, load the RefTool_v2.0.py script, then either execute it immediately or save it to a shelf for a one-click launch later. The same listing also includes free scripts labeled RefTool v2.1.1, including RefTool v2.1.1.py and RefTool_V2.1.py.

For the full RefTool v3.0, the install path starts with unpacking an archive. You then open Autodesk Maya, switch the Script Editor to the Python tab, drag and drop a maya_installer.py file into the editor, and click Save. A file dialog prompts you to select the RefToolV_X.X folder that contains the source files. After that, the tool icon appears on the currently active shelf.

One operational detail comes with a big warning label. Each time the tool launches, it runs directly from the folder selected during installation. If you move, rename, or delete that RefToolV_X.X folder after installation, the tool stops working. Both the free and full installs include the same requirement: Viewport 2.0 inside Autodesk Maya needs to be set to DirectX 11.

Versions and pricing

The version split is straightforward on paper. RefTool v2.1 is free and is described as having the core functionality. RefTool v3.0 redesigns the interface and adds extra functionality. The published price for version 3.0 is USD $14.48.

Where this fits in real work

The strongest signal here is not a single feature, it is the focus on keeping the artist in the flow. Reference matching is foundational for portrait work, but it is also a repeated micro-task across creature blockouts, prop modeling, and any job where a specific camera-to-image relationship matters. RefTool targets those repeated touches by putting the camera adjustments and reference image controls in one place.

The JSON export for camera setups adds a pipeline-friendly hook. Reusable setups can reduce churn when a project revisits the same asset type across multiple shots or deliverables, or when a team wants consistent camera matching conventions for a specific modeling task. As always, new tools and workflow tweaks should be tested before you let them anywhere near a production deadline, especially when the tool depends on specific viewport and graphics settings.

https://www.artstation.com/marketplace/p/PBWgY/maya-reftool-the-ultimate-camera-reference-manager-new-version

The post Handy RefTool 3.0 speeds Maya ref matching first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the site: FippedNormals is/was a CG store for assets and training you use alongside Blender, ZBrush, Unreal Engine, and the Substance 3D tools, when your pipeline needs fewer guesses and more ready-to-ship bits. Also Plugins, Tutorials, 3d-Printfiles and much more.

The dates you need on your calendar

The FlippedNormals Marketplace will stop accepting new orders on March 31, 2026. After that, purchases are done. Access to previously purchased files stays available until April 30, 2026. After that date, marketplace files will no longer be accessible. Creator payouts have a final date too. The last creator payout happens on April 15, 2026.

April 30, 2026 is also tied to creator operations, because the Creator Dashboard shuts down on the same day customers lose access to file hosting. If you bought something in the past, invoices matter. An invoice was emailed after every purchase, and it should be in the email inbox used at checkout. You can keep what you have locally forever, but you need to get it locally first. Treat April 30, 2026 as a hard donwload deadline, not a friendly suggestion.

What is actually shutting down

This is a shutdown of the marketplace, not a blanket disappearance of everything connected to it. The official plan is a smaller, more focused reboot that pivots away from running a broad storefront with thousands of creators. The new website is planned to focus on FlippedNormals Exclusives and FlipBox.

Why it is happening

The reason given is simple and painfully familiar to anyone who has ever stared at an infrastructure bill and then stared at their revenue chart. Expenses increased significantly over the last years while earnings decreased. Salary reductions were also mentioned as part of efforts to keep things going.

A key detail here is that revenue from FlippedNormals Exclusives was used to keep the marketplace afloat during that period. That combination of higher operating costs, lower earnings, and internal cost cutting still led to the conclusion that the marketplace model was no longer sustainable. If you are reading this as a warning label for other niche CG storefronts, resist the urge to generalize. The only confirmed facts here are the reasons described for this specific shutdown, not the whole sector.

What customers should do right now

Log in, open your library, and pull down everything you have paid for to local storage before April 30, 2026. If your workflow spans multiple machines, back up like you mean it. Put a copy on a second drive. Put another copy wherever your studio keeps long-term project archives. If you rely on invoice PDFs for accounting, store those alongside the content so future you does not have to play detective.

If you depend on the platform for recurring downloads during a production, plan to stop depending on it before the cutoff. The last thing you want is a late-night render emergency that turns into an “amrketplace is gone” surprise.

There is also a specific path for owners of exclusives content. If you purchased FlippedNormals Exclusives on the current marketplace, there is a process to move them to the new site once it launches.

That process requires contacting support after the new site is live, using the support email address. A 100 percent promo code is described as the mechanism to migrate courses to a new account. One more detail that will trip up anyone on autopilot: you will have to make a new user account for the new site as part of that migration flow.

What creators should expect

If you sell on marketplaces, you already know the question creators ask first: what about payouts. The official timeline includes a final creator payout date of April 15, 2026. That is presented as the last payout event. There is also an operational cutoff on April 30, 2026, when the Creator Dashboard shuts down.

If you are a creator and you have analytics, product files, thumbnails, descriptions, license text, or customer support notes you rely on, assume you need to export whatever you can before that dashboard goes dark.

The new site focus, as described, narrows the catalog to FlippedNormals Exclusives and FlipBox. That is a very different value proposition from a wide creator marketplace, even if the UI ends up sleeker. If your pipeline planning relies on “I can always re-download that later,” change the habit. This event is a reminder that availability is a feature you only notice once it is gone.

https://help.flippednormals.com/article/130-flippednormals-marketplace-closing-down-faq

The post FlippedNormals Marketplace closes March 31 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

InstaMAT Studio is out now – a layer-based painting and node-based authoring tool in the same general category as Substance 3D tools like Substance 3D Painter, Substance 3D Designer, and Substance 3D Sampler, with integrations into common DCCs and engines including 3ds Max, Blender, Maya, Unity, and Unreal Engine.

What changes in 2026 is the set of levers available for high-precision, iteration-friendly detailing. Curves Brushes move detail painting toward an editable, control-point workflow. Lazy Stroke helps freehand lines behave. Radial symmetry adds a new patterning tool. Masking and mesh filters expand geometry-aware selection and effects. The new toolbar and hotkeys aim to keep artists in flow instead of chasing settings panels.

And yes, your first experiment should probably be those curve-driven panel lines that always look great right up until the model changes. This time, the system is explicitly designed so the detail survives that upstream change.

Curves Brushes: strokes that stay alive

Curves Brushes let you create editable curve paths on the mesh, using control points rather than a one-and-done freehand stroke. Those curves remain editable after creation, including moving and refining control points, and transforming an entire curve as a unit by translating, rotating, or scaling the path.

A single curves layer can hold multiple curves, and their painting sequence can be reordered. Curves can also be set to erase instead of paint, and they can be closed to form continuous shapes from end point to end point.

Control points support different point types, including linear, symmetrical, smooth, and cusp, with a Joint Smooth setting to control how sharp or fluid the transitions are between segments. Each control point also supports per-point settings for radius, falloff, flow, and rotation, enabling effects such as tapering and gradual fading along the curve.

Curves can orient brush strokes along the path, so details follow the curve’s flow rather than fighting it. Curves also support dynamics for randomised size, flow, rotation, and position to add variation without manually wiggling your wrist into submission. The Curves workflow uses a GPU-accelerated 3D painting engine and does not rely on mesh UVs. The stated result is that curves remain intact even when topology or UV layout changes, which is framed as especially useful for repeating high-precision details such as panel lines, seams, stitches, and decorative elements.

Lazy stroke smoothing, now built in

Alongside Curves, InstaMAT 2026 adds Lazy Stroke, a brush-smoothing feature designed to dampen shaky-hand input and cursor jitter. When enabled, the brush follows the cursor with a delay set by a configurable radius, producing smoother lines for precision freehand painting. The feature is positioned for tasks such as smooth linework, organic patterns, and fine-detail passes where jitter becomes visible in the final maps. If you have ever zoomed in to paint one confident line and instead produced a seismograph reading, Lazy Stroke is aimed squarely at that moment. Try it, then decide if it belongs in production.

Symmetry upgrades: radial joins planar

Radial symmetry painting is new in InstaMAT 2026, enabling repeating brush instances around a central axis. The symmetry axis can be set to X, Y, or Z, the number of repeated instances is configurable, and the angle span can cover full 360 degree patterns or partial arcs. The plane origin is also customizable, allowing the symmetry center to be placed where it is needed on the asset.

Planar symmetry painting is also described as significantly improved. The symmetry plane can be offset to a custom position on any of the three world axes, plane visibility can be customised, and there is an option to mirror the brush on the opposite side of the plane. Symmetry accuracy is described as improved even when painting on meshes that are not exactly symmetrical, targeting the real-world scenario where characters and props have small asymmetries and deformations.

Masking: normals, submesh size, and raytraced AO

InstaMAT 2026 extends its mask set with new workflows aimed at isolating geometry features without hand-selecting everything. The new Mesh Normal Mask can isolate parts of a mesh based on polygon normals and an angle tolerance. The workflow is click-based: click a region, and the mask selects surfaces with similar normal directions. Multiple chosen areas can be defined within a single mask, and tolerance can be adjusted per point. The mask is described as UV independent and stable across topology or UV changes.

The Mesh Submesh Mask can mask submeshes by size and distance, targeting scenes with many similarly sized objects where manual isolation is tedious. There is also a Mesh Ambient Occlusion Mask described as using raytracing to generate occlusion-based selections for isolating crevices, corners, and recessed areas.

Mesh filters and nodes: mirror, bevel normals, drips, and smoothing

A batch of mesh-oriented effects and nodes are listed as part of the 2026 update. Mesh Laplacian smoothing arrives as an option in the Mesh Smooth node, described as producing a more unified surface while better preserving mesh volume compared to traditional smoothing methods that can shrink geometry. The described use cases include cleaning scan data, removing photogrammetry noise, and refining sculpted details while preserving silhouette.

Mesh Mirror can mirror decals, masks, and entire layers, and it can be applied to a layer group to mirror complex effect and mask combinations.

Mesh Bake Bevel Normals is a node for beveling low poly asset edges using a GPU-accelerated bevel normals baker, with procedural masking for selecting which objects or edges to bevel. The behavior is described as procedural, so bevel placement remains correct if the input mesh topology or UVs change.

Mesh Directional Blur is presented as a way to create leak and drip effects by blurring in a specific direction in 3D space, keeping directionality consistent across the mesh surface regardless of UV layout or texture resolution. It includes distortion and falloff controls.

Additional mesh features listed include Mesh Solidify for solidification to prevent rendering artifacts, Mesh Sharpen for definition and detail clarity, and a Mesh Stylized Filter for non-photorealistic texturing options.

InstaMAT UI and workflow: less hunting, more painting

InstaMAT 2026 introduces a dedicated painting toolbar intended to centralise common controls. The toolbar provides quick access to brush and curve settings, including radius, flow, rotation, Lazy Stroke radius, symmetry, and curve-specific controls. It is described as dynamic, updating based on the active layer type so only relevant options are displayed.

There is also a dedicated brush rotation hotkey, described as Cmd or Ctrl+Shift with a left-mouse drag, to rotate the brush, aiming to reduce interruptions during stroke work.

Viewport and gizmo changes include planar translation gizmos for moving a mesh, effect, or mask along two axes at once, plus custom viewport wireframe settings for width and color, and a viewport shortcut overlay that displays hotkeys while painting, using curves, and using the paint projector.

Mesh import settings add options to configure mesh up axis and coordinate system handedness for asset texturing projects.

Integrations: Blender, Unreal, 3ds Max, Maya

The release notes list updates for several integration plugins tied to the latest https://docs.instamat.io/en/Products/InstaMAT_Studio release.

InstaMAT_for_UnrealEngine lists support for Unreal Engine 5.7.3, plus fixes for crashes when creating invalid graph instances, and fixes for broken materials and mesh orientations for Scene outputs. Library previews are added for Mesh-type Graphs and Graph Instances.

Blender integration notes include support for the latest Studio release, improved performance when setting mesh as a graph input, improved performance when resetting graph instance inputs, and fixes for plugin stalls when creating faulty graph instances. Library grid UX is adjusted with fixed cell width, and search results quality is described as improved.

3ds Max integration notes list support for the latest Studio release and a fix for the plugin getting stuck when creating faulty graph instances, plus window icons changed to match the main menu.

Maya integration notes list support for the latest Studio release, improved mesh-as-input performance, fixes for plugin stalls on faulty graph instances, and a fix for incorrect exported textures when using the export dialog window.

InstaMAT Licensing and pricing: what the numbers say

InstaMAT licensing is split across tiers with revenue or funding caps stated for some options. The Pioneer license is free and fully featured with commercial-use rights, with availability limited to individuals or businesses with annual revenue or total funding less than 100,000 US dollars, and it requires attribution.

The Indie license is available for individuals or businesses under 250,000 US dollars in annual revenue or total funding, with an option at 8 US dollars per month billed annually, and a perpetual Indie price shown at 489 US dollars. For Pro, the pricing page lists a Pro subscription shown at 36 US dollars per month billed annually, and a perpetual Pro license shown at 989 US dollars.

If you are evaluating the tool for a pipeline, test it against real assets, real render targets, and real deadlines before it touches a production branch. New tooling should earn trust with results, not promises.

Finally, keep an eye on how the new mesh filters slot into your existing material graph habits. Directional blur for drips in 3D space, procedural bevel normals, and AO-based masking can remove steps that otherwise happen in separate tools. If it holds up, it reduces context switching. If it does not, at least you learned it on a duplicate branch instead of the hero asset.

Also, do not skip the boring step: validate exports, naming conventions, and texture packing against your engine ingest rules before you fall in love with a shiny new brush. The most dangerous bug is the one that looks like a style choice until delivery day.

InstaMAT Test: Painting, Procedurals and Pasta

The post Abstract ships InstaMAT 2026 Curves Brushes first appeared on DIGITAL PRODUCTION and was written by Manuel Kotulla.