For those who don’t know the tool: Autodesk Flame is the finishing suite that lives between conform, comp, and delivery, with companion stations like Flare and render muscle via Burn for facilities that enjoy sleeping sometimes.

The big three: metadata, scribbles, depth

Flame Family 2027 puts a spotlight on three things that tend to break at the worst possible moment: clip metadata, frame-level notes, and depth workflows. The metadata work targets frame-based metadata keys and keeps them intact from import through export. Annotations land as a practical review tool. Flame Family 2027 can add annotations to frames in the Player or in a Viewport, and it can also display the list of annotations on the current frame. Machine learning shows up as a Depth map feature. Flame Family 2027 can generate a Depth map using internal or external machine learning models.

Metadata that survives the trip

Flame Family 2027 treats metadata as something that should survive real production, not just an import dialogue. In Batch, a Metadata node can view and modify the metadata of a clip. Open Clip can define metadata keys and values to be ignored or modified on a per-feed basis, which gives facilities a way to standardise what comes in and how it gets normalised before it spreads everywhere.

Tokens get a larger role in that same cleanup story. Flame Family 2027 can define Custom Tokens and also limit the display of resolved tokens to a chosen number of characters. Preferences can set Custom Tokens to be used throughout the application, and Centralised Components can deploy system-based Custom Tokens across a facility using a dedicated workflow. That combination aims straight at consistency: one naming plan, one token vocabulary, fewer surprises at export time.

There are also Python API additions tied to the new metadata workflow, aimed at facilities that build glue code around ingest, naming, and publishing. The exact scope of those additions is not specified anywhere I could find it.

One detail worth calling out for day-to-day operators: Flame Family 2027 adds context-menu copy and paste for characters in text fields, including Copy Text, Cut, Paste Text, and Delete, plus a Paste Text option when nothing is selected. Dialogs with multiple text fields can also use Tab and Shift + Tab to move between fields, as long as one field is already in editing mode. None of this sells a subscription, but all of it reduces small daily friction that adds up.

About a third of the way in, the mteadata story boils down to this: fewer per-shot fixes and fewer one-off scripts to keep identifiers, flags, and frame-level tags from vanishing mid-pipeline.

Annotations that behave like a real tool

Annotations in Flame Family 2027 are not limited to a single panel or a single kind of workflow. Artists can add annotations to frames in the Player or in a Viewport. Explorer can access a list of Markers and can also display the list of annotations on the current frame. Snapshot can include annotations, which helps when review happens outside the application and you still want the note to travel with the image. Also: They are somewhat accessible via Python, but so far only “.has_annotations” and “.clear_annotations()“. That is a start, but not a full integration into the overarching pipline that keeps the added Memes from Prep intact until delivery.

Effects also gets marker support: Markers and Segment Markers can be added from the Effects environment. That is a quiet workflow bridge between building looks and keeping editorial or review signposts in sync.

Keyboard shortcuts shift a bit to accommodate the new annotation layer. In the Flame keyboard shortcut profile, Delete or Backspace is assigned to Delete. Tracking shortcuts change too: Tracking Delete Current KeyFrame and Go To Previous in Action, GMask Tracer, and Image move from Delete or Backspace to Shift + Delete or Backspace. Search also changes: F12 no longer opens Search; it now opens Toggle Annotations Display instead. Space + Tab still opens Search, and F16 can be used on macOS.

Tangent panel users get new mapper functions for annotations. Tangent Mapper adds Annotations control for toggling the Annotations layer display, plus navigation functions for previous and next annotation. Data management functions are also added, including Clear Unreferenced Cache for the current project and all projects.

Depth maps, now with fewer excuses

Depth maps via machine learning arrive as a production feature in Flame Family 2027.

A Depth map can be generated using internal or external machine learning models. The Tools workflow can generate a Depth Map using a machine learning model, then create a matte from that Depth Map inside a Selective. This positions depth as an artist-facing selection primitive, not just a technical curiosity.

Let’s quote the documentation: New machine-learning-based models are available as Analysis Type options to generate depth data. ML Depth Indoor and ML Depth Outdoor are internal machine learning models, while Load Model allows an external ONNX depth extraction model to be loaded.

The Documentation does not specify which machine learning models exactly are included (or at least, I couldn’t find it), which external model formats are supported, or what hardware constraints apply. Even without those details, the intended use is clear: build depth, turn it into mattes, and iterate quickly.

