arjun988/blender-skills / .claude/skills/unreal-export
unreal-export
VerifiedUnreal Engine-specific Blender export for FBX scale, LODs, UCX collision, sockets, materials, and skeletal mesh workflows via MCP.
Unreal Export
UE-ready FBX. Correct centimeter scale awareness. UCX collision. LOD and socket naming.
When to Use
- Static mesh or skeletal mesh to Unreal
- UCX/UCLX collision export
- LOD chain import
- Socket / pivot setup for gameplay
Pre-Flight
asset-optimizationPASSlod-pipelinefor LOD0–Ncollision-proxyfor UCX meshes- Apply scale; pivots at intended UE origin
Scale Note
Unreal is centimeter-based. Common approaches:
- Model in meters in Blender, export FBX with unit conversion / 0.01 awareness per project pipeline
- Or work to project-documented scale and verify with a 100cm reference
Always measure a known edge after import.
FBX Defaults (Static)
Selected Objects
Apply Scalings: FBX All
Forward: -Z Forward
Up: Y Up
Mesh: ON
Smoothing: Face
Naming for UE
| Type | Pattern |
|---|---|
| Static mesh | SM_Name |
| Skeletal | SK_Name |
| Skeleton | SKEL_Name |
| LOD | SM_Name_LOD0 … |
| Collision | UCX_SM_Name_01 |
| Socket empty | SOCKET_Name |
Collision
- Prefer convex UCX pieces over complex mesh colliders
- Multiple UCX meshes supported
- See
collision-proxy
Skeletal
- UE mannequin-oriented proportions when required
- Root bone; no leftover Blender deform leftovers
- Export morph targets if needed (shape keys)
Verify in Unreal
- Scale (door ~200cm, character ~180cm)
- Collision wireframe
- LODs auto-detected
- Materials / texture sampling
- Sockets transform
Constraints
MUST DO
- Confirm scale with known-dimension test
- Prefix collision with
UCX_ - Validate LODs and materials after import
MUST NOT DO
- Export without collision plan for physics actors
- Mix unit systems undocumented
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Unreal Checklist | references/unreal-checklist.md | When needed |
| Ucx Naming | references/ucx-naming.md | When needed |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |