Blender 5.2 Mesh Bevel Geometry Nodes - First Indie Worksheet 2026

If you searched blender geometry nodes mesh bevel after Blender 5.2 LTS, you do not need another “finally!” reaction gif. You need a fill-in worksheet that locks six decisions before Discord invents a studio-wide “bevel everything tonight” sprint:

1. Version pin — you are on a real 5.2 LTS build (or you stop and upgrade on a lab clone first)
2. Lab prop only — Mesh Bevel lives on a disposable prop, not the live Steam hero mesh
3. Selection contract — which edges/verts get beveled (attribute, selection, or all — written)
4. Amount + segments budget — numbers you can defend in a mid-spec poly count review
5. Shade + normals honesty — Autosmooth / custom normals do not magically fix a bad bevel
6. Export + engine smoke — glTF (or FBX) hash + one Unity/Godot/Unreal import minute before “ship ready”

This URL is that worksheet. It is not the Blender 5.2 LTS upgrade lock (version pin + experimental edges). It is not the Stop Enabling Remote Asset Libraries without offline plan (network/offline refusal). It is not the 12 free remote asset library tools (host/list/offline toolkit). Those own upgrade governance and remote libraries. This URL owns the first Mesh Bevel Geometry Nodes evening with gates outsiders can footnote.

Why this matters now

October 2026 is when teams that “saw Mesh Bevel in the July notes” finally touch production props while Steam demo Scalability and art freezes still bite. The Blender 5.2 LTS press release positions 5.2 as the long-term support line for studios that need a stable pin. The Geometry Nodes 5.2 release notes explicitly call out the long-awaited Mesh Bevel node with detailed control over edges or vertices to bevel. That combination — LTS pin + new bevel node — is exactly when micro-studios either get a durable prop pipeline or explode poly counts and UV seams on the live demo branch because someone dragged Mesh Bevel onto every crate.

Release notes alone do not ship a receipt. Generic Geometry Nodes tutorials rarely cover game-prop budgets, export smoke, or when to HOLD bevel on a hero that already has custom normals. This worksheet fills that gap.

Direct answer: Fill Sections A–D this week on a lab prop. Choose LAB_ONLY, SHIP_PROP, HOLD_BEVEL, or PIN_THEN_BEVEL. Do not run Mesh Bevel on the Steam-facing hero until gates B1–B8 pass and the receipt JSON is filed.

Who fills this worksheet

Time: 45–75 minutes first lab prop; 20 minutes to re-run gates after each amount/segments tweak.
Honest limit: Mesh Bevel parameters and UI labels can shift in point releases — re-check the 5.2 Geometry Nodes notes and your local tooltip before you quote numbers to a partner. This worksheet models published 5.2 Mesh Bevel availability, not a promise that every bevel mode matches the Edit Mode Bevel modifier 1:1 forever.

Non-repetition

Pair fundamentals with the Blender for game assets — procedural modeling / Geometry Nodes, 25 free Blender-to-engine workflow resources, and Blender color space looks wrong in Unity when the bevel looks fine in Blender and pink/wrong in the engine.

Official facts you must quote (not invent)

From the 5.2 LTS press and Geometry Nodes 5.2 notes:

1. Blender 5.2 is an LTS line — treat studio pins seriously; do not “float to latest main” on ship machines.
2. Mesh Bevel is listed as the long-awaited Geometry Nodes bevel with detailed control over edges or vertices.
3. 5.2 Geometry Nodes also adds other large features (lists, geometry bundles, experimental physics, etc.) — do not stack Mesh Bevel night with experimental cloth/hair or remote-library enablement.
4. Edit Mode / modifier bevel folklore is not a substitute for measuring the Mesh Bevel node on your mesh.
5. A green Blender viewport ≠ a green engine import.

Pasteable diligence line:

We are evaluating Blender 5.2 Mesh Bevel on a lab prop with written edge selection, amount/segments budget, and glTF engine smoke before any Steam-facing hero uses the node. Receipt filed; ship branch untouched until B1–B8 pass.

Beginner path — 60 minutes

Prerequisites: Blender 5.2.x installed; git or zip backup of the .blend; one simple hard-surface prop (crate, panel, weapon clip) that is not the live demo hero.

1. Confirm Help → About (or splash) shows 5.2 — if you are on 5.1 or earlier, stop and use a lab clone on 5.2 (upgrade lock).
2. Duplicate the prop object → rename PROP_bevel_lab.
3. Add a Geometry Nodes modifier → New.
4. Add Mesh Bevel from the Add menu (search “Mesh Bevel”). Wire Geometry in → Mesh Bevel → Group Output.
5. Start conservative: small Amount, Segments = 1 or 2, selection = a few sharp edges only (or a boolean/edge attribute you understand).
6. Shade Smooth / check face orientation; fix flipped normals before you chase “bevel looks weird.”
7. Export glTF 2.0 (or your studio FBX path) → import once into the target engine.
8. Fill Sections A–D and paste the Discord script. Save the receipt JSON shape.

Common beginner mistakes:

Section A — Project identity (fill in)

