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: OctaneRender is a GPU renderer that sits after lookdev and before finals, and it talks fluently with DCC plugins plus OpenUSD and MaterialX, when it is in a good mood.

The alpha, the scope, the fine print

OctaneRender 2027.1 Alpha 1 is out as a public development build intended for testing by experienced users, and it is explicitly not positioned as production ready. Scenes saved in this alpha are not guaranteed to stay compatible with future builds. The build is Windows only right now, the minimum required NVIDIA driver version is 572. The downloads listed for this alpha are the standalone Windows installer and a ZIP archive. Other build types are planned for subsequent releases.

Real time neural viewport, now with thunderbolt energy

The headline feature is a new real-time neural viewport mode that replaces the previous real-time mode. It is built on the neural radiance cache framework introduced in OctaneRender 2026. The alpha describes the new mode as enabling near noise-free interactive rendering at very low sample counts compared to traditional path tracing. The mode is designed to preserve the spectral path-tracing behaviour while improving interactive feedback, even under complex lighting conditions. It combines internal research with NVIDIA DLSS Ray Reconstruction.

In the UI, the alpha notes a dedicated toggle. The real-time neural viewport can be enabled or disabled using a Thunderbolt button in the viewport components bar. Quality settings for the real-time denoiser live under the imager node, with the goal of balancing performance and quality depending on the hardware. If you have ever watched a veiwport go from soup to something readable right as a director walks over, you already know why this matters. The promise here is faster clarity, not just faster pixels.

Upscaling joins the party: DLSS and FSR modes

This alpha adds support for new up-sampling modes based on NVIDIA DLSS and AMD FSR. The build also references AMD FSR 3. The implementation sits in the Upsampler section of the imager node, alongside other up-sampling methods. On the DLSS side, the referenced technology page describes DLSS Ray Reconstruction as an AI method that replaces hand-tuned denoisers with an AI network that generates higher quality pixels between sampled rays in intensive ray-traced scenes. Those statements describe DLSS generally, not a specific Octane integration result. This renderer is CUDA based, and the Windows alpha focuses on NVIDIA GPUs (Big surprise!).

AI Light 2.0: sampling that tries harder

AI Light 2.0 lands as a new light sampling method intended to resolve noise faster. AI Light is described as a hierarchical algorithm for sampling scenes with many light sources, and the update is positioned as a major revision compared to the original introduction back in OctaneRender 4.0.

For lighting heavy setups, this is the kind of change that can alter how fast you converge on creative decisions. If your daily routine includes juggling dozens of practicals, emissive set dressing, and a few too many hero gobos, any sampling improvement tends to show up right where it hurts, in the first minutes of iteration.

USD export and a more hands on USD workflow

OpenUSD workflows get a concrete upgrade. Geometry export to USD is included, and the build adds the ability to export a scene in USD format. The cgchannel overview also notes that geometry export in USD can include limited support for USD Preview Surface materials.

On the editing side, the standalone edition includes a USD Stage editor that allows selecting variants and layers without saving and reopening the USD file. The alpha also adds built in support for authoring variants and muting USD layers directly within the USD geometry archive.

If your pipeline already treats USD as a transport layer between layout, lookdev, lighting, and downstream tools, these changes aim straight at friction. More export options reduce the number of awkward handoffs that turn into late night chat messages that start with “hey quick question….”

UVs and geometry: more room for messy reality

The UV ceiling changes, because production UVs are never as polite as tool demos. The maximum number of UV maps allowed per primitive increases to 10, up from 3, and UV sets can be assigned arbitrary names in DCC apps that support it.

Other geometry and attribute changes include support for named UV vertex attributes, support for using vertex attributes in bump maps, support for colour vertex attributes in vertex displacement, and a Vectron tube primitive addition.

If you have ever inherited an asset with five UV sets and a note that says do not touch UV4, you now have more breathing room. The named UV support also helps keep humans oriented when the same mesh carries multiple UV purposes across shading, decals, and baking.

Changelog nuggets for TDs who read release notes for fun

Beyond new features, the alpha lists a spread of resolved issues and smaller changes. A few examples include fixes around DDS preference crashes, Alembic instancing, several MaterialX node behaviors, and multiple OpenUSD import issues such as points not loading correctly and animated point instances importing incorrectly.

The Lua API gets deprecations in geometry exporter properties, including moving from renderSizeX and renderSizeY to textureRenderWidth and textureRenderHeight, and replacing writeOcsData with embedNativeData. A small UI level tweak removes Clock Rate and Cores fields from the GPU information panel. This is where you start thinking about tool glue. If you have scripts that poke exporter properties or automate export settings, the deprecations are your early warning sign to check for breakage.

Availability, licensing, and pricing

This alpha is available alongside the stable OctaneRender 2026 releases. The software is offered as rental only via Studio+ subscriptions. The pricing listed is €23.95 per month or €239.88 per year, and the Studio+ subscription page also lists an annual price presented as 19.99 € per month billed yearly.

Free Prime editions are also available for OctaneRender and Octane X, with the Prime editions limited to rendering on a single GPU and offering a smaller set of DCC integration plugins. The alpha download links themselves require a licensed customer login for access. That is where OTOY enters the picture in the most practical way possible.

Production reality check

This build is explicitly framed as experimental, and it is not recommended for production use. That guidance aligns with the normal alpha reality: features change, files drift, and stability work continues in later builds.

New tools and innovations should always be tested before use in production, ideally on representative scenes with your actual assets, shading conventions, and deadline pressure.

What to watch while you test

The big workflow test is whether the neural viewport mode makes iteration measurably smoother on your scenes, and whether AI Light 2.0 shifts your sampling strategy. The second test is whether USD export plus USD Stage editing reduces round-trip times in YOUR pipeline. The third is whether the DLSS and FSR upsampler options behave predictably inside your lookdev and review loop, especially when you rely on consistent framing and visual stability.

https://render.otoy.com/forum/viewtopic.php?t=85551

The post OctaneRender 2027.1 alpha goes neural first appeared on DIGITAL PRODUCTION and was written by Manuel Kotulla.