The pitch: graphs, not layers

ArcBrush builds images in a node graph. You wire inputs into operations and wire the result into exports. The app focuses on non-destructive editing, with parameters staying live so you can adjust a pipeline long after the first export. The core editor is free to download and use, and it does not require an account for non-AI work (Oh, blessed 2026, when this is a mention-worthy feature of a software….) . It runs as a native desktop app written in C++ and works on Windows and macOS. Linux coming soon.

If you live in node land already, the concept will feel familiar. The difference here is that the output target is mostly 2D deliverables: icons, sprites, UI variants, texture maps, and piles of formats that someone will ask you to regenerate five minutes before lock.

Node count, node types, and the day job stuff

The app has 75 composable node types and type-safe connections that prevent invalid wiring. It also brings five pin types, separating images, masks, palettes, and variants so the graph can validate what you connect.

A lot of the feature list reads like it came from someone who has rebuilt the same export stack too many times. There is auto save with crash recovery. There is a minimap, node search, undo and redo, node groups, per node notes, and sticky notes.

The preview tooling targets production rather than marketing . You can lock the preview to any node output, zoom deep with a pixel grid, inspect RGBA values, isolate channels, and view a live histogram overlay. For monitoring consistency, the app reads your monitor ICC profile and applies correction so the display matches exports via display color management using the monitor profile from the International Color Consortium. Test that on your own display chain, especially if you work across multiple calibrated panels, because colour surprises are lovely… .

On the output side, there are single-image exports and batch exports. Export Batch can produce named files per palette variant, or pack variants into a single sprite sheet PNG while also writing a TexturePacker compatible JSON manifest. Export nodes also support relative paths, and the app can create directories automatically when exporting.

Pixel art and texture helpers, without pretending to be a full DCC

The feature goes for game art and texture workflows, but it stays in 2D territory. There are pixel art oriented nodes like Pixelate, Outline, Dither, Quantize, Palette Remap, and sprite sheet export. Dither lists Floyd Steinberg, ordered, and blue noise options.

For texture work, the app includes Seamless Blend to make images tileable, Noise and Pattern nodes for procedural bases, Tile Preview to check repetition, and a Normal Map node that generates lighting maps from grayscale. This is not a replacement for a full material authoring suite, but it covers the everyday prep-and-iteration loop where you need quick variants, quick tiling fixes, and quick exports without babysitting layers.

If you spend time in texture painting or material prep, the most interesting claim is the pipeline idea: build the graph once, then regenerate every variant and export target when the source changes. That includes a Watch File toggle on input nodes that reloads when the source file changes on disk. The page even spells out a simple case: edit in Photoshop and see the result live in ArcBrush. That makes it less of a walled garden and more of a graph-driven post station for assets.

OpenCV processes images on CPU and GPU, and OpenGL renders previews. For SVG import, it rasterizes via ThorVG. None of that guarantees performance on your particular workstation, but it does clarify that the app aims for native processing rather than another browser wrapper.

Optional AI nodes: credits, cloud, and knobs you can count

AI features are optional. The app has AI cloud based nodes that only reach out when you use them, while the rest of the graph runs locally. There are nodes for text to image, image edit with text instructions, background removal, and 4x upscale powered by AuraSR. It also has differnet models, including FLUX variants and Nano Banana 2 for text to image and editing.

Pricing for AI is a one time credit packs with no subscription and credits that never expire. The packs listed are Starter at $10 for 350 credits, Plus at $20 for 800 credits, and Pro at $40 for 1800 credits. The site also states 10 free credits on signup. Credit costs vary per model and task, and at standard resolution up to 1024 by 1024.

That setup makes it easy to budget AI usage as a production expense, but it also adds a network dependency for those nodes. Treat it like any other external service: check availability, latency, and whether cloud processing fits your client and studio rules. Or if the bubble already burst, and you need to rewire things to the little Docker Server you have in your Cupboard that replaces all the Hype…. If you only want the node graph editor, you can ignore AI completely and still use the full non AI toolset.

Where it fits if you already have node tools

Node based workflows already dominate compositing and lookdev, so the real question is whether a dedicated 2D node graph editor reduces friction compared to existing tools. ArcBrush positions itself as a build once and export everything machine: variants, palettes, batch exports, sprite sheets, and texture prep steps chained together so you can re run them on demand.

