Base Thickness vs. Blend Depth: Pick the Right HueForge Control

Y'all, I'm excited about this one because the 2.64 mm Blend Depth test makes the difference impossible to miss.

Both controls add height, but they solve different problems. If they still feel tangled, that's okay. We'll test one at a time.

Base Thickness controls the solid foundation below the image. Blend Depth controls the available height for the image and its color transitions above that foundation.

In October 2025, I pushed Blend Depth from 1.76 to 2.64 mm on a four-color image. I don't have a ruined print to dramatize—I stopped before wasting it. The preview grew from 2.24 to 3.12 mm and from 27 to 39 positions without fixing a named region.

What you need: Open a finished HueForge project. Keep your slicer—the program that turns HueForge's exported mesh into printer instructions—nearby. If you have not built a project, start with my first HueForge setup tutorial, then return with a basic filament stack.

By the end, you'll know which control to move, what number should change, and when a smaller layer height is the cleaner answer.

Start with the height budget

HueForge builds a thin relief image. Dark or low parts sit close to the base. Lighter or higher parts rise through the color region.

The two controls divide that model into different jobs:

Base Thickness is the solid foundation. Increase it when exposed base-color areas need more material or the panel needs more rigidity.

Blend Depth is the vertical height available for the image and color transitions. Increase it when the stack needs more possible layer positions.

The practical mental model is:

Total allowed model height ≈ Base Thickness + Blend Depth

That is a height budget, not a promise that every possible layer will carry a filament change. The image and its color placements decide what HueForge uses.

This is the same height model I teach inside HueForge Basics & Theory in HueForge Pro.

Mesh Mode is the method HueForge uses to turn image colors or brightness into model height. Leave your project's existing Mesh Mode unchanged during this test. Changing it would rebuild the geometry and ruin the comparison.

Base Thickness grows the foundation. Blend Depth expands the color range.

HueForge renamed the older Min Depth and Max Depth controls to Base Thickness and Blend Depth in the 0.9.0 interface. The new names describe the model more clearly. Current HueForge 0.9.4.3 still uses the same relationship.

In the current interface, find these values together on the settings strip along the bottom. Layer Height is the thickness of each printed layer. Base Layer is the first-layer thickness. Mesh Height is the total-height readout.

The Color Core is the vertical filament stack in the middle of the workspace. Scroll over a filament chip, use the arrow keys, or drag it to move its placement one layer at a time.

Here's the diagnostic split that matters:

If the weak area is mostly the bottom filament, investigate Base Thickness.

If the color stack needs more possible layer positions, investigate Blend Depth.

If the stack needs finer positions without as much extra height, investigate Layer Height.

Layer Height must match between HueForge and the slicer. A mismatch moves color changes to the wrong physical heights.

One more setting matters here: Depth Mode. Static Depth keeps the layer range you set. Dynamic Depth may squeeze the useful color layers into a smaller part of the model, even when Mesh Height increases.

Step 1 — Record the starting math

Don't drag a setting and judge only the prettier preview. Write down the starting values first.

Record these five values:

Base Thickness

Blend Depth

Mesh Height

Layer Height

Reported layer count

The source project started at a 0.48 mm base and a 1.76 mm blend region. HueForge reported a 2.24 mm mesh height and 27 layers.

The arithmetic checks:

0.48 mm + 1.76 mm = 2.24 mm

At a 0.08 mm layer height, that height has 28 positions. HueForge starts counting at zero, so those positions appear as 0 through 27. Use the exported swap heights for production. Don't build a swap plan from mental division alone.

Take a screenshot or save a project copy before changing anything. Then change one control at a time.

Checkpoint: You can state the current foundation, color range, total height, and layer height without guessing.

Step 2 — Diagnose a foundation problem

Look at the flat preview and ask where the print is physically thin. If broad corners or exposed background areas are mostly the base filament, test Base Thickness first.

The source project's corners mapped close to the bottom of its height range. That left those areas made almost entirely from the base filament.