Like any ML feature, you will still want to test it on your own footage, your own lens mess, and your own deliverables before trusting it in production. That includes checking edges, temporal stability, and failure cases on smoke, hair, reflections, and anything else that enjoys humiliating clever algorithms.

Conform, color, and the rest of the plumbing

Flame Family 2027 also invests in pipeline plumbing, the kind that keeps facilities from inventing new swear words. Conform can import OTIO files in the Conform environment, via OpenTimelineIO. That gives conform artists a more direct path for timeline interchange when the upstream system exports OTIO.

Color management updates land via OpenColorIO, updated to version 2.5.1. The Sources do not describe behavioral changes from that update, only the version number.

Project management adds OpenEXR uncompressed as a Cache and Renders format for floating-point content. For facilities that lean on float caches, this adds another option alongside existing cache formats.

Configuration and OS support expands to include Rocky Linux 9.7. DKU 21.0.0 is listed as Rocky Linux only and includes support for Rocky Linux 9.7 and an updated NVIDIA driver. The Sources do not specify the exact driver version.

Hardware I O support gets AVIO updates with updated AJA and Blackmagic Design drivers. Service Monitor gains new Diagnostics intended to help troubleshoot configuration.

User settings import changes affect Setup. User settings can be imported on a new system before the application is launched for the first time, and importing a user profile overwrites all existing user settings.

Backburner 2027.0 is a minor update with fixes and no visible changes for end users, via Autodesk Backburner. Burn can be installed on macOS workstations, which expands where that render companion can live.

As always, new features and new workflows deserve a proper test pass on real show material before they touch a live delivery schedule.

The post Autodesk Flame 2027: metadata and depth maps first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: 3ds Max is a DCC for modeling, animation, and rendering, often paired with Arnold and OpenUSD for lookdev and pipeline handoffs across VFX, broadcast, and realtime.

The newsroom tries to explain Max to itself

Over in the Digital Production newsroom, there is a special kind of silence that happens whenever I say the words modifier stack. Half the team nods like they understand. The other half quietly searches for a button called “Make It Pretty”. So here is the deal. 3ds Max 2027 lands with new modeling tools, new deformation noise, selection upgrades, performance work, viewport cleanup, and a few foundation updates that matter to pipeline folks who like their tools modern and their crashes vintage.

Smart Bevel: post Boolean intersections, less cleanup

Boolean modeling can be fast, brutal, and wonderfully irresponsible. The new Smart Bevel feature targets post Boolean intersections and focuses on creating cleaner bevels with less fuss. Smart Bevel is designed for post Boolean intersections and is presented as a way to create cleaner and more intricate bevels with ease. It is framed as a dedicated approach to getting better looking edges after Boolean work, aimed at reducing the need for manual cleanup.

This fits neatly into the hard surface rhythm a lot of artists know too well: cut the shape, stare at the resulting edge spaghetti, then spend quality time repairing the part that was supposed to be the fast part. Smart Bevel tries to make that edge repair step less of a ritual. And yes, Bela asked if this means booleans are finally safe. The answer is still no. But fewer sharp edges turning into a bveel shaped tragedy is a welcome upgrade.

Extrude and Spline Chamfer: splines get better directions

The Extrude modifier now supports a custom direction workflow. Splines can extrude with orientation and direction rather than only local Z. For spline driven workflows, that is a practical change, because it reduces the need to pivot objects around just to make an extrusion behave.

Spline Chamfer also gets updates, including the ability to use a fixed radius for consistent circular corners. This focuses on predictability, which matters when spline corners must stay consistent across revisions, instancing, or exported geometry. If you have ever watched a single inconsistent corner ripple into five downstream fixes, you already know why this is worth caring about.

Noise Plus: more fractals, animation, tiling controls

A new Noise Plus modifier arrives with new fractal types, animation ability, and tiling controls. It is positioned as a more capable procedural noise option for pushing results further. The legacy Noise modifier also gets updates. It now uses a modern Qt interface and supports Paramblock2 for user-defined defaults. The animated Phase parameter now uses linear interpolation rather than ease in and out, for more predictable animation behaviour. For deformation work, predictable interpolation is the unglamorous hero. It keeps animation curves from feeling like they are fighting you.

Field Helper: more precise component selections

