For those who don’t know the tool: Cinema 4D is Maxon 3D for modeling, animation, sims, and lookdev, with tight Redshift Renderer integration and common handoffs like USD. Think MoGraph, then render, then wonder why lunch is over.

The update in one sentence

Cinema 4D 2026.2.0 comes with new modelling (especially for cloth) and lighting features, plus broad fixes across animation, modelling, MoGraph, simulation, viewport, exchange, and rendering. As well as a load of smaller cool features and updates.

Fabric Brush gets hands-on with soft stuff

The big new feature is Fabric Brush, a modeling tool that uses the app’s simulation system to shape soft materials directly in the viewport. The intent is tactile: push and pull forms while the sim helps create folds, draping, and deformations, without setting up rigs for the job.

In practice, this is a new option for artists who want quick cloth-like sculpting while staying in a familiar modelling workflow. It aims for standard tool responsiveness while adding simulation-driven behaviour for the soft look.

Redshift goes nocturnal

Cinema 4D 2026.2 introduces a night-sky option in the Redshift Sun and Sky system for dusk and night lighting setups. If your scene needs a sky that reads after sunset, this is now a first-class mode inside that system, rather than a workaround of lights and environment tricks.

Cinema 4D 2026.2 ships with Redshift 2026.5.0. Older Redshift versions from 2026.0.0 and higher remain compatible, but they will not include the newer Redshift features, plus enhancements to integration and performance.

Redshift 2026.5.0 also raises a practical requirement: the minimum required version for the 2026 plugin becomes Cinema 4D 2026.2. On the Cinema 4D side, a related integration note calls out Redshift Live replacing Redshift RT.

Deformers, clones, and command lines get small superpowers

A few smaller changes target everyday rigging and motion graphics chores. Bend Deformer improvements add new symmetry origin options, so mirrored bends can come from a single deformer. For quick character tweaks, product flex shots, or anything that wants a symmetric bend without duplicate setups, this is a quality-of-life gain.

A new Xpresso Command Line Argument node allows passing string arguments into Xpresso setups during command line rendering. That is a direct nod to pipeline automation, where renders often start from a farm call, a script, or a build system rather than a human clicking the Viewer.

MoGraph users get a new loop option for the Target Effector, allowing the first and last clones to target each other in closed arrangements. That fits neatly into circular patterns, rings, and repeating layouts where “ends” should not exist.

In the Material Manager, an Active Object Material Filter shows only materials applied to the currently selected objects.

Animation, curves, and viewport comfort

Cinema 4D 2026.2 adds an Align Tangents command to quickly align tangents on F-Curves. If you spend time cleaning curves after mocap, procedural animation, or hand-keyed polish, this is the sort of tiny tool that can save a lot of clicks.

Exchange formats and rendering housekeeping

Cinema 4D 2026.2 includes an exchange crash fix when exporting to Alembic. It also fixes an issue where reimporting a previously exported skeletal animation USD scene could result in an incorrect preview area and scene length even though the export itself was correct.

Rendering and output fixes include preventing multipass images from being saved in viewport render, and a Physical renderer change where Remesh no longer recalculates during rendering. The Picture Viewer gets reduced color banding, and a Redshift-related workflow fix allows creating a render setting from a render to work with Redshift renders.

Redshift 2026.5.0 adds and fixes several Cinema 4D specific items, including a new default native Projection Mode intended to resolve material tag UV tiling incompatibilities with UV Contexts, a fix for UDIMs not rendering correctly when using Team Render, and a fix for random black images when rendering heavy meshes with deformation blur enabled. It also notes a faster connection and smoother navigation for the RS Live Viewport IPR, limited to Cinema 4D 2026.2 and higher.

ARM downloads and driver reality checks

Cinema 4D 2026.2 includes a warning for downloads on ARM: update the GPU driver to the latest version – they even have a link for Windows on Snapdragon users to Qualcomm for the latest drivers.

https://support.maxon.net/hc/en-us/articles/8658038724124-Cinema-4D-2026-2-0-April-15-2026