I raise Base Thickness from 0.48 to 0.80 mm. Mesh Height climbs from 2.24 to 2.56 mm, while Blend Depth stays at 1.76 mm. The foundation grows; the color region does not.

The color region did not gain extra room. The same 1.76 mm Blend Depth moved upward on a thicker foundation.

A thicker base is plywood under the picture: the panel gets sturdier, but the color area does not grow.

Use the smallest increase that solves the physical problem. HueForge steps these controls in increments of the selected layer height. At 0.08 mm, moving from 0.48 mm to 0.80 mm adds four layers of foundation.

Judge the result in three views:

HueForge Slicer View: Press the middle mouse button over the preview to toggle the flat-color view. Confirm that the fragile area is base-dominant.

HueForge lit preview: Toggle back and confirm that the image itself did not change.

Slicer: Export the candidate STL—the mesh file HueForge creates. Inspect its side profile, then check the added time and material.

Don't assume every wall piece needs a thick base. A small framed panel has different support needs than an unframed sign with exposed corners.

Checkpoint: The foundation is thick enough for handling and mounting, while the image's color range remains unchanged.

Step 3 — Diagnose a color-headroom problem

Now ask a different question: does the color stack have enough possible layer positions? If several colors are competing for too few heights, test Blend Depth.

Blend Depth expands the image region above the base. It creates more printable heights where you can place filament changes. It does not automatically make every gradient better.

The source walkthrough shows the relationship cleanly with the base held at 0.48 mm:

1.44 mm Blend Depth → 1.92 mm Mesh Height → 23 reported layers.

1.76 mm Blend Depth → 2.24 mm Mesh Height → 27 reported layers.

2.64 mm Blend Depth → 3.12 mm Mesh Height → 39 reported layers.

Those extra positions can help a Color Match build with many real filaments. Some filament needs several printed layers before its color becomes visible over the plastic below.

But more headroom is not free. The model gets taller. The print takes longer. A four-color image may gain nothing visible from another eleven or twelve layers.

I push Blend Depth to 2.64 mm. The project jumps to 39 positions, and I know I'm not printing it there. You might be thinking, “If the preview is smoother, why back down?” A position earns its place only when it fixes a named region.

After increasing Blend Depth, check every color placement. The top filament may no longer sit at the best height because the available range changed.

I move Blend Depth from 1.76 to 2.64 mm. Mesh Height jumps from 2.24 to 3.12 mm, and the white background falls apart. Now I select the white chip and move it higher, checking the background after each change.

Move one layer at a time. Stop at the first position that cleans the white area without washing out the black arch.

Use the preview as a comparison tool:

Save the original view.

Add one or two layer increments of Blend Depth.

Reposition only the color that lacks room.

Compare the target region at the same zoom.

Keep the change only when it improves a named region.

“It looks smoother” is too vague. Name the leaf edge, skin highlight, lettering, or shadow that improved.

Checkpoint: Every added layer position has a job in the color stack. If you cannot name that job, remove it.

Step 4 — Use Layer Height when you need finer positions

Sometimes the stack needs more positions, but adding model height is the wrong trade. A smaller Layer Height creates finer vertical steps inside the same physical depth. Smaller layers divide the same height into tinier steps, so the printer takes more laps.

The source workflow uses 0.08 mm layers with a 0.4 mm nozzle. It pairs 0.04 mm with a 0.2 mm nozzle, but newer HueForge-specific testing updates that advice.

You can run 0.04 mm layers on a tested 0.4 mm PLA profile. The smaller layer height improves vertical resolution. A 0.2 mm nozzle mainly improves side-to-side detail, such as tiny lettering and edges.

That can produce smoother transitions and finer surface detail. It can also make the print substantially slower.

Treat those numbers as examples, not universal prescriptions. OrcaSlicer's current guidance gives a conservative nozzle-based range. Stay inside a tested profile for your machine.

