Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Layers and depth

This is the chapter that makes shapes stop looking like slabs.

Depth belongs to a layer, not a pixel

You cannot give one pixel a different thickness from the pixel beside it. What you can do is put them on different layers and give each layer its own depth.

A face, a nose, a pair of eyes: three layers, three depths, and you have relief without ever leaving the 2D grid.

Every layer carries two numbers, both at the top of the Outliner:

What it means
Depthhow thick the layer’s slab is
Z offsetwhere that slab’s centre sits along the depth axis

Both are whole pixel counts and their sliders snap to whole steps, mid-drag included.

Any slider can be typed into — click the number and enter a value. And Shift slows a drag to a quarter rate, which is what makes a 129-step range usable in a panel a hundred pixels wide.

The Outliner

The layer list, and the layer you are on. Add, remove, rename, toggle visibility, solo a layer to work on it alone, and move one forward or back with ^ and v. The readout at the head of its list says how many layers there are and how many separate islands of artwork they add up to.

Layer order decides which layer wins where two slabs contest the same depth, and the 2D blend order. It is not the same thing as where a layer sits in space — that is Z offset.

Hiding a layer, and soloing one

Each row carries a tick and a solo dot, and they are two different questions. The tick is is this layer part of the drawing; the dot is am I looking at this one on its own for a minute.

Untick a layer and it leaves the drawing — the whole of it. The canvas, the deck, the 3D view, the line art, a recording and every file you export are built from the layers that are ticked, so putting one away and pressing Export gives you a model without it.

Reaches
the tickeverything: the 2D canvas, the layer deck, the 3D view, the line art, recordings, and every file that comes out
the solo doteverything you look at, and the pictures taken of it — but never the .glb, the .bbmodel, the .obj or the .stl

Solo stops short of a model file because it is not saved with the project. It is a lens you flick on and off a dozen times an hour, so a file built through it would come out differently tomorrow from the same drawing, and nothing in the drawing would say why. Hiding is saved: put a layer away, close the project, and it is still away when you open it next year — which is exactly why it can be trusted to travel into an export.

Hiding a layer is not an edit. Put one away to see what is behind it, make a stroke, then press Ctrl+Z, and it is the stroke that goes. Undo steps back through the drawing you made, never through the way you happened to be looking at it.

Seeing through a layer

Opacity fades a layer on the canvas, and it is how you draw one shape over another: turn the layer in front down to a third and trace the thing behind it.

It lives on the bar along the foot of the 2D canvas, in the LAYER group — the key beside solo and clear. Click it and a small panel with one slider opens above it. The key stays lit for as long as the layer you are on is faded, so a layer you turned right down last week cannot quietly stay that way.

It reaches the canvas and nothing else. Not the 3D view, not the deck, not the line art, not a model file — a layer faded to a whisper is still a solid block in the model, at every value including nothing at all. The one picture that follows it is the artwork PNG, and only because that file is the canvas written out.

It used to be a slider in the Outliner, sitting between Depth and Z offset — which are geometry — so it read as a third piece of geometry, and people reasonably expected a faded layer to come out faint. It never did. Moving it to the surface it actually affects was the fix; there was nothing to be gained from a note underneath explaining that two neighbouring sliders meant something else.

It no longer dims cards in the layer deck either. The deck has its own way of getting the sheets in front of you out of the way, and the two were fighting: a faded layer came out fainter than the card standing in front of it, so the one you had asked to look at was the hardest to see.

^ and v move a layer through the model

They step the active layer one place through the front-to-back order, and what that costs depends on what it is stepping past:

The layer it passes isAnd ^
at a different depthtrades places with it along the depth axis — the layer genuinely moves in space
in the same planeswaps their places in the list, which is what decides who wins a contested range