A new Field Helper is introduced for more precise component selections for manipulating items, including driving selections.

This is paired with a performance note elsewhere in the release that Volume Select soft selection performance has been improved for polys. The stated goal is smoother, more responsive soft selection performance on high poly objects. In practical terms, selection quality and selection speed both matter. Selection is not just a click. It is the start of most modeling and deformation decisions, and it tends to multiply into every other step you do.

Viewport grid and display improvements: cleaner and less annoying

Viewport grid and background display have been refreshed to provide a cleaner, more focused environment. This is the part where the newsroom says, “Cool, so the background looks nicer!”, and searches for snacks.. Then a Max user quietly smiles, because they live in the viewport. The viewport is where time goes, and small friction reductions add up quickly.

Arnold for 3ds Max: MaxtoA updates

The included Arnold for 3ds Max plug-in is version 5.9.0. Updates since 3ds Max 2026.3 include lightweight OpenUSD instancing, a new hair scattering mode, more flexible light sampling, plus other enhancements and bug fixes. If your pipeline touches Arnold, these plugin updates matter because they affect how features show up inside the host.

Retopology and Shape Map: faster processing, better targets

Flow Retopology has been relocated to Tools and is now under Tools > Flow Retopology to make it easier to find and access as part of core modelling workflow. Retopology performance is described as improved via faster ReForm processing. It is presented as providing quicker results and improved support for meeting quad target goals, with more reliable and consistent outputs.

Shape Map performance is also described as much faster, reducing wait times when working with shape keys and morph targets. This is a more responsive shape-based workflow, especially with complex character rigs or detailed morphing operations.

Colour management: sampling and OCIO

Colour management gets updates. You can sample underlying colours from the scene space in windows that support it, including viewports and the Rendered Frame Window. The Colour Selector eyedropper includes options to sample display colour or sample scene colour. The software also uses the latest version of the OpenColorIO library (OCIO v2.5.1).

Autodesk Assistant: tech preview help inside the app

A tech preview called Autodesk Assistant is included. It is described as an AI-powered tool / LLM that helps you quickly find information about features and workflows directly within the product. This might be cool for beginners, or if you are looking for that feature you know is in there, but can’t find. Only time will tell if it works.

Bela asked if it can also explain why someone would stack twelve modifiers and still sleep at night. No promises were made.

Autodesk prices Subscriptions are at 255 USD per month or 2,010 US Dollars a year. In many countries, artists earning under 100,000/year and/or working on projects valued at under 100,000 Dollars per year can get the Indie subscription, which now cost 330 US Dollars a year. Before you roll this into a pipeline, do the boring but essential checks. Open hero scenes, validate modifier stacks, confirm export paths, and compare renders. New tools and innovations should be tested before use in production.

https://help.autodesk.com/view/3DSMAX/2027/ENU/?guid=GUID-7CC2F041-F797-4DB9-B2F9-326AAB994F37

P.S. If you are asking yourself, “Where does he get the cat pictures?” Be in a chat with Bela for any amount of time, and you’ll have them, too.

The post 3ds Max 2027 is here. first appeared on DIGITAL PRODUCTION and was written by Mike Kuhn.

For those who don’t know the tool: Blender is the free all in one DCC for modeling, animation, rendering, and export tasks like USD, with Eevee for realtime previews, Cycles for finals, and a Compositor that keeps quietly expanding its job description.

The release vibe: refine, then refine again

Blender 5.1 arrives with a clear theme: make everyday work feel lighter. The focus sits on quality of life improvements, stability, and polish, following a “Winter of Quality” push that solved 350 important issues and also cleaned up code to make future improvements easier.

That mindset shows up everywhere. Some changes are the sort you notice instantly. Others only reveal themselves after a week, when you realize you have not sworn at a dialog box even once. Progress comes in many forms. It is still the same familiar toolset. The difference is how often it gets out of your way.

Raycast: a shader node that likes to ask questions

A new Raycast shader node lands in the material system, built around a simple idea: shoot a ray, get useful surface information back, and use it to drive looks. That unlocks effects that rely on the closest point on a surface from the ray source, or the distance to it. There are demo files showing setups like toon shading and an X ray render effect.

There is also a practical warning: Raycast can be computationally expensive, and baking its output is suggested as a way to improve render times when needed.

Rendering: faster compiles, leaner memory, quicker frames

