At Unite 2025, Unity unveiled its official roadmap through 2026. The presentation focused on the core engine, the package ecosystem, and Unity Gaming Services, while the leadership repeatedly stressed one theme: stability before novelty. The roadmap confirms a measured rollout of new architecture and workflow improvements under the Unity 6 generation. Upcoming versions will follow a quarterly supported-update cadence through 6.7 LTS in 2026.

Verified Quality, Smaller Deltas

Unity’s Production Verification (PV) programme, now central to its release process, links internal and external studios to test new features in real projects. The company reports a 43 percent faster regression-fix time and a 54 percent smaller backlog since expanding PV to partners such as Kinetic Games and Ten Chambers.

Diagnostics and analytics are being merged under the Developer Data Framework, a unified telemetry system that provides early issue detection while keeping player data consent “cautious by default.” Engine diagnostics now ship active in new projects and can be managed or disabled at runtime.

Signed Packages and Core Standards

Security and traceability in the package ecosystem were a major focus. Starting with Unity 6.3, the editor gains built-in support for signed packages and visible trust indicators in the Package Manager. Unsigned packages trigger warnings, while verified authorship will be handled either by Unity, an organisation admin, or an approved publisher. From early 2026, Asset Store publishers can distribute extensions directly as Unity Package Manager (UPM) packages with strong versioning and dependency metadata. Unity calls this framework its new Core Standards, a more or less polite term for supply-chain hygiene.

Editor Quality of Life

The Unity Hub and editor receive long-requested usability upgrades. In 6.3, the main toolbar becomes customisable, the grid and snapping systems are rebuilt, and the internal search database moves to LMDB for large-project speed. A rewritten scene hierarchy using UI Toolkit handles “millions of objects” and finally introduces horizontal scrolling.

UI Toolkit itself gains world-space UI, custom shaders, filters, and vector graphics. Despite the focus on the new system, Unity reaffirmed long-term investment in uGUI, including performance fixes drawn from its own Survival Kids game. The Graph Toolkit moves from an experimental package into the core editor, becoming the default node-based framework. Shader Graph receives major upgrades, including nested properties and UI/terrain templates, with stencil support due in 6.5.

Graphics and Performance

Lighting tools gain XAtlas UV packing, a unified ray-tracing API, and early work on dynamic global illumination for the Universal Render Pipeline (URP). A shared Render Graph backend and cross-pipeline upscaling framework are being introduced to unify HDRP and URP features. Vulkan and DirectX 12 remain the focus for desktop, with DX12 now the Windows default after memory-usage optimisations and smoother pipeline compilation. Burst 1.8.25 adds cross-CPU determinism for consistent multiplayer simulations, and new build settings reduce shader compilation time by up to 45 percent in URP.

CoreCLR, ECS and the Long Merge

A major architectural shift is the gradual migration from Mono/.NET to Microsoft CoreCLR, promising higher runtime performance and full modern C# compatibility. An experimental desktop player using CoreCLR is planned for 6.7, followed by a CoreCLR-powered editor. The Entity Component System (ECS) becomes a core engine package in 6.4, with unified transforms for ECS and GameObjects to follow. Unity intends to allow ECS components to attach directly to GameObjects without re-architecting existing projects, an incremental unification rather than a rewrite.

AI Gets “Agentic”

Unity introduced Agentic AI tools,editor-integrated assistants that understand project context, index assets, and offer diff-verified code suggestions. Agents will analyse profiler data for optimisation hints, assist in UI Toolkit layouts, and generate assets such as skyboxes or textures through a built-in chat interface. All code changes must be manually approved, with Git-diff visualisation built in. These features begin rolling out with 6.4 and expand later with visual-context inputs and performance debugging. So, another tool with a barely working assitant nobody asked for.

Platform Toolkit and Device Expansion