Step a layer one way and then the other and it is exactly where it started. The two layers exchange their positions rather than being recomputed, so nothing drifts however long you spend nudging a stack into order. What that gives up is the span the pair covered: two slabs of different thicknesses cannot both keep their thickness and still fill the same run, so the gap between them is kept and the outer edge moves. With equal depths — which is every layer in a fresh document — nothing moves but the two layers.

A thin slab that was buried inside a thicker one is lifted clear rather than swapped, because trading centres would leave it swallowed exactly as it was.

The status bar says already at the front or already at the back rather than doing nothing quietly.

Pack the layers back to back

Pack layers, the last key on the Outliner’s toolbar, gives every layer a Z offset so the slabs touch, centred on zero. It is the fastest way from “four layers all at zero” to something with front-to-back structure, and it is refused with a reason when there is only one layer and therefore no gaps to close.

Hidden layers take part, and that is not an oversight. Packing decides where each slab sits, which is a question a layer still has an answer to while it is put away — skip it and you leave a gap with nothing in it, waiting to be wrong the moment you tick the layer back on.

Several layers at once

Layers have a selection of their own, and the active layer is always part of it.

DoGet
Ctrl+click a rowadd that layer to the selection, or take it out
Shift+click a roweverything from the active layer up to that one
the select-all key in the Outlinerevery layer; click it again for just the active one

With two or more selected, Squash flattens them into one. Where two of them have a pixel in the same cell the one further forward in the model wins — the same rule the 2D canvas blends by, so squashing cannot change the picture. The result keeps the lowest layer’s name and depth.

It flattens the layers you can see, and leaves the rest alone. A layer you have unticked takes no part and survives untouched, so squashing three layers with one hidden leaves you two rather than one. Both halves matter: flattening a layer you had put away would bring back artwork you had put away, and leaving it out of the flatten while still removing it would be worse than either — that is artwork destroyed rather than resurrected.

Two things deliberately do not count. A faded layer lands at full strength, because opacity is a way of looking at the drawing and baking it into pixels makes that permanent. And soloing changes nothing, because it is a lens you toggle constantly, and losing a layer over how you happened to be looking at the stack would be a loss with no gesture behind it.

Squash is refused rather than hidden, and says which of the two it is: fewer than two layers picked, or fewer than two of the picked ones showing.

Delete, with the Outliner focused, removes the layers you have selected.

Flextrude

F. Paint over the drawing to mark cells out, then raise what you painted into a slab of its own, in front of everything.

It is the odd one out among the tools — it lays no colour down at all, and it reads the whole stack rather than the layer you are on. What it makes is not a mark but a layer, which is why it lives on this page.

The wash you paint is not a selection: nothing lifts, nothing moves, and the cells stay exactly where they are until you ask for the raise.

ControlDoes
Size / Shapethe brush you mark with, the same pair the brush itself has
Depthhow far the painted pixels are raised, in canvas pixels
Instant punchon, a stroke raises itself the moment you let go; off, paint as much as you like and then press Raise
Raiselift the painted cells into a slab of their own
Clearunpaint every cell, leaving the drawing exactly as it is

Only cells the canvas actually draws can be marked, and the refusal is in the brush rather than in the button — so the wash you can see is exactly what Raise will act on.

Raise repeatedly and the new slabs abut rather than drifting: each one is placed against the back of the last, on whole pixels.

The layer deck

The deck shows your layers as cards floating in 3D, sorted by their actual position. It is the view where “which layer is in front of which” stops being an abstraction.

Order in the deck is position; order in the Outliner is priority. Keeping those apart is what makes the deck honest:

What it isWhere you change itWhat it affects
Z offsetwhere the layer sits in the volumethe deck’s Move mode, the Outliner’s slider, or ^ / v past a layer at another depththe geometry
Layer orderwhich layer wins^ / v past a layer in the same planewho owns a contested range, and 2D blend order

The Outliner’s two arrows reach both, which is the point of them: they mean “move this forward” and let the document work out whether that is a matter of space or of priority.