First, when you need to ship a lot of consistent variants, like tiered item icons, UI colorways, or platform specific asset sets. Second, when you need to keep a process editable after the first deliverable, because late changes rarely arrive in a neat package.

Reality check before you bet a deliverable on it

ArcBrush looks designed for artists who want node graph control for 2D assets and textures without living inside a heavyweight suite. The free core editor and the explicit credit pricing for AI lower the barrier to testing (Which we’ll do after FMX) , and the node count and export features cover a lot of common production chores.

Still, new tools and innovations should be tested before use . Put it on a few real assets, run it through your team review loop, and see whether teh graph model actually reduces mistakes compared to your current wokrflow.

ArcBrush is available as a free download from the product site, with documentation hosted on the docs portal and community links including Discord.

https://arcbrush.com/

The post ArcBrush turns image editing into a node graph first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

InstaMAT Studio is out now – a layer-based painting and node-based authoring tool in the same general category as Substance 3D tools like Substance 3D Painter, Substance 3D Designer, and Substance 3D Sampler, with integrations into common DCCs and engines including 3ds Max, Blender, Maya, Unity, and Unreal Engine.

What changes in 2026 is the set of levers available for high-precision, iteration-friendly detailing. Curves Brushes move detail painting toward an editable, control-point workflow. Lazy Stroke helps freehand lines behave. Radial symmetry adds a new patterning tool. Masking and mesh filters expand geometry-aware selection and effects. The new toolbar and hotkeys aim to keep artists in flow instead of chasing settings panels.

And yes, your first experiment should probably be those curve-driven panel lines that always look great right up until the model changes. This time, the system is explicitly designed so the detail survives that upstream change.

Curves Brushes: strokes that stay alive

Curves Brushes let you create editable curve paths on the mesh, using control points rather than a one-and-done freehand stroke. Those curves remain editable after creation, including moving and refining control points, and transforming an entire curve as a unit by translating, rotating, or scaling the path.

A single curves layer can hold multiple curves, and their painting sequence can be reordered. Curves can also be set to erase instead of paint, and they can be closed to form continuous shapes from end point to end point.

Control points support different point types, including linear, symmetrical, smooth, and cusp, with a Joint Smooth setting to control how sharp or fluid the transitions are between segments. Each control point also supports per-point settings for radius, falloff, flow, and rotation, enabling effects such as tapering and gradual fading along the curve.

Curves can orient brush strokes along the path, so details follow the curve’s flow rather than fighting it. Curves also support dynamics for randomised size, flow, rotation, and position to add variation without manually wiggling your wrist into submission. The Curves workflow uses a GPU-accelerated 3D painting engine and does not rely on mesh UVs. The stated result is that curves remain intact even when topology or UV layout changes, which is framed as especially useful for repeating high-precision details such as panel lines, seams, stitches, and decorative elements.

Lazy stroke smoothing, now built in

Alongside Curves, InstaMAT 2026 adds Lazy Stroke, a brush-smoothing feature designed to dampen shaky-hand input and cursor jitter. When enabled, the brush follows the cursor with a delay set by a configurable radius, producing smoother lines for precision freehand painting. The feature is positioned for tasks such as smooth linework, organic patterns, and fine-detail passes where jitter becomes visible in the final maps. If you have ever zoomed in to paint one confident line and instead produced a seismograph reading, Lazy Stroke is aimed squarely at that moment. Try it, then decide if it belongs in production.

Symmetry upgrades: radial joins planar

Radial symmetry painting is new in InstaMAT 2026, enabling repeating brush instances around a central axis. The symmetry axis can be set to X, Y, or Z, the number of repeated instances is configurable, and the angle span can cover full 360 degree patterns or partial arcs. The plane origin is also customizable, allowing the symmetry center to be placed where it is needed on the asset.

Planar symmetry painting is also described as significantly improved. The symmetry plane can be offset to a custom position on any of the three world axes, plane visibility can be customised, and there is an option to mirror the brush on the opposite side of the plane. Symmetry accuracy is described as improved even when painting on meshes that are not exactly symmetrical, targeting the real-world scenario where characters and props have small asymmetries and deformations.

Masking: normals, submesh size, and raytraced AO