The new Platform Toolkit abstracts console and device SDKs, allowing cross-platform certification code to be written once. The API launches in 6.3 with successful Xbox and Nintendo Switch 2 certification already confirmed. Unity supports Nintendo Switch 2 out of the box (HDR, 120 Hz, 4K output), and continues work on Android XR and Meta Quest platforms via OpenXR. Mobile updates include a rewritten Apple integration layer in Swift, due in 6.6, and Android startup optimisations through thin LTO builds in 6.5. Unity WebRequest now defaults to HTTP/2, cutting server load by up to 40 percent in internal tests.

A Pause for Foundations

Unity confirmed it has paused work on new animation and world-building workflows to focus on architectural stability and the CoreCLR migration. The company says this pause will accelerate the delivery of foundational systems across the entire engine stack.

Reality Check

Unity’s roadmap finally reads less like a sales pitch and more like a maintenance schedule. Most features arrive through incremental 6.x updates, with verification baked in before rollout. Production teams should, as always, test every new version before adopting it in live pipelines.

The post Unity’s 2026 Roadmap: CoreCLR, Verified Packages, Fewer Surprises first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

When a group of architectural illustrators set out to test Chaos Vantage, they planned a few small real-time experiments. Instead, they built Unbox, a fully animated short film where an architectural cube folds open like a mechanical puzzle. From “a few little minis,” it grew bigger – there are worse outcomes for a stress test.

DP: What was the initial spark for testing Chaos Vantage and why risk it on a narrative short instead of a comfy archviz sizzle?

Peter Stulz: Honestly, at first we intended to do a few little minis in Vantage… and then the second test spinned out of control and grew bigger each day. But no regrets, we embraced the prospect to develop a narrative architectural piece ourselves.

You see, we are architects and not an animation studio. So this was a massive learning journey for us: sequencing shots in an attractive manner, telling a story, how to reveal information and how to retain it… Vantage was fantastic, because it allowed us to be quite experimental here, make mistakes and learn while working on it.

DP: Give us the pipeline in one breath: DCC(s), renderers, interchange (Alembic/FBX/USD), and the editorial path from storyboard/animatic to picture lock.

Peter Stulz: Natively we use 3ds Max in our studio, still the main tool for architecture. Our studio mostly renders in Corona Render, but I feel very home in Vray. For asset creation I use Blender which then sent to Max via FBX. The animation was rendered in Vray CPU – 5 months was tight enough and I know Vray as an engine that delivers without funky surprises.

For the creative part, I drew initial sketches and the storyboard in Procreate. We were lucky to have my friend and cinematographer Olaf Aue (LinkedIn) on board, who was kind enough to share some of his Know-How. The storyboard was straight away sequenced in Resolve with some stand-in SFX and music, just to get a feeling for timing. The stills were then replaced with Vantage Previz shots; the iteration frequency could be kept fastpaced due to Vantage, that was a tremendous relief. Finally for that project we also familiarized ourselves just enough with character creator and Iclone to pull off a somewhat decent protagonist – which then is mostly kept out of focus anyhow :).

Depth of field and lighting are crucial in linear storytelling formats. Vantage allows for having these available during the early layout phase, enabling us to evaluate the flow and precise timing of edits early on, resulting in fewer iterations and more streamlined communication, features that Olaf, as a cinematographer, found lacking in the animation feature films he previously worked on.

DP: Hardware reality check: what exactly were the two workstations (CPU/GPU/VRAM/RAM/storage), and how did that cap scene size, proxies, and iteration speed?

Peter Stulz: There are two parts to this, the GPU and CPU specs: For working with Vantage, I had a 4060TI with 16GB. It was mainly the ground displacement in Vantage that was the key factor for VRAM necessity. Otherwise Vantage is smart when scaling to smaller GPUs. You don’t need massive GPUs to get started with Vantage.

For the final CPU rendering – we have several AMD 9950x in our studio with 64GB Ram, totally unspectacular workstations. In fact rendering moved between machines, whatever was available, the bottleneck was that we had just two render licenses available. Another thing, that I really appreciate about Vray CPU – it stays pretty consistent even if you throw in an older architecture.

DP: How did you keep the master scene nimble?

