Skip to content
PN Scripts

Blender add-ons

Hullcrate

by PN Scripts

Export every object or collection of a Blender scene to its own GLB, glTF, FBX or OBJ file in one click, and let a budget gate stop LODs that break their triangle budget, ladder order or size before they reach your engine.

  • Blender
  • Python
  • glTF 2.0
  • FBX
  • OBJ
  • Coming soon

Coming soon

Not published on its store yet, so there is no buy or download link. PN Scripts does not take payment for it here.

Blender add-ons
Blender 5.2 screenshot with the Hullcrate sidebar tab, the file name preview, the export results and the report text

What it solves

The gap

Exporting a set of props or modular pieces from one .blend file means selecting, moving to the origin, exporting and naming each piece by hand, and doing it again after every change.

What it is

Hullcrate plans the files from your collections and object names, moves each export to its origin, writes them with Blender's own exporters and tells you what it wrote and how many triangles each file has.

How you use it

One click replaces a repeated manual export routine, and the presets and templates make the result the same every time.

For game artists and developers who keep many assets in one .blend file and need repeatable exports to an engine.

Who it is for

Use it when

  • Exporting a kit of modular level pieces to separate GLB files for Godot or a web viewer
  • Sending LOD chains of props to a game engine as FBX files with consistent names
  • Blocking a build when a LOD was subdivided by mistake or exported at the wrong scale, before the files reach Unity, Godot or Unreal

Built for

  • Game artists who build many assets in one Blender file
  • Indie developers who move assets from Blender to Unity, Godot or Unreal often

What is inside

From scene to files, report and presets

Pick a folder, a format and whether to split by object or by collection. Hullcrate collects the selected, visible or all geometry objects, plans one file per object or collection and writes them with Blender's own exporters. Collections can export only their direct objects or, at the top level, everything nested in them. A dry run shows the planned files with triangle and vertex counts; after an export, the same table goes to a Blender text block and to hullcrate_report.json and hullcrate_report.csv with file sizes, and presets keep whole export setups inside the .blend file.

Names, folders and LODs

The name template decides file names and folders, for example {collection}/{name}_{lod}. LOD suffixes like _LOD0 or .lod2 are split from the name, and the LOD mode decides whether LODs become separate files, one file per asset or only the first LOD. Illegal characters are replaced and duplicate names get a number and a warning.

Origins and transforms

Each export can keep its world position, move the object origin to world zero (the instance offset for collections) or put the bottom centre of its bounds on zero. Apply transforms bakes rotation and scale into the vertices so the exported object has an identity transform. The original objects are never moved; Hullcrate works on temporary copies.

Budget gate

Choose Off, Report or Block failing files. Set a triangle limit per file, a limit per LOD such as LOD0=5000, LOD1=2500, a material limit, the largest share of the previous LOD a LOD may keep and how far a LOD's size may drift from LOD0. Hullcrate measures every file first, because a LOD ladder spans several files, then writes the files that pass. Each problem is named in the panel, the report text and the JSON and CSV files. Warnings (a LOD that keeps too many triangles, a size drift, a missing UV map) never block; failures (over budget, a LOD with no fewer triangles than the one before) block in Block mode.

Specs

Availability
Coming soon
Vendor
PN Scripts
Type
Extension
Platforms
Blender
Pricing
One-time purchase Price to be announced.
Deployment
Download (Blender extension ZIP)
Maturity
v1.2.0

Compatibility

Platform or runtime Supported versions Tested up to
Blender 4.2 or newer 5.2.2

Stack

  • Blender
  • Python
  • glTF 2.0
  • FBX
  • OBJ

Hullcrate is coming soon

It is finished and tested. It is not on sale yet; this page will say where to get it when it is.

Coming soon

Not published on its store yet, so there is no buy or download link. PN Scripts does not take payment for it here.

Questions

A Blender extension that exports each object or collection of a scene to its own GLB, glTF, FBX or OBJ file, named from a template, with LOD detection, origin options, presets and a dry run. A budget gate checks triangles per file and per LOD, materials, meshes without UVs and whole LOD ladders (fewer triangles at every step, a maximum share of the previous LOD, no missing LOD number, no size drift against LOD0) before anything is written; Report mode lists problems, Block mode also skips the failing files.

Blender 4.2 or newer. It was tested on Blender 5.2.2 LTS on Linux. No other add-ons are needed.

Armatures, skinning, animation, lights and cameras are not exported, and object hierarchies are flattened to world transforms. It is meant for static meshes.

It was written in Python against Blender's API, and 50 automated tests export a generated scene in all four formats, re-import the files and compare triangle counts, transforms and bounds. Created with AI assistance; the exports were checked by PN Scripts with automated export and re-import tests in Blender 5.2.2 and an install test of the built zip.

It is not on sale yet. When it is, this page will link to the store; PN Scripts does not take payment on this site.