InstaMAT 2026 extends its mask set with new workflows aimed at isolating geometry features without hand-selecting everything. The new Mesh Normal Mask can isolate parts of a mesh based on polygon normals and an angle tolerance. The workflow is click-based: click a region, and the mask selects surfaces with similar normal directions. Multiple chosen areas can be defined within a single mask, and tolerance can be adjusted per point. The mask is described as UV independent and stable across topology or UV changes.

The Mesh Submesh Mask can mask submeshes by size and distance, targeting scenes with many similarly sized objects where manual isolation is tedious. There is also a Mesh Ambient Occlusion Mask described as using raytracing to generate occlusion-based selections for isolating crevices, corners, and recessed areas.

Mesh filters and nodes: mirror, bevel normals, drips, and smoothing

A batch of mesh-oriented effects and nodes are listed as part of the 2026 update. Mesh Laplacian smoothing arrives as an option in the Mesh Smooth node, described as producing a more unified surface while better preserving mesh volume compared to traditional smoothing methods that can shrink geometry. The described use cases include cleaning scan data, removing photogrammetry noise, and refining sculpted details while preserving silhouette.

Mesh Mirror can mirror decals, masks, and entire layers, and it can be applied to a layer group to mirror complex effect and mask combinations.

Mesh Bake Bevel Normals is a node for beveling low poly asset edges using a GPU-accelerated bevel normals baker, with procedural masking for selecting which objects or edges to bevel. The behavior is described as procedural, so bevel placement remains correct if the input mesh topology or UVs change.

Mesh Directional Blur is presented as a way to create leak and drip effects by blurring in a specific direction in 3D space, keeping directionality consistent across the mesh surface regardless of UV layout or texture resolution. It includes distortion and falloff controls.

Additional mesh features listed include Mesh Solidify for solidification to prevent rendering artifacts, Mesh Sharpen for definition and detail clarity, and a Mesh Stylized Filter for non-photorealistic texturing options.

InstaMAT UI and workflow: less hunting, more painting

InstaMAT 2026 introduces a dedicated painting toolbar intended to centralise common controls. The toolbar provides quick access to brush and curve settings, including radius, flow, rotation, Lazy Stroke radius, symmetry, and curve-specific controls. It is described as dynamic, updating based on the active layer type so only relevant options are displayed.

There is also a dedicated brush rotation hotkey, described as Cmd or Ctrl+Shift with a left-mouse drag, to rotate the brush, aiming to reduce interruptions during stroke work.

Viewport and gizmo changes include planar translation gizmos for moving a mesh, effect, or mask along two axes at once, plus custom viewport wireframe settings for width and color, and a viewport shortcut overlay that displays hotkeys while painting, using curves, and using the paint projector.

Mesh import settings add options to configure mesh up axis and coordinate system handedness for asset texturing projects.

Integrations: Blender, Unreal, 3ds Max, Maya

The release notes list updates for several integration plugins tied to the latest https://docs.instamat.io/en/Products/InstaMAT_Studio release.

InstaMAT_for_UnrealEngine lists support for Unreal Engine 5.7.3, plus fixes for crashes when creating invalid graph instances, and fixes for broken materials and mesh orientations for Scene outputs. Library previews are added for Mesh-type Graphs and Graph Instances.

Blender integration notes include support for the latest Studio release, improved performance when setting mesh as a graph input, improved performance when resetting graph instance inputs, and fixes for plugin stalls when creating faulty graph instances. Library grid UX is adjusted with fixed cell width, and search results quality is described as improved.

3ds Max integration notes list support for the latest Studio release and a fix for the plugin getting stuck when creating faulty graph instances, plus window icons changed to match the main menu.

Maya integration notes list support for the latest Studio release, improved mesh-as-input performance, fixes for plugin stalls on faulty graph instances, and a fix for incorrect exported textures when using the export dialog window.

InstaMAT Licensing and pricing: what the numbers say

InstaMAT licensing is split across tiers with revenue or funding caps stated for some options. The Pioneer license is free and fully featured with commercial-use rights, with availability limited to individuals or businesses with annual revenue or total funding less than 100,000 US dollars, and it requires attribution.

The Indie license is available for individuals or businesses under 250,000 US dollars in annual revenue or total funding, with an option at 8 US dollars per month billed annually, and a perpetual Indie price shown at 489 US dollars. For Pro, the pricing page lists a Pro subscription shown at 36 US dollars per month billed annually, and a perpetual Pro license shown at 989 US dollars.

