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.