Looma · Desktop app for Windows

The atelier for wrinkle maps.

Looma takes a garment from a skinned FBX to a finished, consistent set of wrinkle maps. Simulation, wrap, bake, paint, sculpt and blend preview share one viewport, one scene file and one undo history.

Native C++ / QtWindows x64English · Русский
Looma
9workspaces, from pose library to export
3built-in cloth solvers, on CPU or GPU
2bake methods: raycast and surface projection
0extra applications — no Maya, no Python
Workspaces

Nine benches. One garment on the table.

Each workspace is a bench for one job. The garment stays in the shared viewport while you move between them, and nothing you've done is lost on the way.

Start from what you already have.

Bring the garment as a skinned FBX, the body it is worn on, and — if your rig has them — the Pose Wrangler RBF correctives. Looma reads the skeleton, weights and animation takes directly.

  • One scene file.A .looma scene keeps poses, zones, settings and camera together.
  • Sources stay untouched.FBX files are referenced and fingerprinted, so a changed source never slips in unnoticed.
1
Cloth FBXskin weights · skeleton · takes
✓
2
Body FBXcollision for the simulation
✓
3
RBF JSONPose Wrangler · optional
✓
+
Pose set from Unrealfrom the analyzer · optional
✓
From simulation to map

Every fold the cloth made, kept.

A wrinkle map is just colours until light falls on it. Drag across to see a map as the folds it holds — one T-shirt pattern, five poses.

Lit relief of the selected pose's wrinkle map The selected pose's wrinkle normal map Normal map Lit relief
Assistants & automation

Ask for a bake. Find it in Unreal.

Turn on MCP in Looma and an assistant such as Claude or Codex can read your scene, prepare a bake, check it, start it and deliver the result to your Unreal project — while you keep working.

  • Nothing starts unchecked.A bake runs only after every listed check has passed.
  • You stay in charge.Jobs appear in Looma's Bake workspace with their settings and a Cancel button.
  • Never overwrites.Results always go to new folders; your sources are read-only.
Example session · assistant + Looma MCP
Bake "Arms up" from the new sculpt and send it to Unreal. looma_list_assets receiver → current mesh looma_prepare_bake raycast · 2048 px looma_validate_bake all checks passed looma_start_bake job running inside Looma looma_get_job done · normal map published looma_send_to_unreal → your project's inbox unreal_get_receipt imported The new map is in the project and the pose uses it.
Specifications

What goes in, what comes out.

Looma is in active development; this is what the current build does.

PlatformWindows x64. Native C++ and Qt — no Maya, no Python needed.
InterfaceEnglish and Русский
Garment inSkinned FBX (linear or rigid skin), OBJ
Also inBody FBX · Pose Wrangler RBF JSON · pose sets from the Unreal analyzer
SimulationBuilt-in cloth solvers · CPU and GPU · pause, resume, live grab · collider clips for external simulators
BakeRaycast · surface projection · DirectX or OpenGL green
Maps outPNG or TGA normal maps · packed pairs (RG + BA)
Also outOBJ / FBX surface snapshots in any pose · .looma scenes
AutomationMCP server for assistants · command-line runs for checks · delivery to Unreal projects with the runtime

See Looma on your own garment.

Send us a skinned garment and a few animations. We'll take it from FBX to maps with you, live.