If you are evaluating the tool for a pipeline, test it against real assets, real render targets, and real deadlines before it touches a production branch. New tooling should earn trust with results, not promises.

Finally, keep an eye on how the new mesh filters slot into your existing material graph habits. Directional blur for drips in 3D space, procedural bevel normals, and AO-based masking can remove steps that otherwise happen in separate tools. If it holds up, it reduces context switching. If it does not, at least you learned it on a duplicate branch instead of the hero asset.

Also, do not skip the boring step: validate exports, naming conventions, and texture packing against your engine ingest rules before you fall in love with a shiny new brush. The most dangerous bug is the one that looks like a style choice until delivery day.

InstaMAT Test: Painting, Procedurals and Pasta

The post Abstract ships InstaMAT 2026 Curves Brushes first appeared on DIGITAL PRODUCTION and was written by Manuel Kotulla.

For those who don’t know the tool: OpenPBR sits in the material and shading layer, feeding lookdev and final-frame rendering. It can travel between CPU and shader code thanks to a shared macro layer, and it plugs neatly into a broader Substance 3D style workflow.

A reference library you can actually drop in

A public reference implementation of the full OpenPBR 1.0 BSDF is now available, released as a small, self-contained library built to mirror a production implementation used in an internal engine. The package is designed to be simple to integrate. It is delivered as a single header include named openpbr.h, aimed at teams who want to evaluate, sample, and ship consistent shading behaviour without hauling in a larger framework. The licensing choice matters for production teams and tool builders. The library is licensed under the Apache License 2.0, which is commonly used for permissive reuse and redistribution.

The API is small and very on purpose

The exposed interface is intentionally compact. The API surface is described as prepare, sample, eval, and pdf. That kind of shape is familiar to anyone who has wired a material model into a renderer, a path tracer, or a real-time shading stack. You prepare state, you sample directions, you evaluate response, and you compute the probability density for whatever sampling strategy you picked.

The key point here is not that these names exist, but that the implementation is a complete production implementation of the full OpenPBR 1.0 BSDF, then refactored into a tighter library form. That implies the library is meant to be used as a working baseline rather than a toy example.

One source, many targets

A core design goal is portability across multiple compilation targets. The library includes a GLSL style macro layer so the same source can compile as C++, GLSL, CUDA, Metal Shading Language, or Slang. For pipeline folks, that is the headline hiding behind the headline. A single code path that can be shared between CPU side reference evaluation and GPU side shading variants can reduce mismatches between offline and realtime looks, reduce duplicated bug fixing, and cut down on the inevitable drift that happens when implementations fork.

This release is presented as a reference implementation, but it is also explicitly described as the physically based production implementation that ships in an internal engine. That is a different promise than a pure spec document. It is code that has been used in anger, then packaged to travel.

What this changes for lookdev and realtime teams

The practical value for working artists and tech artists is consistency. A reference implementation offers a common baseline for how OpenPBR 1.0 behaves across tools and targets, especially when the same source is intended to compile into CPU and GPU contexts.

For realtime teams, the goal of compiling into shader languages and shader adjacent toolchains is the kind of detail that can save weeks. If your renderer uses GLSL and your tools team validates materials in a C++ baker or previewer, sharing one library can reduce the odds that two implementations disagree in subtle ways.

For offline teams, a compact library with a clean API can be easier to wrap into a renderer plugin, a USD shading adapter, or a testing harness that validates renders across builds. Nothing in the provided facts claims any of those integrations exist out of the box, but the library shape is clearly aligned with that kind of usage.

Some of the most valuable wins in shading are painfully unglamorous. Deterministic results across targets, fewer implementation forks, and clearer testability can be the difference between a stable material library and a never ending parade of look diffs.

One reminder that applies to every new shading drop, no matter how solid it sounds: new tools and innovations should be tested before use in production.

The vendor angle

Adobe is positioning this as a public release of a production OpenPBR 1.0 BSDF implementation, repackaged into a minimal single header library with a cross target macro layer.

https://github.com/adobe/openpbr-bsdf

The post OpenPBR BSDF reference code from Adobe first appeared on DIGITAL PRODUCTION and was written by Bela Beier.