Docs

Modeling mode

In-app Babylon studio: chat writes mesh code, a live viewport updates, you inspect parts, then export GLB. Not the Unreal viewport.

Last updated 19 September 2026

What you are looking at

Dola Modeling mode with a bamboo mesh in the Babylon viewport, Scene Explorer, Properties, and a chat that used execute_babylon_code — Bamboo example: chat → execute_babylon_code → inspect_scene on the live viewport → GLB export. This is not Unreal Editor.

Modeling mode is a Babylon.js studio inside the desktop app. A modeling specialist writes JavaScript for @babylonjs/core via execute_babylon_code. The live viewport, Scene Explorer, and Properties pane update on your machine. When the inspect is clean, the scene exports to GLB.

The loop

Switch to Modeling in the title bar (Ctrl+Shift+M).
Ask for a specific object. The agent should author named parts with real proportions.
It inspects the live scene. Empty, off-camera, or overlapping-origin results should be redone or marked incomplete — not dressed up as finished.
Colour / PBR stays on the Babylon mesh (model-materials), not Unreal MI_* assets.
Export GLB from the studio. Publishing into Unreal is a later, separate step.

What this is not

It is not the Unreal viewport, not a StaticMesh author inside /Game/Geometry, and not a hosted text-to-3D farm. Game-dev Blueprints and C++ stay on the Unreal plugin path. See Game-dev vs Modeling · Agent roster · Blog note.