For those who don’t know the tool: Drivers is a Blender rigging and animation add-on that builds driver setups for shape keys, adds viewport control panels, and manages action constraints, all from one sidebar so you can stop spelunking in editors.

What Drivers 2.0 is actually shipping

Drivers 2.0 is a paid Blender add-on that groups three ideas into one place: shape key drivers, viewport control panels, and action constraint management. The pitch stays practical. You pick a mesh, select a bone, set min and max, then wire a shape key to a bone transform with one click. The product explicitly calls out “No graph editor, no scripting.” That alone will make some riggers cheer and others quietly back up their files.

Drivers also frames itself as a workflow organizer for animators and riggers, with a focus on keeping controls in a clean N-panel interface. That is the part that usually gets messy first once a rig grows beyond a face and two hands.

Shape keys without the ceremony

The Drivers tab centers on instant shape key automation. Shape key values can follow bone rotation, location, or scale in real time, and the listing includes support claims for Rigify, Auto-Rig Pro, and custom rigs.

That makes it a tool for people who build facial systems, create corrective shapes, or apply quick pose-based deformations and want the setup to feel less like a spreadsheet and more like an actual rigging task. The appeal is speed, and also staying orgnaized once there are dozens of relationships to maintain.

Drivers 2.0 also bundles bone highlighting and bone colour management into the same UI, so the rig can communicate what is what without relying on naming discipline alone.

Viewport panels that behave like controllers

The Panels tab focuses on in-viewport control panels. It can spawn custom-shape bone panels in the viewport, with square, horizontal, and vertical control styles, and the idea is simple: drag a controller to blend shape keys without leaving the 3D view.

Text labels can be attached to panel bones via font objects, with type, scale, and offset controls exposed in the N-panel. That makes the UI layer explicit, which matters when a rig gets handed off to someone who did not build it.

There is also a master control option that adds a master bone to reposition every panel as one group, with offsets baking automatically when you hit Done. On top of that, a global lock can freeze panels to prevent accidental movement or edits before delivery.

If you have ever watched a control panel drift two pixels per shot because someone grabbed the wrong thing, you already know why that lock button exists.

Actions get their own manager

Drivers 2.0 includes an Action Constraint Manager in an Actions tab. It can assign directional action constraints to any control bone and uses a viewport glow highlight to show which bone is being edited live. The product page also lists compatibility notes that mention Blender 5.x layered actions alongside rig systems like Rigify and Auto-Rig Pro. In the same listing, the details section lists a Blender version range of 5.0 to 5.1, while another compatibility line states Blender 5.1+.

Pricing, license, and where it lives

Drivers 2.0 sells for $30 on Superhive, on a GPL license. The add-on is developed by Weybec,and remember: New tools should earn their keep the boring way: install, stress test, version-check, and only then let them near production rigs.

https://superhivemarket.com/products/drivers
https://weybec.com/

The post Drivers 2.0 cleans up Blender rigs first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Light Painter is a Blender add-on for lighting lookdev that paints onto a light texture in Cycles using Spot or Area lights, right in the viewport.

Setup: Cycles or nothing

Light Painter by ShaderError depends on Cycles light texture nodes, so it requires Cycles as the render engine. It does not support Eevee for this workflow. The baseline is Blender 3.6 through 5.1, and tCycles as the render engine and GPL as the license. Before you get excited and start scribbling highlights onto your hero asset, there is a short checklist that matters. You need a Spot Light or an Area Light, since the tool only works with those two light types. Point and Sun lights do not apply here, because the workflow relies on directional texture projection.

For sharper painting while you work, keeping the light size small helps. Spot Light uses a small Radius value and a Spot Size under 160 degrees to reduce distortion. Area Light uses scene scale dependent Size and a fairly low Spread value while painting. You can soften things later by changing Radius or Spread, but the painting stage favors crisp edges so you can read what you are doing.

The docs also recommend enabling GPU Compute for performance, since the tool relies heavily on shader computation. CPU rendering still works, but GPU is expected to be faster.