https://support.maxon.net/hc/en-us/articles/8814051767964-Redshift-2026-5-0-2026-04-April-15-2026

The post Maxon ships Cinema 4D 2026.2 update first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Adobe ships Color mode as a dedicated color workspace inside Premiere Pro beta. It uses a streamlined layout that maximizes the Color monitor, reduces on-screen clutter, and adds dedicated color panels that only appear in Color mode.

Colour mode centres the experience around three pieces: the Colour monitor for evaluation, a Clip Grid for picking shots quickly, and a Colour Controls panel for doing the actual work. The intent reads as editorial-first grading: jump between shots fast, make decisions with the image front and centre, and keep the toolset close to what you already do in an NLE.

Color mode switches the monitor between a sequence view for checking the timeline and a clip view for focusing on a single shot. It also adds a Solo mode that temporarily disables overlays and composited elements so you can judge adjustments without extra layers muddying the view.

The new workspace design lands alongside a clear compatibility message. The Lumetri effect remains available in the beta Effects panel and stays supported. Existing projects and Lumetri grades keep their expected look. The Lumetri panel itself no longer appears in the beta UI, and Lumetri changes move to the Effects Controls panel.

Clip Grid turns your sequence into a grading playlist

The Clip Grid presents clips from the active sequence as thumbnails for quick selection. It supports filtering, sorting, and grouping to keep large timelines manageable while you grade. It also includes view controls that change between a row style layout and a multi-row grid so you can either stay focused on a short run of shots or see more of the cut at once.

Color Controls and Operations aim at repeatable grades

The Color Controls panel acts as the hub for adjustments to the currently selected clip in the Clip Grid. It organises colour operations applied to that clip, and it frames each operation as equivalent to a layer or node of colour tool modifications. That puts grade-building blocks front and centre, with a structure that can scale from quick balancing to more involved looks.

Color mode also introduces an Operations system for grade management, positioned as part of the new experience alongside the interface and control set. Operations appear as the mechanism for managing grades across clips, groups, and sequences.

Color mode also leans heavily on feedback. Many controls activate a heads-up display that combines scopes, numeric feedback, and real-time visual guidance. The goal is to help you understand what a control does while you drag it, instead of making you guess and undo your way back to safety.

That HUD concept matters because many controls are bi-directional. One axis adjusts one parameter and the other axis adjusts a second parameter. There is also a modifier for precise single-axis moves. Each control can surface its own on-screen feedback as you work.

If you already live in scopes, the pitch is simple: fewer trips to separate panels, more continuous feedback while you push the image. If you are newer to grading, the design tries to teach you by making the response visible and measurable while you move.

New controls: from contrast to zones to hue isolation

Color mode adds a set of new control groups and built-in styles and modules. On the adjustment side, the control set includes contrast with contrast and pivot, exposure with exposure and black level, temperature with temperature and tint, balance for shifting color balance, saturation, and a Detail section that covers texture and sharpness. Texture offers global, single, or multi-band detail. Sharpness includes radius and threshold controls, plus blur.

There is a Zones section that grades the whole image globally or isolates grades into shadow zones and highlight zones. Shadow zones and highlight zones support multiple preset zones and custom zones, letting you target darker or brighter parts of the image with separate adjustments.

There is also a Color Shift section with Sat Shift, Hue Shift, and Lum Shift. These controls focus on specific hues, letting you change saturation, hue direction, and brightness for a selected hue range. Automatic Hue Isolation surfaces prominent hues from the image for faster selection, and it also supports an eyedropper plus a full RGB spectrum picker for manual targeting.

Styles and Modules show up as built-in starting points. The system includes modules such as Film Color, Contrast Kit, and Flare, plus style presets such as Cinematic Contrast, Varied Temp, Varied Lighting, Varied Sat, and Monochrome. There is also a Make Your Own path that combines modules to build custom styles.

Color management: SDR and HDR workflows in the same mode

Color mode links directly into the application color management system. It supports workflows that include Direct Rec. 709 SDR and Wide Gamut Tone Mapped. It also supports SDR and HDR output formats including Rec. 709 and Rec. 2100.