Peter Stulz: 3ds Max can become a real chore, when scenes get too heavy. I wholeheartedly hate unresponsive scenes – anything that breaks the creative flow has to be solved. Technically, there are several approaches: obviously using Proxies for heavy assets is a must; staying parametric if possible also keeps my scenes small; my modifier stacks can get quite impressive and I avoid baking them.

I xref wherever it makes sense, especially if parts of your scene are used in different settings. If I find the time, I localise heavy textures and reduce them – tedious but worth the effort later. Ideally the Master Scene only contains the camera, the lights and a few key assets. All the heavy load is loaded from external files. These scenes mostly are only a few MB in itself – helping with autobackups.

DP: Camera language before pixels: how did boards/animatic evolve once you could “walk the set” in Vantage?

Peter Stulz: It was important to develop a storyboard outside of 3D first to avoid thinking as a 3d designer. The environment was conceived like a sandbox, so we could freely explore the set with different lenses and angles. The superfast iterations we could do with Vantage really helped to test alternatives. That felt very powerful. Obviously some storyboard shots were then adapted or omitted. Vantage was great to secure we are on the right path.

DP: Lighting in Vantage: What translated 1:1 to finals, and where did parity crack?

Peter Stulz: At first it is scarily impressive how close Vantage can feel to the final look. We did a few final shots directly in Vantage and realised afterwards we could have done more in Vantage to prove the point. The extra turntable animation is done 100% in Vantage, but we really had to go deep in the settings to get rid of some flickering.

You have to understand, Vantage works like this: It downscales automatically to achieve close-to realtime speed and then gradually refines the look. But that logic causes limitations: For example GI depth in tricky setups might cause visible flickering. If you want to get rid of unwanted artefacts like these, you have to go deeper into the settings; and then you get these Vray 2010 vibes again :). Apart from that the denoiser might create some artefacts, textures are getting blurry, VDBs were not possible etc.

DP: Materials & lookdev: which shader features were non-negotiable, and what did you simplify for real-time parity?

Peter Stulz: Since we decided to use Vray CPU for finals, we just accepted that some stuff for Previz looked different – we knew it would be ok in the finals. But to answer the question we used Vantage for a another client project and it became clear again: If you want to produce in Vantage you can not set stuff up in Vray and hope for the best. In that case we had a semitranslucent ocean setting and that looked quite diffferent in Vantage and had to be especially adapted.

DP: The moving house: How was it rigged , and what broke first under real-time playback?

Peter Stulz: The architectural cube is in fact one scene with 2000 frames of animation. No cheap tricks – nothing appears magically out of thin air – it’s all in there. Only the initial cube with the rough surface is a different prop because it had a tricky blending shader which was animated ( animating materials in 3ds Max is a disaster …).

The rig for the unfolding was very basic and was built out of a lot of nested helpers. That was the most simple way to avoid the “locked axis” problem. What is this? Well, rigging a rubics cube is in fact not so straightforward as it seems: after a few twists the individual parts start to move quite unexpectedly – try it yourself, it’s actually pretty hard. The nested helpers solved this, now it was a matter of adjusting the right timing; how fast is the right speed for a massive 12m cube? You want to correspond a certain weight without boring the viewer. At the end we sprinkled some subtle secondary movements on top.

DP: Performance metrics: What were typical FPS for look-dev in Vantage and per-shot render times? Both for Vantage previews and V-Ray finals?

Peter Stulz: We could render out playblasts in Vantage (+/- 200 frames) over a toilet break in 1.5k resolution at 1:2.39. For finals in Vray I attempt to stay around 10 minutes / frame. If you want to use Vantage for final quality in FullHD, you crank up the settings to 1 minute / frame. If there was any noise left, the Resolve temporal denoiser is the last polish.

DP: The famous 95%: where did Vantage land “close enough” to V-Ray and what are the missing 5%?

Peter Stulz: Every “resolution” in Vantage is more coarse. I am not only talking textures, but sampling, atmospherics, global illumination. Obviously the denoiser also tends to smear everything. Everything is just lower definition than in Vray / Corona. That’s why oldschool rendering is still very valid to achieve that crispy level of detail.