Painting on lights, not on meshes

The core idea is simple: you paint into a texture image that drives the light, and the tool previews the result in the viewport while you paint. You choose the target light in a panel, pick a texture resolution, and run a reset action that initializes the node setup. Then you paint using tools that include a brush and a gradient tool.

Light Painter stores the paint in a light texture image, with selectable resolutions from 512 pixels up to 4096 pixels. Higher resolution gives finer detail at the cost of more memory and slower interaction.

There is also a surface scoping system that controls what receives paint. You can paint on all meshes, a single object, or a collection. Separately, there is a skip list for objects that should behave as transparent for the painting depth pass, like glass windows, translucent curtains, fog and dust volume boxes, wireframe grids, and objects used for volumetric effects. If a see-through object blocks your strokes, it needs to be marked there.

Layers, masks, and the temp EXR stash

Light Painter includes a Photoshop style layer stack per light. Layers have blend modes, opacity, visibility, and transforms, and they composite from bottom to top. Blend modes listed in the docs include Mix, Multiply, Screen, Add, Subtract, Overlay, and Soft Light.

Each layer creates a Blender image datablock to hold pixel data. The layer system also writes temporary files to disk in the OpenEXR format to support undo, persistence, and compositing. These temporary files are cleaned up automatically when the add-on is disabled or when Blender closes, and layer metadata such as names, blend modes, order, and transforms is saved inside the blend file.

Layer transforms are non-destructive in light UV space, with offset, rotation, scale, and a pivot. The docs list shortcut gestures while the brush or gradient tool is active for moving, rotating, and scaling the active layer.

Selections add another control lever. You can build a mask to restrict painting so areas outside the selection are protected. The selection tool supports rectangle, polygon, lasso, and brush shapes, plus modes like add, subtract, and intersect. Expect to use this when you want to localize a fill or protect a face from accidental spill while you dial in a rim.

About that spill: the docs warn about light bleed beyond the painted region when the light source has a physical size. Blender can spread light beyond the texture boundary and into shadowed areas, and the current version does not compensate for that during painting.

Camera space vs light space

There are two paint spaces. In camera space, the paint is designed to match what you see on screen, with brush falloff mapping one-to-one with the viewport result. In light space, the brush math and gradient blending happen in the light texture space, while the brush centre and gradient endpoints come from the viewport, which can look distorted in the viewport depending on angle and distance.

Light space comes with two projection approaches for mapping the cursor. Raycast traces against geometry each frame and falls back when the cursor moves off surfaces. Plane establishes a paint plane on the first click, then projects subsequent cursor positions onto that plane. The gradient tool always uses raycast in light space.

This split is practcial. Camera space supports quick art direction because what you see is what you paint. Light space supports behavior that follows the light texture space more directly, and the docs describe it as a fallback for edge cases where camera space painting fails to cover some texels, such as steep angles or complex shadow boundaries.

Some studios will end up using both in the same shot. Start in camera space for broad strokes, switch to light space for the annoying bits, and remember that the annoying bits always find you in the final.

Preview and troubleshooting

The add-on includes a real-time overlay preview system. One mode previews only what is currently being drawn. Another mode overlays the full light texture and mask across the viewport and marks unpaintable areas in red, so you can see where the light reaches and where it is blocked.

There is also a preview option to show raw paint colour versus a falloff preview that includes rendering factors like distance attenuation and exposure. A light blur option attempts to mimic how Blender spreads the light based on the physical size of the source, with a multiplier to scale the effect.

If the result looks broken, reset the operator that rebuilds the shader node setup and resets layers. Changing light size can reset layers because the texture proportion ties to light size, and the docs recommend undo if the size change was accidental.

Advanced settings in the docs cover near and far clip for the light frustum, a surface bias for shadow acne, softness and bleed reduction controls, and internal capture resolutions.

Pricing and licensing