Wide Gamut Tone Mapped has more flexibility when adjusting images. Tone mapping aims to create smoother highlight and shadow roll-off, with the benefit of easier exposure and color adjustments without clipping.

There are also updated tone-mapping and gamut-compression settings for handling SDR media and graphics. An advanced option called Apply Inverse Tone Mapping and Gamut Compression targets accuracy when working across mixed media formats. But never change the working color space mid-workflow, since switching after adjustments can alter the appearance of the grade and force extra refinement.

This is the part that can make or break the experience in real projects. Colour management should behave consistently across cameras, codecs, and delivery targets, or editors will revert to what they trust.

Some workflows will still need careful validation on your own media, especially mixed camera jobs and sequences that move between SDR and HDR deliverables. Test new tools and innovations before use in production, and verify the pipeline from ingest to export with footage that matches your real work.

Plans, beta access, and what it costs

Color mode is included in the Premiere beta and it comes with any Creative Cloud plan that includes Premiere, with no additional cost for the feature itself. The beta installs through the Creative Cloud desktop app. New users can start with a 7-day free trial of Premiere. The official product page also states that the Premiere single app plan starts at US$22.99 per month for an annual plan billed monthly. Pricing changes by plan and region…

https://www.adobe.com/de/products/premiere/color-mode.html

The post Adobe brings Color mode to Premiere beta 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.

For those who don’t know the tool: Spark Story sits in early previs and story workshops, pairing a browser build step with a mobile virtual production app, plus workflows that touch Blender and Unreal Engine.

NAB gets the hands-on bit

Spark Story is set for a public preview at NAB Show 2026, with an interactive booth demo that lets attendees create shots live and move between a browser session and a mobile virtual production app. The preview is scheduled on the show floor from April 19 through April 22 in Las Vegas (Booth N3148). Lightcraft calls Spark Story the first piece of a broader Spark platform that is still in development, with the NAB preview focused on rapid virtual-shot creation, script linkage, and a browser-to-mobile workflow. A beta notification signup page for the broader Spark platform is already live, indicating that a formal beta program is planned and more or less around the corner.

The pitch is simple: start workshopping a film on day one with the team, using rapid virtual shot building instead of waiting for later stages to see whether scenes and beats land. The preview demo uses scanned environments (Splats) and prompted environments as part of setting a scene, plus the ability to block and capture camera shots from a phone.

Browser to phone, with script in the loop

The preview description frames Spark Story as a real-time workflow that links a browser tool with a mobile app so teams can collaborate while building scenes and placing cameras. Script linkage sits near the center of that workflow, with an emphasis on connecting shots back to a screenplay, and on turning camera placement in a 3D scene into entries that feed a shot list tied to settings and framing.

A separate feature preview calls out collaborative screenplay editing and breakdown, aimed at real-time collaboration and development from partial ideas into a full screenplay. That matters less for the final file format and more for how teams keep intent, coverage, and revisions connected while the visuals evolve.

If you have lived through the classic version of previs, where shots float around in a folder tree while the script keeps changing in a different tool, this is clearly trying to make that disconnect go away. The claim is that a team can move much faster through early planning, pitching, and shoot preparation.

Environments: scans, prompts, and Gaussians

The preview highlights three main buckets of scene content: scanned environments, prompted environments, and more traditional 3D content. It also calls out support for Gaussian Splats and imported USD assets in the same workspace.

For Gaussian Splats, the industry standard is 3D Gaussian Splatting, a real-time radiance field rendering approach with an official, publicly available reference implementation. For USD, the relevant target is OpenUSD, positioned as a platform for building and exchanging 3D scenes at scale.

The interesting bit here is not that any one of those elements exists, but that the preview bundles them into one collaborative shot-building flow. If teh tool can keep scale, orientation, and camera intent consistent while teams mix splats with USD assets, that would remove a lot of glue work that currently happens in side scripts and one-off conversion steps.

Camera intent and virtual production capture