DP: Editorial rhythm: how often did you re-cut while “shooting in engine,” and what told you a shot was edit-locked before triggering finals?

Peter Stulz: In our case that answer is quite simple: the presentation date was coming up, so we had a very strict timeframe when shots had to be done. Only thing we updated in the last days, we extended a few shots by 30 frames, because they felt rushed in the beta cut. That little change improved the rythm quite substantially.

DP: Pitfalls & fixes: three things that wasted time before you found the trick and what was the trick?

Peter Stulz: Vantage is built in a way that it actually could be used as a standalone loading in VrayScenes. Since I had my friend Olaf Aue as a cinematographer on board we tried to use it in that way. Theoretically that works, but with a lot of drawbacks and very limited editing and getting the changes from Vantage back into 3dsMax is hard.

We omitted that concept and resorted to live link only with 3ds Max. But actually that standalone option is not so bad – Chaos could really focus there more.

DP: If you rebuilt “Unboxed” today at 100% Vantage, what would the delivery plan look like? QC, shot classes that stay real-time, and the shortlist that still goes offline?

Peter Stulz: I know, that there are more shots that could be realised in Vantage directly. But if you plan this, it is smart to set up the whole project more focused on Vantage directly. Switching to Vray, if needed, is easy, the other way can be frustrating.

DP: What did “Unboxed” change in how you scope, price, and pitch real-time narrative work to clients?

Peter Stulz: We can offer fast animation works more easily which don’t need very high quality or are visually suitable for Vantage (clay shots).

DP: Wishlist to Chaos: What are the top parity/features that would let you ship more shots straight out of Vantage next time?

Peter Stulz: I would like easier quality settings if you intend to use Vantage as final renderer. We had to do a lot of tweaking for specific scenes or even change the 3d scene to avoid artefacts. Additionally Vantage ships with specific assets like a water surface or animated plants. These are great, but in LiveLink they are hard to be used, because there is not way to insert them in your Root Scene.

DP: For Vantage newcomers: What is your “first-day” checklist?

Peter Stulz: Familiarize yourself with the basic UI and do some stress tests to find the limits. Additionally I would look for a study project that comes close to a client environment. There is no point in having all the bells and whistles, if in a real production case you are missing the crucial components.

DP: One more hypothetic: with one extra week or one extra GPU, which single area would you invest in—and why?

Peter Stulz: Funny alternatives. As described above a half-decent GPU is good for previz which was the main usage in “Unbox”. Having a week extra is always great – so I would opt for that!

DP: Where exactly did you keep the “cube layer” for the whole piece: did we start life on the Blender Default Cube, and how much of that origin survived?

Peter Stulz: It sure was great that we could hire the mighty default cube as a support role. It didn’t even mind too much to be shipped into another 3d-suite – what a humble character and it really outshined itself in our short. 3d-artists should show more appreciation to have it per default all free!

DP: The cube’s side text: What does it say, and why?

Peter Stulz: The cube text gives instructions how to mix the perfect Daiquiri as it is served on Kepler 5 but it is quite explicit so I can’t go into depths here. But if you look for easter eggs, we have hidden various personal items in the architecture. Talking about audio my friend Olaf had a lot of fun browsing through his SFX library and pull out quite unusual sounds for the cubes inner mechanics.

The post The Cube Moved: Go for the Chaos (Ad) Vantage first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Blackmagic Design has reduced prices on its URSA Cine camera kits. The URSA Cine 12K LF kit now starts at $9,495, down from $14,995. The URSA Cine 17K 65 kit is reduced to $22,995 from $29,995. Bundles with the EVF follow similar reductions, reflecting discounts in the 22–36 percent range.

As with previous Blackmagic launches, regional price variation remains significant, driven by tariffs, taxes, and import costs. Outside the U.S., customers should expect noticeably higher pricing or lower pricing that reflects these additional charges. No change there.