Cards are sorted by actual z, and ties break by layer order — the mesher’s own rule, so the fan is never a fiction.

Three modes

The deck has modes rather than modifiers, because the left button has four plausible meanings here.

ModeLeft buttonShift+leftRight button
Lookdrag orbits · click selects——
Paintpaint the active carderaseorbit
Movedrag a card along z—orbit

In Paint mode the active card owns the pointer wherever it lies under it, so you can aim at the layer at the back of a stack through the artwork of a nearer one. Switching layers lives in Look mode. Flextrude is the one tool the deck refuses — what it makes is a new layer, and a deck of cards is not where you ask for one.

Seeing the card you picked

Cards you are not working on are drawn faint, and a card standing between you and the one you picked is fainter still. Choose the layer at the back of the deck and the sheets in front of it step aside far enough that you can read it — no need to solo, which used to be the only way through.

They do not vanish, and that is on purpose: their silhouettes are most of the reason to use this pane at all. Orbit round to the other side of the deck and the roles swap, because which cards are in the way depends on where you are standing.

Push the camera in and cards dissolve as you reach them, one plane at a time, until the layer you are painting is the only thing left. Close up a half-visible neighbour is the worst of both — too faint to be context, still enough to tint the pixel you are judging.

True Z, spread and labels

True Z shows the cards at their real spacing. Turn it off and the spread slider opens the gaps so every card is visible and clickable — the same order, pulled apart. It is a zoom along z, not a re-sort.

Layers that share a plane fan apart by a hairline, so a tie is visible rather than one card hiding another. When there are ties, a Pack layers key appears on the deck’s own bar and says how many layers share an offset — the same key the Outliner has, offered where you noticed the problem.

Labels puts each card’s name beside it, and Frame points the camera back at the whole deck.

Which way the layers run

Every project reads its layers one of two ways, and the choice is a switch in two places: Layers bottom to top on the Project pane’s World placement card, and the stepped-block key along the bottom of the 3D view. They are the same setting; use whichever pane is open.

The canvas isA layer’s Z offset moves itThe model
off — back to frontthe front viewtowards youstands up, extruded out of the page
on — bottom to topthe top view, a planupwardlies on the ground, a stack of slices

Nothing about the drawing changes, and neither does the order the layers sit in. What changes is which view of the model your canvas turns out to be. Back to front, the layer that reaches furthest forward is the one nearest you; bottom to top, that same layer is the highest slice. Draw a pyramid as concentric squares on layers at rising offsets and turn it on. Draw terrain as contours.

The 3D view is the only place the difference can be seen, which is why the key lives there: the canvas looks identical either way, and that is the point of the feature rather than a limitation of it.

Bottom-centre is the one pivot the switch moves. It is a promise about the world — the model’s base lands where you place it — so bottom to top it rests the lowest slice on the ground instead of the bottom edge of the canvas. Center and Top left describe the canvas and mean the same cell whichever way the model is built. See Exporting.

The setting is saved with the project and travels into every export, and one Ctrl+Z takes it back.

What the mesher does with all this

Worth knowing, because it explains why some things are impossible and others are free.

Layers are never meshed separately. For each column of the canvas, the slab of every layer taking part is collected and resolved into one list of non-overlapping spans, with upper layers winning any contested range. Front and back caps come from the ends of each run; side walls are the parts of a span the neighbouring column does not cover.

This means coincident and buried faces cannot be generated, because nothing ever emits them. Two layers whose planes touch exactly will not z-fight.

Faces then merge greedily into the largest rectangles they can. A solid 8×8 block is six quads. A 32×32 cloud is about 130.

One consequence to know about: the side colour is per column, shared by all four of that column’s walls. Rim-painting the top wall of a pixel also paints its side walls. On a straight run you never notice, because the other walls face away. On a staircase, where one pixel shows two walls at once, you do. It is a deliberate trade — one click colours a whole step instead of four.