Light Painter is sold on Superhive in multiple tiers. LightPainter Lite is listed at $12. LightPainter for individuals is listed $36. LightPainter Indie for up to 3 people is listed at $80. LightPainter Full for up to 14 people is listed at $350. LightPainter Studio for 15 or more people is listed at $750. Currently there is a promotion that halves the prizes, no idea how long that goes.

As always, test any new tool and workflow in a controlled scene before it touches production assets, especially anything that rewires nodes, writes temp files, or changes how your lgiht setup evaluates across machines.

// Product page, pricing tiers, compatibility, license
https://superhivemarket.com/products/light-painter

The post ShaderError Light Painter paints light in Blender first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Nature Generator is a procedural asset library add-on that lives inside Blender via the Asset Browser and an N-panel, sold on Superhive Market, so you can kitbash nature without leaving your DCC.

The whole point is staying in your scene

Nature Generator builds natural assets directly inside Blender. Rocks, terrains, plants, water, and other environment bits all come in as editable, generated assets rather than fixed meshes. You drag an asset into the scene, the side panel recognizes it, and the controls you need show up without a detour to another app. The comparison to Quixel Megascans is obvious, being fully procedural and customizable.

The minimum version requirement is Blender 4.1 or higher. Hardware requirements call for a modern GPU from NVIDIA, AMD, or Apple Silicon. There is an optional texture options folder with 1K, 2K, and 4K texture resolutions. By default, the add-on uses low resolution preview textures, and the guidance recommends keeping the texture folder on a fast local SSD because it affects performance.

Installation stays simple. You drag and drop the zip into Blender, click OK, and the library sets up inside the Asset Browser. The Nature Gen panel appears in the side panel and opens with the N key. From there, drag and drop assets into the scene and start tweaking.

Geometry controls that reward restraint

Every asset follows a similar structure: shader settings and geometry settings, with slightly unique controls per asset. Geometry includes a resolution section, and most assets support a low-poly option. Viewport and render resolution can be controlled separately, and resolution can be subdivided or voxelized depending on the asset.

The documentation also includes the most honest feature statement possible: resolution can go infinitely high, and every asset can crash Blender if you push it too far. That makes the control powerful, but it also makes self-control part of the user interface.

Base shapes come from primitive forms you can alter in edit mode. Some assets follow the structure of a mesh and react to topology. Some are planes. Some are driven by curves. Displacement settings include multiple texture and noise displacement controls, with patterns such as noise breakup, stratification lines, and crack patterns. Many categories expose basic settings and an advanced subcategory for deeper tuning.

At around the moment you start dialing prcoedural detail like it is free, that crash warning stops reading like documentation and starts reading like prophecy.

Custom shaping can use a gradient with its own displacement, falloff, location, and scale settings, with viewport gizmos available when the modifier is selected. Alternatively, a custom curve object can influence the terrain, with a radius setting and a distance based falloff where farther from the curve means weaker influence. A secondary custom shape can be added, such as one curve for valleys and another for mountains.

Scatter was rebuilt to be more direct

The latest update changes how the scattering system works. If you have an older version, the update workflow shown is to download the new version from Blender Market and drag and drop it into the scene so it overrides the old version.

The new scatter setup aims to be simpler with fewer settings. The key change is the import flow. You import the specific assets you want to scatter, then assign them into the scatter collection. After importing, you can toggle an exclude option so the collection does not sit visibly in the scene, while still being used by the scattering system.

Core scatter behavior remains familiar. You can adjust density, and you can still use slope based scattering, altitude based scattering, and noise based scattering. Scatter zones remain part of the tool, controlled by empties with viewport gizmos so you can define a local area for scattering.

The update also introduces threshold softness controls across settings. The stated purpose is scaling down scattered assets toward the edges of masks. That creates a smoother falloff where a hard cutoff would look like a stamp.

Draw where the scatter goes

A major addition in the update is a scatter curve or grease pencil option. You can assign a curve or a Grease Pencil object and use it to decide where scattering appears and where it does not.