The timing of the price cuts is hard to ignore: IBC 2025 in Amsterdam begins in less than two weeks. While totally and defintily unconfirmed, this could indicate that Blackmagic is clearing inventory ahead of a new release, or gently steering attention toward something fresh in their Cine line. The price reductions on existing URSA Cine kits may suggest that Blackmagic is preparing to shift focus to new variants or accessories, potentially a wider rollout of cinema bodies, storage upgrades, or immersive systems. As always, production professionals should test any new or discounted gear in real-world scenarios before committing to deployment.

The post URSA Cine Price Cut first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Adobe’s Substance 3D Designer 15 (released July 2025) brings long-demanded upgrades for production artists: a unified viewport renderer, native post-processing FX, and direct scene-based context editing. This is not just a facelift—it’s a workflow upgrade for material creators who want to see results that won’t embarrass them in dailies.

Unified Renderer: Real-Time Raster and Path Tracing, No Compromises

The all-new renderer merges real-time rasterization and GPU path tracing into a single engine. Shadows are physically plausible, ground planes are supported, and switching between preview and final-quality output no longer involves arcane OpenGL settings or the creaky Iray plugin. MaterialX support is also built in, which may be useful for studios prepping for cross-pipeline transfers.

This renderer now replaces both the old OpenGL and Iray viewport modes—so what you see in Designer finally matches what you get in production renderers. This isn’t speculative; CG Channel{:target=”_blank”} and 80.lv{:target=”_blank”} both confirm it.

Native Post FX: Bloom, DoF, and Modern Tone Mapping

Post-processing is now handled directly in the 3D viewport. Users can enable bloom for those inevitable emissive materials, add depth-of-field (in raster mode), and choose modern tone-mapping profiles like ACES and AgX. No more exporting a bunch of screenshots for “Photoshop it later” passes—production lookdev can happen right where you texture. These FX are in-app and don’t require third-party plugins.

Scene Context Editing: Import USD/GLTF, Edit Materials in Place

Material authors can now import whole 3D scenes—including USD, USDA, USDC, USDZ, GLTF, PLY, and STL—and replace or tweak materials directly on selected meshes. That means actual context for lookdev: artists can edit, preview, and export scene-based material graphs without round-tripping to another DCC or losing mesh data. This is not a half-step: USD edits are non-destructive and maintain scene fidelity.

Workflow Upgrades: Tooltips, Bakers, CLI

Designer 15 includes context-sensitive, illustrated tooltips for atomic nodes—finally, some clarity for anyone lost in spaghetti graphs. GPU-accelerated bakers are improved, non-square UVs are supported, and the baking CLI is now more sensibly named substance3d_baker.exe.

One Caution: Test Before Production

As always: New features should be thoroughly tested in your actual production pipeline. Rendering, material export, and FX might behave differently outside the pristine confines of Designer’s viewport.

These tweaks (and more) are detailed in Adobe’s own release notes.

The post Substance 3D Designer 15 arrives first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

On March 16, from 11:00 to 15:00, Design for Film – Art and Costume Department meets VFX will take place at Kino 2, HFF München. The event brings together professionals and students to discuss the practical and creative intersections between digital and analog film production. Moderated by Waleska Leifeld, the panel includes Prof. Jürgen Schopper (HFF, VFX) and industry experts from Art and Costume Departments in film and series production.

Symposium at HFF München: Where Art Meets VFX

The symposium examines fundamental questions about interdisciplinary collaboration: Who communicates with whom—producers with VFX studios, location scouts with VFX supervisors? Who oversees the overall design? What role does a VFX supervisor’s independence play? At what stage is the decision made between digital and practical effects, and how does budget planning factor into this? The discussion also covers the integration of digital costume and art departments, the crucial on-set interactions between VFX supervisors and costume teams, and the evolving educational landscape for these fields.

Insights from VFX studies at HFF München, Production Design at ZHdK (Zürcher Hochschule der Künste), and Costume Design programs will provide context on how education aligns with industry demands. The symposium concludes with a networking session at Minna Thiel from 15:00 to 16:30.

And if you want to join, write a mail to info@v-sk.de

The post 16.03.25: DESIGN FOR FILM: Bridging Art, Costume & VFX @ HFF Munich first appeared on DIGITAL PRODUCTION and was written by Bela Beier.