On the realtime side, Eevee speeds up material compilation by pre processing shader sources. In the standard Barbershop text scene benchmark, GPU shaders compile 25 to 50 percent faster across operating systems. Memory also gets attention. Eevee reduces texture memory use via texture pooling, helping scenes fit into less VRAM.

Cycles picks up performance gains too. GPU rendering improves by about 5 to 10 percent for many scenes, and HIP RT ray tracing is enabled by default on AMD GPUs. If your day includes lots of lookdev iteration, the combined effect is straightforward: fewer pauses between decisions.

Animation and rigging: the biggest speed win in the room

If you care about playback, Blender 5.1 comes with a headline worthy improvement: actions and shape keys evaluate significantly faster, with reported gains ranging from 4 percent to 304 percent in frames per second depending on the file. For cleanup work, the Graph Editor adds a Gaussian smoothing modifier that smooths curves non destructively. It is also explicitly described as resource heavy, with guidance not to use it on too many curves at once.

There are also small but practical timeline and editor touches that help animation feel less fiddly, like interpolation line colors indicating interpolation type in the Dope Sheet and menus.

Compositing and editorial: nodes that earn their keep

The built in Compositor adds a Mask to SDF node. It converts a mask into a Signed Distance Field by computing the distance of each pixel from the mask edges. That supports effects like edge glows, eroding or dilating mask edges, and distance based effects like procedural blurs.

The compositor also gains utility nodes including Boolean, Integer, Vector, and Index Switch, plus support for the existing Radial Tiling node. Speed matters here too. Several key nodes are faster, including Blur, Directional Blur, Vector Blur, Glare, Lens Distortion, and Anti Aliasing, described as 1.2x to 2x faster.

In the Sequencer, the Blade tool adds a box gesture that supports ripple editing, aimed at quicker cutting. Taken together, the message is clear: the VFX and video toolsets are being treated like first class citizens, not the side quest you only visit when your shot count gets scary.

Modeling and sculpt: a pile of small wins

Modeling sees a mix of performance and wrokflow tweaks. Filling for text objects improves, expanding the types of fonts that behave well as 3D text. Filling in general is up to five times faster, especially for n gons with many sides. Snapping adds an option to snap to the center of faces. In sculpt and paint, one visible addition is a Blur brush for blurring surface colors in Sculpt mode.

Grease Pencil: holes, at last

Grease Pencil gets notable workflow improvements, including better handling of strokes and fills and new ways to cut holes in shapes. Holes in fills can be created either via new operators that perform Boolean style operations or via the SVG importer. The draw here is practical: importing SVG and PDF content becomes easier to integrate without the same fill weirdness described in the feature overview. If you have ever built a workaround stack just to preserve negative space, this one lands with a satisfying thud.

Geometry Nodes: more rig friendly, more volume friendly

Geometry Nodes adds a Bone Info node that makes it possible to access bone position data. There are also new nodes for working with volume grids, including nodes for dilating, eroding, and clipping volume grids.

UI, file I O, and pipeline glue

The UI picks up just under 100 fixes and feature improvements, including the ability to search for controls by name in Preferences. Other practical UI touches include resizing quad views interactively by dragging the center point, and copying and pasting nodes between separate instances. On file formats, new options include AVIF export. Updates also land for USD, glTF, and FBX, with FBX files now including Shape Key normals for better compatibility with game engines like Unity.

For pipeline integration, support includes Python 3.13 and OpenColorIO 2.5, matching the CY2026 spec for the VFX Reference Platform. For virtual reality projects, the arc teleportation system is described as completely rewritten, and OpenXR is supported on macOS.

Availability and licensing

Blender 5.1 is a free download. The source code is available under the GPLv3 license. That free and open model is not new, but it still matters. It shapes how fast features get tested in the wild, how quickly workflows spread through studios, and how often a random late night fix becomes a shared win by morning.

The only remaining job is the boring one: install, test, validate, and only then roll it into serious work. Even a tool with a good mood still deserves a proper pipeline check. And yes, the Blender Foundation clearly wants this release to feel like a calm upgrade, not a reinvention.

https://www.blender.org/press/blender-5-1-release/

The post Blender 5.1 is here first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: DJV is an open source image sequence viewer and playback tool for VFX and animation. It runs on Linux, macOS and Windows, supports OCIO colour management, and is typically used for dailies, shot review and quick sequence inspection without licence infrastructure.

