Automating Godot 4 GLB Asset Pipelines: Vertex Pivot Grounding, Colliders, Occluders & MeshLibrary Baking
Importing a handful of 3D hero models into Godot 4 is straightforward. Importing 150 modular .glb / .gltf pieces from Kenney, Quaternius, Synty, KayKit, or Blender into a clean level-building workflow is where teams quietly lose entire weekends.
When you drop raw .glb packs into res://, four production bottlenecks show up immediately:
- Off-origin / floating pivots: Asset packs routinely export modular walls with origin corners offset along X/Z or floating +0.5m to +0.65m above Y = 0.
- Manual Advanced Import clicking: Configuring Trimesh vs. Convex collision shapes, physics layers/masks, shadow-casting flags, and
OccluderInstance3Dacross dozens of.glbfiles one by one does not scale. - The GridMap / MeshLibrary Trap: Moving
MeshInstance3D.positioninside a wrapper scene does not move the mesh inside aMeshLibrary. GridMap reads raw mesh vertex coordinates. - Fragile Inherited Scenes: Editing inherited
.tscnscenes by hand works until someone re-exports the.glbfrom Blender and silently breaks node overrides or duplicates surface material paths.
While building MeshForge 4 (and testing every stage headlessly on Godot Engine 4.7.2-stable), we solved these with a declarative .glb -> .tscn + MeshLibrary pipeline. Here is the engineering breakdown of every non-obvious Godot 4 gotcha we hit along the way.
Why Node-Offset Grounding Fails for GridMap
The naive approach to fixing a wall whose bounding-box min_y sits at +0.65m is to set mesh_instance.position.y = -0.65. That looks fine when you instance the .tscn manually, until you export a MeshLibrary for GridMap:
# MeshLibrary reads the underlying Mesh resource's local vertices,
# NOT the wrapper MeshInstance3D transform inside your source scene!
mesh_lib.set_item_mesh(item_id, baked_array_mesh)
If you only shifted the node transform, every tile painted in GridMap still floats +0.65m off the cell origin or sits misaligned half a tile off the X/Z grid.
To make both standalone .tscn prefabs and GridMap MeshLibrary tiles snap deterministically to Y = 0.00m and center cleanly on X/Z, shift the geometry directly in ArrayMesh vertex space:
static func bake_vertex_pivot(src_mesh: Mesh, snap_y_zero: bool, center_xz: bool) -> ArrayMesh:
var aabb := src_mesh.get_aabb()
var offset := Vector3.ZERO
if center_xz:
offset.x = -(aabb.position.x + aabb.size.x * 0.5)
offset.z = -(aabb.position.z + aabb.size.z * 0.5)
if snap_y_zero:
offset.y = -aabb.position.y
var out := ArrayMesh.new()
for s in range(src_mesh.get_surface_count()):
var arrays := src_mesh.surface_get_arrays(s)
var verts: PackedVector3Array = arrays[Mesh.ARRAY_VERTEX]
for i in range(verts.size()):
verts[i] += offset
arrays[Mesh.ARRAY_VERTEX] = verts
var prim := src_mesh.surface_get_primitive_type(s)
out.add_surface_from_arrays(prim, arrays)
var mat := src_mesh.surface_get_material(s)
if mat:
out.surface_set_material(s, mat)
return out
Wait - remember one critical second step if you bake static walls or props: once vertices shift by offset, generate collision shapes from the baked ArrayMesh, not the original GLB mesh:
match collider_type:
"trimesh":
shape_node.shape = baked_mesh.create_trimesh_shape()
"convex":
shape_node.shape = baked_mesh.create_convex_shape(true, true)
In our Godot 4.7.2 verification suite, a test fixture wall_modular_01.glb exported with min_y = +0.650m and asymmetric X/Z bounds bakes deterministically to min_y = 0.00000m and AABB center (0.0, 1.575, 0.0) in both the .tscn prefab and the generated MeshLibrary item.
The Silent PackedScene.pack() Bug
If you build .tscn prefabs from an @tool EditorPlugin script, adding child nodes with parent.add_child(child) looks correct in memory - until you reload the saved .tscn and discover your StaticBody3D and CollisionShape3D vanished completely.
PackedScene.pack(root) only serializes descendants whose .owner == root:
static func _set_owner_recursive(node: Node, owner_root: Node) -> void:
for child in node.get_children():
child.owner = owner_root
_set_owner_recursive(child, owner_root)
Even better: when generating a standalone .tscn prefab, construct a fresh clean root (Node3D) carrying your baked MeshInstance3D, optional StaticBody3D / CollisionShape3D, and optional OccluderInstance3D - rather than saving an inherited scene wrapper tied back to the raw .glb hierarchy. Re-baking becomes repeatable and diffable in Git.
Declarative Glob Rules Over Hand-Tuned Folders
Rather than forcing artists to sort assets into rigid sub-directories, a rule table ordered by priority works well across mixed kits (walls, floors, crates, multi-mesh prop sheets, foliage):
*wall*, *floor*- Trimesh, Layer 1, ArrayOccluder3D, Shadow Cast ON, Split Multi-Mesh false, MeshLibrary true*prop*, *crate*, *barrel*- Convex, Layer 2, Occluder false, Shadow Cast ON, Split Multi-Mesh false, MeshLibrary true*kit*, *sheet*- Convex, Layer 2, Occluder false, Shadow Cast ON, Split Multi-Mesh true, MeshLibrary true*foliage*, *pine*- None, 0, Occluder false, Shadow Cast OFF, Split Multi-Mesh false, MeshLibrary false
Two high-leverage additions pay off immediately in studio workflows:
- Multi-Mesh GLB Kit Splitting: When
*kit*, *sheet*matches a single.glbcontaining 4 sub-meshes (Crate_Small,Pillar_Broken,Lantern_Post,Bench_Wood), extract eachMeshInstance3Dindependently, center and Y=0 ground-snap each piece in vertex space, and write 4 clean single-asset.tscnfiles plus 4 MeshLibrary tiles. - Non-Destructive
.glb.importReimport Hook Binding: Instead of asking artists to click into Import settings on 100 GLBs, patch[params] import_script/pathvia Godot'sConfigFileinside a tracked rollback manifest (.meshforge_manifest.json). When a.glbis updated from Blender, Godot invokes yourEditorScenePostImporthook automatically - while keeping a 1-click Dry-Run & Rollback safety net.
Try the Free MIT Auditor or Full Pro Pipeline
We split this workflow into two cleanly separated packages tested end-to-end on Godot Engine 4.7.2-stable:
- Free & MIT Open Source - MeshForge 4 Lite (GitHub Repo & v1.0.0 Release):
- Recursive
.glb/.gltffolder auditor (mesh count, triangles, material slots, floating pivot min_y warnings, missing collider flags) - Single-rule batch collider prefab generator (Trimesh / Convex / Box + custom physics layer & mask -> clean
.tscnprefabs) - Configured with
.gitattributesso Asset Library / release archives package onlyaddons/meshforge_lite/
- Recursive
- Full Production Pipeline - MeshForge 4 Pro ($11.99 Launch Week - 20% OFF regular $14.99, with Free Lite [demo] downloadable on the same page):
- Multi-rule Glob Priority Engine + 4 studio presets (Kenney / Quaternius / Synty / Blender Architecture)
- Dry-Run non-mutating preview +
.meshforge_manifest.json1-click rollback - True ArrayMesh vertex-space Y=0 ground-snap + X/Z centering
- Multi-mesh GLB kit splitter (4 sub-meshes -> 4 centered
.tscnprefabs) - External shared
.tresmaster material slot remapper & automatic ArrayOccluder3D extraction - Deterministic GridMap MeshLibrary compiler &
.glb.importpost-import hook binder - Complete runnable Godot 4.7.2 Demo Project (6
.glbfixtures, PBR master.tresshaders, Before/After showcase scene, and 22-assertion headless test suite)
Questions or edge cases in your own .glb pipeline (skeletal animations, compound box hulls, or Blender material naming conventions)? Drop a comment below or open an issue on GitHub - real pipeline pain points are driving our v1.1 roadmap.
Comments
No comments yet. Start the discussion.