The workflow shown is straightforward: create a blank Grease Pencil object, draw directly on the surface, then select that drawing as the scatter guide. The same idea works with a curve object. You get controls for draw radius and radius softness, and the falloff scales down scattered assets toward the edges. There is also a noise option to distort the shape and avoid a too clean, too perfect outline.

Remove the draw object, and scattering returns to the default behavior. That makes the feature easy to test and easy to abandon if a shot changes direction.

Viewport survival mode, now with choices

Scatter can get heavy. The update adds a display mode control in the instance settings. You can display instances as originals, as boxes, or as wire box. Instance scale stays, but the update adds a secondary scale and a secondary scale probability. That lets a minority of instances become much larger than the rest, adding variation without requiring a second scatter layer. Rotation controls remain.

There is also a new wind animation option for scattered assets. Wind time is a value you animate, with an example workflow of adding a driver expression using hashtag frame and optionally dividing to slow it down. The update explains why this stays manual: using a scene time node inside node trees made performance drop sharply, including an example of frame rate dropping to around seven. Removing the time node restored smooth playback. With many scattered objects each carrying the scatter system, the update keeps wind time explicit to protect performance.

Terrains, water, and the new step look

Terrain and mountain assets use a separate X and Y resolution, because resolution on those axes influences the shape and form of erosion. Terrain maps include a random seed, and terrain can generate from noise or be influenced by a custom shape.

Noise displacement includes control over influence on X, Y, and Z, plus a noise seed and standard noise settings. Texture displacement adds rock detail. Erosion settings apply erosion from a selected height, with placement, falloff, and an option that can add mountains and inverted valleys. Boundary falloff can flatten edges.

Water effects add a cube with a procedural water shader. Controls include height and depth, and rivers can be created by combining a water effect value with custom curve shaping that pushes terrain down so water appears in selected areas. Water shader settings appear in the shader tab, including animated noise controls to create the illusion of moving water with separate speed controls on X and Y.

The update adds terrain presets, including a forest preset and a canyon preset. The forest preset uses the scattering system, and trees can default to box display for performance on lower-end systems, with the option to switch back to originals. The update also adds a terrain steps feature on some presets, described as a stepping effect. Controls include the number of steps, detail, strength, and blur, with noise-based selection and influence. Terrain steps can be found in erosion settings, in noise settings, and when drawing along a custom curve.

Trees arrive, and snow gets more physical

The update adds tree assets. Tree shaders follow the same structure as flowers, including leaf color controls and translucency. Leaves can be pushed toward an autumn look by changing colors. There is also a setting for a leaf mask, and leaf shapes are generated procedurally, with controls for scale and mask threshold.

Scatter categories shown include plants such as flowers, wheats, grass, ground cover, shrubs, plus rocks, snow, and trees. Scattered rocks are procedurally generated and have their own settings such as resolution, shape distortion, size ratio, and a seed.

Snow scattering gets a notable twist. Importing a snow object can be recognized and turned into a volume style approach for creating snow on objects rather than only shader based snow. Snow settings sit in the geometry tab, including resolution and displacement settings. Particle detail adds small particles with alpha textures, intended to improve realism for close-ups. The tool also notes that foamy snow detail may require higher transparency bounces.

Materials, uniqueness, and the new override option

Materials are shared by default. The tool includes Make Material Unique to create a new copy of a material for the selected object, and Revert to return to defaults. The update also adds a use custom material feature for the new scatter effect. The workflow shown duplicates a material and assigns it as an override for the scattered assets, so you can make unique changes without affecting the original material used elsewhere.

Scatter effects can stack, and the update shows renaming modifier labels to organize multiple scatter effects. This is the part where it starts feeling less like an asset pack and more like a small ecosystem.

Pricing and what is actually specified

Pricing is specified on the product page. A Personal License costs $99. A Commercial License costs $169. A Studio License costs $259.

https://superhivemarket.com/products/the-nature-generator?ref=586