Section B — Decision codes (pick exactly one)

Do not leave “we’ll bevel later.” Pick a code.

Destination worksheet

Worked examples (patterns, not fake case studies)

Pattern First crate evening — LAB_ONLY
You just installed 5.2. Duplicate crate → Mesh Bevel amount small, segments 2, four top edges only. Export glTF → Godot import. File receipt. Do not touch the demo crate collection.

Pattern Environment kit after green lab — SHIP_PROP
Lab panel passed B1–B8 with ≤15% tris increase and clean UVs. Promote Mesh Bevel to the kitbash wall panel set only. Heroes with baked bevel maps stay HOLD until a separate night.

Pattern Next Fest week — PIN_THEN_BEVEL
Demo is live. Art freeze. Keep Mesh Bevel experiments on a branch that cannot upload. Schedule promote week after unset. Pair with your store freeze checklist — not this node graph.

Pattern Hero with custom normals — HOLD_BEVEL
Bevel node destroys the look you already paid for in Substance/custom normals. Hold GN bevel; document “baked bevel maps remain source of truth” until a dedicated hero rebake sprint.

Section C — Node graph checklist (fill in)

Treat this as the graph contract. Empty cells fail the evening.

Selection honesty table

Amount / segments budget table

Section D — Gates B1–B8 (all PASS before SHIP_PROP)

If B1 fails, stop — upgrade lock first. If B4 fails, lower amount/segments or HOLD. If B8 fails, do not “fix in engine later” — the evening is incomplete.

Section E — Export and engine smoke

Cross-link the clean art handoff checklist and the hero glTF hash evening when this prop is diligence-facing. Mesh Bevel does not replace hash discipline.

Engine lane notes (one paragraph each)

Unity: Import once; check Model tab scale, Normals/Tangents, and Read/Write if you need runtime mesh access. Color-space fights belong in the sRGB vs Linear help — do not blame Mesh Bevel for a linear workflow miss.

Godot 4.x: Prefer glTF; confirm mesh arrays and tangents. If you use LODs, decide whether bevel exists only on LOD0 before you generate meshes.

Unreal: FBX or glTF per studio; watch Nanite vs non-Nanite budgets. A bevel that looks cheap in Blender can still blow Nanite fallback or lightmap UVs — measure the asset you will cook.

CapEx four-liner (companies)

1. Risk of skip: Uncontrolled Mesh Bevel adoption after 5.2 raises tris, UV repair hours, and mid-demo hitch risk.
2. Destination cost: One lab evening + export smoke + optional LOD pass — still cheaper than a week of hero rebakes.
3. Avoided cost: Shipping a “bevel everything” pass without a receipt during art freeze.
4. Decision: LAB_ONLY / SHIP_PROP / HOLD_BEVEL / PIN_THEN_BEVEL — owner + date in Section A.

Discord paste (creators)

Blender 5.2 Mesh Bevel (Geometry Nodes) — lab prop only tonight.
Amount/segments + edge selection written. Gates B1–B8 before any ship mesh.
No remote-library enablement and no cloth XPBD on the same evening.
Receipt in #art. Live demo collection untouched.

Developer path — tech-art evening (after Section B)

Use this when you are past “does the node exist?” and need something CI can argue with.

Hour 0 — Inventory

1. Tag pre-mesh-bevel-YYYYMMDD on the art branch.
2. Record exact Blender build on every machine that can export ship art.
3. List props candidates: lab only tonight.
4. Write tris caps in Section C — no “looks fine.”

Hour 1 — Graph contract

1. Build the Mesh Bevel graph on PROP_bevel_lab.
2. Prefer a named edge attribute if the kit will repeat.
3. Capture before/after tris in the spreadsheet or a small Python snippet your studio already trusts.
4. Fill B3–B5.

Hour 2 — Export + engine

1. Export with studio defaults; compute hash.
2. Import in engine; one gameplay-camera orbit.
3. Fill B7–B8.
4. Only then discuss SHIP_PROP for a named prop set.

Honest limits for developers

• Mesh Bevel ≠ free detail — segments multiply cost; LODs must be planned.
• Attribute selection ≠ documented until the attribute name is in the receipt.
• 5.2 also shipped lists, bundles, experimental physics — stacking those nights with bevel night is how evenings die.
• Remote Asset Libraries are a different risk class — see the Stop and tools listicle; do not enable remote hosts “while we are in Blender anyway.”

Failure modes (and what to write)

Receipt JSON shape

{
  "receipt_type": "blender_5_2_mesh_bevel_gn_worksheet_v1",
  "filled_at": "2026-10-11",
  "product": "",
  "blender_build": "5.2.x",
  "decision": "LAB_ONLY",
  "prop_lab": "PROP_bevel_lab",
  "selection_method": "edge_attribute:bevel_edges",
  "amount": "",
  "segments": 2,
  "tris_before": 0,
  "tris_after": 0,
  "export_format": "gltf",
  "export_hash": "",
  "target_engine": "",
  "gates": {
    "B1_version": false,
    "B2_lab_only": false,
    "B3_selection": false,
    "B4_budget": false,
    "B5_shading": false,
    "B6_uvs": false,
    "B7_export": false,
    "B8_engine": false
  },
  "owner": "",
  "notes": ""
}