DJV 3 has been evolving through incremental releases, culminating for now in version 3.3.3. We missed the earlier 3.x updates, so let’s summarise.

Version 3.3.3 is the latest tagged release. It adds one feature and resolves two bugs. The new feature enables the Escape key to close the secondary window. The fixes address a flipped export issue and incorrect tool tooltips. No further technical detail is provided in the release notes regarding the root cause of the export flip or the tooltip behaviour. Not independently verified at press time. Prebuilt binaries are provided for Linux x86_64, macOS arm64 and Windows amd64. Assets include tar.gz, dmg, exe and zip packages. SHA256 checksums are published for the binaries. To understand the significance of 3.3.3, it is necessary to look at the broader 3.x changes.

Sequence awareness and file handling

One of the more practical changes in the 3.3 branch arrived in version 3.3.0. The built in file browser can now display image sequences as a single item with an associated frame range. Instead of listing every frame as an individual file, the browser aggregates them into a sequence entry.

This change affects directory navigation and review workflows directly. For facilities handling large EXR sequences, reducing file list clutter improves browsing speed and visual clarity. The release notes describe this as a display change in the built in file browser. No additional details are given about sequence detection rules or supported naming conventions beyond the example provided for command line input.

The command line in 3.3.0 now accepts file sequences written in hash notation, such as render.#.exr. This aligns with established VFX naming patterns and allows users to load sequences from the terminal using shorthand notation.

Keyboard shortcuts expanded

Keyboard customisation received significant attention in 3.3.0 and 3.3.2. Version 3.3.0 introduced primary and secondary keyboard shortcuts. It also added a search box to the keyboard shortcut settings. The Tab key can now be assigned to shortcuts, including combinations such as Ctrl+Tab and Ctrl+Shit+Tab for changing the current file. The spelling in the official notes reads Ctrl+Shit+Tab.

A fix in 3.3.2 addressed the keyboard shortcuts search box. Another fix in 3.3.0 resolved keyboard shortcut behaviour in the secondary window. In 3.3.2, the version number was added to the window title, and a command line flag was introduced to print the version. A dialog for displaying system information was also added. These additions are small but relevant for deployment and support scenarios. Being able to query the version from the command line simplifies scripting and diagnostic workflows.

Mouse behaviour and interaction changes

Version 3.3.0 updated mouse configuration in several ways. Extra 1 and Extra 2 buttons were added to the mouse settings. A frame shuttle scale was introduced in the same settings panel. The default mouse mapping was changed so that the left mouse button performs frame shuttle and the middle mouse button pans. This represents a behavioural change for existing users migrating from earlier versions. A separate fix in 3.3.0 corrected swapped middle and right mouse buttons in the settings.

In 3.3.2, pixel and mouse binding labels were added to the colour picker and magnifier tools. The release notes state that both tools now update when picking with the mouse. This suggests synchronised feedback between cursor interaction and tool UI. Version 3.3.3 then added Escape key support for closing the secondary window. Together, these changes reflect ongoing adjustments to interaction ergonomics rather than new feature domains.

Colour management and UI indicators

DJV 3 integrates OCIO for colour management. In 3.3.0, the colour tool was updated to display the OCIO configuration name. At the same time, the path for the OCIO and LUT file names was hidden within the tool.

Status bar indicators were added in 3.3.0 to display whether colour controls, the audio sync offset or the output device are enabled. In 3.3.2, additional status bar indicators were introduced to display when mirroring is enabled.

In 3.3.0, compare overlay and difference modes were fixed to prevent image flipping. In 3.3.3, a flipped export issue was also fixed. The two issues are described separately in their respective release notes, with no explicit statement linking them.

The cumulative effect is a reduction in unexpected image inversion behaviour in both interactive comparison and export contexts, based on the wording of the fixes. The specific code paths affected are not described. Not independently verified at press time.

Playback behaviour

Version 3.3.0 modified playback speed behaviour. The release notes state that playback speed can be increased and decreased by pressing forward or reverse multiple times. This implies incremental speed changes tied to repeated transport input. A magnify tool was added in 3.3.0, along with grid labels. The magnify tool was later enhanced in 3.3.2 with pixel and mouse binding labels and updated mouse interaction behaviour.

Platform specific fixes and build updates

The 3.3.x series includes multiple platform and build fixes.