Then make the same change in both places:

Set the chosen Layer Height in HueForge.

Set the matching layer height in the slicer for the color region.

Rebuild the color swaps from the exported height instructions.

Slice and inspect the actual change heights before printing.

Avoid adaptive or variable layer height through the color region. A changing layer thickness breaks the direct relationship between HueForge's planned heights and the slicer's layer numbers.

You can still print the solid base faster with a Height Range Modifier. That slicer feature uses thicker layers only below the image region. Keep the color region at HueForge's planned layer height. Verify each swap at its exported physical height above the build plate.

Checkpoint: HueForge and the slicer agree on the color-region layer height, and every swap lands at the exported physical height.

Step 5 — Run the three-question decision test

Before exporting, ask these in order.

1. Is the print physically weak where only the base color shows?

Increase Base Thickness in small layer-height increments. Stop when the part is strong enough for its use.

2. Does the image need more possible heights for the color stack?

Increase Blend Depth in small increments. Recheck the top filament and every affected transition.

3. Do you need finer positions without much more physical height?

Use a smaller supported Layer Height, often with a smaller nozzle. Accept the longer print time and verify the slicer profile.

One project can need all three adjustments. Think of these as three different wrenches, not three sizes of the same one.

Build a controlled comparison

A good settings test changes one variable and preserves everything else. Make three saved versions before you commit to a long print.

Name them so the numbers stay visible:

A-original-base048-blend176

B-thicker-base080-blend176

C-more-blend-base048-blend208

Version B answers the foundation question. Version C answers the color-headroom question. Those are separate tests, even if both previews look taller. This one-variable test is really, really helpful when both previews look better.

Open the same region at the same zoom in each version. Compare the exposed base areas first. Then compare one difficult color transition.

Write down four results:

Which region changed?

Did the change solve the named problem?

How much height did it add?

What did the slicer estimate change?

I love this comparison because the winning version gives you awesome evidence instead of a prettier hunch. A taller preview can look smoother even when the target area was already good.

For a physical check, do not re-import a cropped source image. Cropping can remap brightness, rebuild the mesh, and invalidate the comparison.

Instead, export the full candidate mesh first. Use the slicer's Cut tool to isolate the troublesome side-to-side area. Keep the full bottom-to-top height and the same filament changes. Make sure the cut piece still starts at the original print height. If it does not, reject that test and compare the full project.

A small mesh cut will not prove that the full-size panel is strong enough. It can show whether one added blend increment improves the target transition without rebuilding the HueForge geometry.

Keep the winning project and archive the other tests with their numbers intact. Next time the same failure appears, you'll have evidence instead of a remembered hunch.

When more Blend Depth appears to do nothing

This is the advanced failure that catches experienced users. The number climbs while the top color waits like it missed the elevator.

Check the depth mode before adding more height.

Dynamic Depth may squeeze the useful color layers into a smaller part of the model when the stack gets deep. Static Depth keeps the range you set, which makes manual color placement predictable.

Switching modes can change the mesh. Save a project copy first, change the depth mode, then compare the same named region. Keep the mode change only if it restores useful layer positions without breaking the image.

If Static Depth still leaves the top color pinned, inspect the Color Core's saturation marker. That marker shows where more layers stop changing the visible blend. Adding height above a saturated color wastes thickness.

A better default than “which matters more?”

Neither setting wins. They measure different things.

Base Thickness controls how much solid foundation the print needs.

Blend Depth controls how much vertical room the image and color stack need.

Layer Height controls how finely that room gets divided.

Write those three questions beside your next project. You'll stop adding height blindly and start spending every layer on purpose.

If you want the full working demo, watch Base Thickness vs Blend Depth. HueForge Pro members can revisit HueForge Basics & Theory for the underlying height model and Color Match for filament-transition control.

Then bring your before-and-after screenshots to the Discord crew. Tell them which lever solved it. That comparison will teach more than another unexplained settings screenshot.