The post Nature Generator update brings procedural nature to Blender first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Real Caustics is a Blender add-on that bakes caustic textures for scenes, then you can carry them into a USD pipeline without dragging your render engine into a fistfight.

The pitch, minus the pool noodles

Caustics are the moving light patterns you see under shallow water, like on a pool floor or riverbed. Real Caustics is an add-on for Blender that targets that exact look, with a workflow built around animated water surfaces. It is designed for fluid simulations, ocean modifiers, dynamic paint, and any mesh-based water surface, with the pattern tracking the surface shape frame by frame.

The product page states a clear intention: stop faking caustics with video textures or noisy approximations, and generate patterns that follow the water motion instead. That is a creative goal, not a standards document, but it sets expectations for what the tool tries to automate.

One noteworthy disclosure sits right on the page: development used AI coding tools, while the author directed and validated the technical decisions, node structures, interaction logic, and tests.

Bake once, keep your renders on a diet

Real Caustics generates caustics as textures that get baked. The claim is that once generated, they add zero overhead to your render, since the heavy lifting happened during baking. The workflow is hands-on and iterative: Generate Current Frame writes a texture, reloads it, and shows it in the viewport in seconds. After you like the look, you generate the full sequence and render.

That bake-first approach matters for production planning. It shifts time from per-frame render cost to a preprocessing step you can schedule and version like any other cache. The baked output also means the textures can be used in any render engine, since they are just textures at that point.

In practical terms, this is the difference between fighting caustics every frame and treating them like any other animated texture sequence. If your waetr surface changes, you regenerate. If lighting changes, you may need to rebake depending on how you set things up.

Controls that aim at art direction

The add-on includes settings intended for look development. The product page describes intensity control independent of the light and water mesh. It also describes generating caustics straight from displacement and bump rather than relying on geometry density with smoothing patterns, adding dispersion, and a tiling mode for generating seamless textures, with the condition that the input geometry tiles reasonably.

When enabled, generation reads shader-based displacement and bump maps so the caustics follow the generated normals of the water, not just the base mesh. You can get the best results when a simulation generates real geometry while shader bump adds smaller detail waves.

Real Caustics is designed and optimised for water surfaces, but it maybe can produce interesting results with other glass objects, but it only accounts for a single ray pass. It explicitly states there are no internal bounces, depth variation, or IOR changes as rays are traced through geometry, and that standard path-traced methods give more accurate results for realistic glassware and gemstone caustics.

Engines, versions, and the part where you avoid surprises

Real Caustics generates caustic textures using both Cycles and Eevee. Since the output is baked textures, it can be used in any render engine. It also calls out USD workflows: you can generate textures in Blender and bring them into other software.

The listing specifies support for Blender versions 5.0 through the most recent 5.1 release, and the FAQ warns that after an update, you should check supported versions if something breaks.

There is also a specific setup constraint worth flagging for shot assembly: nested collections inside the Water Collection are not supported, only direct object members are supported, and collection instances will not work either. If you have a scene-building habit of nesting everything, this is the kind of detail that can quietly derail a bake until someone notices.

Caustics Energy Fix limits caustic intensity when light passes through multiple overlapping surfaces to prevent overbright artefacts, and it must be plugged in after the caustics texture.

Caustics Water is a pre-built Mix Shader combining Transparent BSDF, a surface shader input, and an Is Shadow Ray condition, handling the complete shadow ray setup in a single node.

Documentation also describes a Rebuild Node Groups function that reinstalls shader node groups into the current scene and overwrites node groups with specific names, advising you to rename node groups or create non-instanced duplicates if you want to keep older scenes working as-is. That detail is a polite way of saying version management still matters even when the UI looks friendly.

Pricing and licensing, spelled out

The listing includes multiple purchase tiers. The Individual license is priced at $30 and includes the add-on with full functionality plus a pack of pre-baked textures. A Studio option for up to five users is priced at $50. A Studio Pro option for five or more seats is priced at $70. There is also a Pre-Baked Textures product – a pack of 10 pre-baked animated textures that are seamless and looping, priced at $5.