Version 3.3.0 fixed compilation on Rocky 8 and addressed excessive CPU usage caused by the clipboard on Gnome. It also fixed the mouse settings to only show the Command key on macOS.

Version 3.3.1 was dedicated to macOS package fixes. No further detail is provided in the release notes.

Version 3.3.2 fixed an issue with the window title bar appearing off screen.

The 3.3.0 release notes list a library update to SDL2 release 2.32.10. No additional third party dependency changes are described in the provided notes.

Version 3.3.3 assets include Linux, macOS and Windows builds, with SHA256 hashes published for verification.

What has not changed

Based on the official notes provided, the 3.3 branch does not introduce new file format support, new codec integrations, or changes to core rendering architecture. There is no mention of GPU acceleration updates, threading model changes or cache redesigns in the referenced releases.

There is also no pricing information, as DJV is distributed as free open source software via GitHub.

Any assumptions about performance improvements, stability gains beyond listed fixes, or pipeline scale suitability would be speculative and are not supported by the cited documentation. Not independently verified at press time.

Version 3 so far

Taken together, DJV 3 up to 3.3.3 reflects iterative refinement. Sequence aware browsing, expanded shortcut handling, improved mouse customisation, clearer OCIO labelling, and a series of bug fixes define the branch.

For studios using DJV as a lightweight review tool, the changes are operational. They reduce friction in file browsing, clarify status indicators, and address specific bugs such as flipped compare modes and flipped export.

As always, new tools and updates should be tested in controlled conditions before deployment in production environments.

// https://github.com/grizzlypeak3d/DJV

The post DJV 3.3.3 fixes flipped export and adds Escape first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Blender 5.0 introduces a built‑in ACES 2.0 view transform, available in both standard and high dynamic range (HDR) variants. This is integrated via OpenColorIO (OCIO) and provides a direct alternative to Filmic and AgX transforms. It includes heuristics to better match display and view names, enhancing compatibility between Blender’s interface and standard ACES workflows. This is especially helpful for freelancers and smaller studios that do not use a full ACES OCIO configuration.

HDR and Wide-Gamut Support and Export Features

The release also brings built‑in support for Rec.2100‑PQ and Rec.2100‑HLG display transforms, enabling accurate HDR grading workflows. For wide‑gamut previews and output, artists can now choose Display P3 or fall back to sRGB for broader compatibility. Export formats including PNG, TIFF, WebP, and JPEG can now be rendered in P3 or Rec.2020, though HDR image file export is not currently possible. Exported stills thus benefit from wide‑gamut range, and video export in HDR is supported.

To activate HDR and wide-gamut modes, proper hardware and system conditions must be met. On macOS this includes Apple Silicon hardware; on Windows users must enable HDR and use the Vulkan backend; Linux requires Wayland + Vulkan.

Workflow Enhancements

Updates to Blender’s colour workflow include a revamped colour picker with both Linear RGB and Perceptual RGB sliders, allowing artists to work directly in scene-linear or sRGB spaces. Shader brush and palette colours are stored in scene-linear but can be edited in sRGB, facilitating consistency in compositing and node workflows. Additionally, a new “Convert to Display” compositor node simplifies converting scene-driven colour into output display space.

Render and Baking Improvements

Blender 5.0 delivers broader render improvements beyond colour. The Voronoi texture node now runs substantially faster due to a new hashing algorithm, although its results differ from previous versions. The ‘Z’ render pass has been renamed to ‘Depth’ for clarity. Multires baking workflows see enhancements: support for n-gon faces, better subdivision level and UV interpolation handling, the ability to target selected-active images, and support for vector displacement baking from Multires.

Why This Matters for Artists

The inclusion of a built-in ACES 2.0 view transform, HDR/wide-gamut display support, and direct export capabilities marks a practical evolution for Blender. These features streamline HDR and colour-accurate workflows within Blender’s environment, reducing reliance on external OCIO configurations. Colour picker enhancements and a “Convert to Display” node support artist control and output consistency. However, hardware compatibility and proper pipeline testing remain essential. And, when you want to work in big poroductions with Belnder, ACES colorspaces are a standard these days. So, it is going towards making Beldner a high-end-tool.

The post Blender 5.0 Ships Built-In ACES 2.0 View Transform first appeared on DIGITAL PRODUCTION and was written by Bela Beier.