The preview copy states that Spark Story builds scenes around realistic digital environments, physically correct motion, and camera and lens models intended to keep early decisions consistent through shoot days. That is a marketing claim, but it is also a promise: camera behaviour and motion should (!!!!) translate from early planning into on-set execution without a full redo.

On the capture side, the preview positions a mobile app as the place where shots get captured from anywhere, with an integrated iOS experience described as push-button simple. For the platform piece, that points straight at iOS, no word of Anroid yet.

The practical production question is what data comes out the other end and how it plays with the rest of a pipeline. The preview text focuses on workflow and collaboration rather than interchange details beyond imported USD assets. So, at press time, there is no confirmed list of export formats, tracking data handoff details, or round-trip guarantees for specific DCCs in the NAB preview description. But there are importers for Fab.comMegascans, Unreal, Autoshot, as well as Blender, Nuke and After Effects. No word on Lightwave.

What is confirmed on the ecosystem side

Outside the NAB preview messaging, the public documentation site already carries Spark Story sections alongside broader tooling docs, including workflow pages that reference Blender and Unreal-related processes and USD troubleshooting topics. That is not a full product spec, but it does confirm that Spark Story documentation exists publicly and that USD sits inside the expected workflow surface area.

That matters because it suggests this is not a closed demo-only concept. There is already a documentation structure, including tutorials and debugging notes, which is usually where pipelines go first when they try to validate a tool against real production constraints.

What to test before you bet a schedule on it

Rapid collaborative previs sounds great right up until a production needs repeatability, versioning, and predictable handoffs. If you plan to evaluate Spark Story, put it through the boring tests early: multiple artists editing the same sequence, script changes mid-session (Thrice), asset relinking, and exporting or round-tripping anything your downstream tools require.

New tools and innovations should always be tested before use in production, preferably on something disposable, like a two-day internal short that still hits the same technical constraints as a real show.

The post Spark Story at NAB first appeared on DIGITAL PRODUCTION and was written by Jürgen Firsching.

For those who don’t know the tool: Marvelous Designer turns 2D patterns into simulated garments, then exports assets and animation through formats like FBX, Alembic, glTF, and VRM.

Drawing first, pattern later

The loudest shift in 2026.0 is the push toward direct creation on the avatar, with 3D Pencil aimed at skipping some of the usual back and forth between sketching intent and building patterns.

3D Pencil works in the 3D window on an avatar. Activating it from the 3D toolbar opens a Sketch dialog and switches the viewpoint to the front view. The view then stays locked to either the front or back for sketching, with zoom allowed, to keep conversion reliable when the lines become editable 3D pen data.

Sketching is a click and drag action on the avatar. Cleanup happens inside the same tool using an eraser mode. The eraser has a size setting to control how much gets removed in one pass, and the viewpoint can be switched between front and back.

Converting moves the sketch into a 3D pen result and automatically switches to the edit tool for that pen. There is also a sewing behaviour note that matters for garment builders: when 3D pens get created by sketching both the front and the back, flattening both sides automatically sews the front and back together. This is not a promise that all garments suddenly become one-click wonders. It is a workflow: sketch in a fixed view, preview conversion, convert to editable pen lines, then continue editing as needed.

Laces that behave like patterns

The other flagship addition is the Lacing Tool, which formalises a common production detail into a dedicated workflow.

The tool creates lacing by clicking a sequence of designated holes. You pick the starting hole, then continue clicking holes in the desired order until the last or exit hole, and finish with a double-click on the final hole or by pressing Enter. When the path is finalized, an editable lace pattern generates in the 2D window for modification.

Undo controls are built into creation. Backspace undoes the last step, while Esc or Ctrl+Z undoes the entire creation step. That sounds minor, but in practice it signals that the tool expects iterative route tweaking, not a single perfect pass. Just a warning. If you are one of the people who is even nominally an adult, still struggles sometimes with shoelaces. Not judging, brother!

After the path finalises, direction and curvature can be adjusted. A reverse icon appears attached to the cursor immediately after finalising. Clicking a specific hole reverses direction at that point, changing whether the cord enters from the top or bottom of the eyelet. Routing updates in real time in the 3D window.