As always with new tools, test in a staging scene before you roll anything into production, especially when re-baking sequences and updating node groups can change reuslts across shots.

https://superhivemarket.com/products/real-caustics

The post Real Caustics for Blender first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Procedural Clouds plugs into Blender as a volumetric sky builder aimed at Cycles, letting you rough in atmosphere during lookdev before lighting turns everything into a science project.

How?

Procedural Clouds exposes its controls in the N-panel, so you can steer the setup without opening node graphs. That matters in production because fewer accidental edits land in the wrong graph at 2 a.m.

Solid Preview is the key switch for fast iteration. Turn it on and the clouds show up in Solid mode. There is also an auto mode that watches viewport shading and toggles Solid Preview for you, keeping it off in Rendered mode and on in Solid mode.

The add-on also includes a Pin system that locks the UI to a target object so the controls keep talking to the right volume even when selection gets messy. Pin Auto Switch exists as a preference and is enabled by default, letting the pinned target follow the currently selected supported object. Turn it off and the pin stays glued to the original target.

Scene tweaks you should notice before they bite

Some features can automatically adjust Blender scene settings during use, including volume bounces, step count, and clip distance. If you want your scene settings left untouched, you need to disable those options in the add-on preferences or dial them back.

Clip Start and Clip End are specifically called out for Solid Preview artifacts. If the volume looks sliced or flickers, raise Clip Start. If the cloud gets cut off in the distance, raise Clip End. You also need to set matching Clip Start and Clip End values on the scene camera.

Made by Suzanne studio, the docs also flag that Blender 5.0 changed the algorithm for Voronoi Texture, so presets can look slightly different between Blender 4.5 and 5.0 even when the cloud remains the same and the seed changes.

Scaling rules that keep the look consistent

The scaling behavior is split by mode. Scale in Object Mode and the object changes size without changing internal settings, so the effect parameters stay the same and the visual result stays consistent. Scale in Edit Mode and you change the underlying volume or mesh size, extending the existing content while keeping internal settings and detail density stable.

The recommended starting point is a cloud object around 2 meters, then resizing in Object Mode. After extreme scaling, you may need to adjust Density to get the result back to where you want it, especially if your cluod suddenly looks like it went on a diet.

Knobs that trade detail for speed

Three controls define the look to cost relationship. Point Density controls how full the cloud is. Higher values produce thicker and more detailed clouds, while lower values produce lighter clouds and faster performance. Point Size Min and Max control variation in the cloud shapes. Higher values push softer and puffier shapes. Lower values push finer structure. Volume Resolution controls the final detail of the volume. Higher values sharpen detail but slow things down. Lower values render faster with a softer result. That resolution knob is also where perofrmance usually goes to negotiate for lunch.

Keeping your scene clean while you iterate

Make Unique creates an independent copy of a selected object so changes do not affect others. It is built for the classic moment when you duplicate a cloud, tweak it, and discover you just changed every cloud in the shot.

There is also a note about removing a Boolean Empty cleanly. Deleting the Empty in the viewport may leave it in the scene, so removal can require deleting it from the add-on panel or deleting it in the Outliner.

New tools and innovations should be tested before use in production, especially when they can touch scene settings and when shot continuity depends on repeatable volumetrics.

https://superhivemarket.com/products/procedural-clouds/

https://www.youtube.com/@suzanne_studio3d

Licensing and tiers

Pricing is tiered into three licenses, all of which include creator support and future updates.

The Personal tier costs $25 and is for personal or non-profit projects.
The Commercial tier costs $45 and is for commercial projects.
The Studio tier costs $110 and is a multi-seat license. It also lists custom features request alongside creator support and future updates.

The post Procedural Clouds with Cycles focus first appeared on DIGITAL PRODUCTION and was written by Bela Beier.