Copy the shape into your art ops folder. A screenshot of the node graph is optional evidence; the filled gates are mandatory.

Second evening — promote or hold (optional)

Only after LAB_ONLY receipt is green:

1. Pick one non-hero prop set (e.g. corridor panels).
2. Re-run B1–B8 on that set with the same amount/segments policy.
3. If any gate fails → HOLD_BEVEL for that set; do not half-promote.
4. Update CapEx with “promoted set name + date.”
5. Still keep heroes with custom bevel maps on a separate rebake sprint.

Common mistakes (studio edition)

Partner one-liner (copy/paste)

Blender 5.2 Mesh Bevel is under lab evaluation with written edge selection, tris caps, and engine import smoke; Steam-facing heroes stay on prior bevel/normal policy until receipt B1–B8 pass.

Key takeaways

1. Mesh Bevel in Geometry Nodes is real in Blender 5.2 — quote the GN release notes, not Discord memory.
2. This worksheet owns the first evening — not the 5.2 version pin and not remote libraries.
3. Pick a decision code — LAB_ONLY, SHIP_PROP, HOLD_BEVEL, or PIN_THEN_BEVEL.
4. Selection + amount + segments must be written — empty cells fail.
5. Gates B1–B8 gate any promote to ship props.
6. Export hash + engine smoke are part of the bevel evening, not a later chore.
7. Do not stack remote assets or experimental cloth on the same night.
8. Heroes with custom normals often HOLD — that is discipline, not fear.
9. CapEx four-liner makes the risk speakable to producers.
10. Receipt JSON is the artifact partners can ask for.
11. Beginners can finish a lab crate in about an hour with the beginner path.
12. Search intent for blender geometry nodes mesh bevel is a how-to + checklist gap — this URL is the fill-in answer.

FAQ

What is the Mesh Bevel node in Blender 5.2 Geometry Nodes?

It is the Geometry Nodes bevel operation called out in the 5.2 Geometry Nodes release notes as the long-awaited Mesh Bevel with control over edges or vertices. This worksheet is how indies adopt it without nuking ship props.

Is Mesh Bevel the same as the Bevel modifier?

Treat them as cousins, not twins. Measure amount, segments, selection, and export results on this node. Do not assume Edit Mode muscle memory transfers 1:1.

Do I need Blender 5.2 LTS specifically?

You need a 5.2.x build where Mesh Bevel exists. For studio pins, prefer the 5.2 LTS upgrade lock process so ship machines do not float.

Can I bevel the live Steam demo props tonight?

Only if Section B is SHIP_PROP and B1–B8 are green. If the demo is live, prefer PIN_THEN_BEVEL or LAB_ONLY.

How many segments should game props use?

Start at 1–3. Higher segments need an LOD story. Write the cap in Section C before you “make it pretty.”

What if UVs break after bevel?

Fail B6. Repair seams or HOLD and keep baked bevel maps. Do not ship shattered islands because the silhouette looked softer.

Should this evening include Remote Asset Libraries?

No. Use the Stop opinion and tools listicle on a different night.

What primary keyword does this page target?

blender geometry nodes mesh bevel — first indie worksheet with gates and receipt after Blender 5.2.

How does this help companies / diligence?

The CapEx four-liner + receipt JSON give producers a dated artifact: lab evaluation, tris caps, and engine smoke before hero promotion.

What if Mesh Bevel is missing from Add menu?

Confirm you are actually on 5.2.x. If the build is wrong, stop and fix version (B1). If the build is right and the node is missing, file a studio note and HOLD — do not invent a fake node group and call it Mesh Bevel.

Related reading

• Blender 5.2 LTS - What Indies Should Lock Before Upgrading Game Assets 2026 — version pin sibling
• Stop Enabling Blender Remote Asset Libraries Without Offline Plan - 2026 — remote offline refusal
• 12 Free Blender Remote Asset Library Tools After 5.2 LTS - 2026 — free remote toolkit
• Blender to Unity and Godot Export Pipeline - A Clean Art Handoff Checklist
• Your First Blender Hero glTF Export Hash - Q4 Diligence Mirror One Evening 2026
• How to Use AutoRemesher Free - First Indie Quad Retopo Evening 2026
• Blender Cloth Dynamics - First Indie Experimental Cape Keep Hold 2026 — different experimental night
• Procedural modeling with Geometry Nodes
• Blender Color Space Looks Wrong in Unity
• 25 Free Blender-to-Engine Workflow Resources

Primary sources: Blender 5.2 LTS press · Geometry Nodes - Blender 5.2 release notes · Blender 5.2 download notes.

Conclusion

Blender 5.2 finally puts Mesh Bevel in Geometry Nodes. The win for micro-studios is not a celebration post — it is a written lab evening: selection, amount, segments, UV honesty, export hash, and engine smoke before anyone bevels the demo.

Fill the worksheet. File the receipt. Keep heroes honest. Promote only when B1–B8 are boring.