Curvature adjustment uses a slider to change the cord arc. Increasing curvature is intended to stabilise the simulation by preventing the cord from colliding with or clipping into nearby patterns. The resulting lace is still a standard pattern piece, so thickness, material, and physical properties remain editable in the property editor like any other garment component.

The tool works by eliminating manual intervention by automatically routing the cord and generating an editable pattern for further customisation.

Toon materials, with familiar knobs

2026.0 also adds a toon material workflow under a feature called Express Cartoon. It applies to fabrics, 3D objects, and avatar materials. The workflow is simple: select a fabric style or an avatar, then set Material type to Toon in the property editor, then adjust the exposed properties. The options list is long and reads like a practical toon shading panel rather than a single style preset. If your goal is the next KPop Deamon Hunter, well, go for it.

Base colour can be set as a colour or a map. Opacity has both a value and a map. Shadows get a shade colour and an optional shade colour map, plus hardness and a shift control that adjusts where shadows begin. Emission has both colour and a map. There is also a MatCap section with color and map, described as a fake reflection effect that blends with a MatCap image.

Rim light includes colour, fresnel power to control thickness and sharpness, and lift to adjust position offset. Outlines have a mode, an outline map for masking, a line colour, and a width value in millimetres.

It is worth remembering what this does and does not say. The feature allows a cartoon-style look using those material controls. It does not define a renderer, a lighting model, or a compliance target for any specific engine. That keeps expectations grounded: it is a shading feature inside the tool, with parameters designed to shape a toon result.

Export workflow: fewer surprises, more switches

The 2026.0 feature list calls out new and expanded format support, including glTF and VRM. In production terms, that points toward web compatibility and virtual character workflows, and it sits alongside existing interchange routes that many pipelines already rely on.

On the export control side, play region selection appears as a specific addition for FBX and glTF export in the feature list, enabling selective export of specific animation ranges. For joint animation export, baking keyframes is there to generate keys for empty frames to prevent unintended transformations.

Those items have matching controls visible in the updated FBX import and export documentation. FBX import supports Open or Add load types, scale, axis conversion, and several toggles such as joint animation and cache animation. It also lists trim import behaviour that cannot collide with clothing when simulation is on, plus a collide option toggle for trim in the property editor, and a glue icon workflow to attach trim to clothing.

FBX export includes single- and multiple-object exports, weld and un-weld options, and thin and thick options for exporting with or without rendering thickness. It includes combined UV coordinates and texture export controls, including texture size and seam fill. It also includes a 2026.0 specific note: Weld Turned Sewing Lines allows vertex merging for export even when the sewing line type is set to turned.

Licensing and cost facts that affect teams

A personal monthly subscription is listed at $39 per month and is cancelable anytime, with automatic billing. A one-year prepaid license is listed at $280 as a one-time payment, not automatically billed.

A student subscription is listed at $99 as a one-time payment, not automatically billed, with a note that it can be purchased up to two times over four years after student status verification.

Enterprise options list an enterprise network online monthly plan at $199 per seat, an enterprise network online annual plan at $2,000 per seat, and an enterprise Linux annual plan at $2,300 per seat. An indie studio option is listed as “Contact sales”. There is also an enterprise notice that, from December 2, 2025, the enterprise standalone license was discontinued and shifted to network online monthly and annual subscriptions.

The boring but important note

2026.0 stacks a lot of workflow surface area into one release: new creation tools, new material type controls, and a pile of import and export switches that can change how data lands in downstream tools. The right way to treat that is like any pipeline-facing update. Test the new tools on your ugliest garments (For bonus points: Remake the garment you are wearing right now as a training exercise. Hoodie, PJs, and Fluffy slippers and all), validate the round-trip exports, and confirm that your intended use stays stable before you put it on a deadline.

The post Marvelous Designer 2026.0 adds 3D Pencil and lacing first appeared on DIGITAL PRODUCTION and was written by Bela Beier.