Skip to content

Free, open-source 3D sculpting for Linux, macOS and Windows: dense meshes, remeshing, painting, built-in AI (image/text to 3D), Send to Unreal, game-ready LODs, Gaussian splats and OpenUSD.

32.3 KB
Raw Blame
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Exporting, Unreal and Bridge - SculptForge User Guide</title>
  <meta name="description" content="This chapter covers getting your sculpt out of SculptForge: the export formats and what each one keeps, LOD chains for games, sending a mesh straight into a running Unreal Editor, and exchanging models with another sculpting application through the Bridge. To keep everything (Parts, layers, mask, ve">
  <meta name="theme-color" content="#111114">
  <meta name="color-scheme" content="dark">
  <link rel="icon" type="image/png" sizes="32x32" href="../img/favicon-32.png?v=7">
  <link rel="icon" type="image/png" sizes="64x64" href="../img/favicon-64.png?v=7">
  <link rel="apple-touch-icon" href="../img/apple-touch-icon.png?v=7">
  <link rel="canonical" href="https://sculptforge.app/guide/exporting.html">
  <meta property="og:type" content="article">
  <meta property="og:title" content="Exporting, Unreal and Bridge - SculptForge User Guide">
  <meta property="og:description" content="This chapter covers getting your sculpt out of SculptForge: the export formats and what each one keeps, LOD chains for games, sending a mesh straight into a running Unreal Editor, and exchanging models with another sculpting application through the Bridge. To keep everything (Parts, layers, mask, ve">
  <meta property="og:image" content="https://sculptforge.app/img/social-preview.png?v=5">
  <meta property="og:url" content="https://sculptforge.app/guide/exporting.html">
  <link rel="stylesheet" href="../style.css?v=19">
  <script src="../motion.js?v=12" defer></script>
  <script data-goatcounter="https://sculptforge.goatcounter.com/count" async src="https://gc.zgo.at/count.js"></script>
  <script src="search-index.js?v=52" defer></script>
</head>
<body class="guide-page" data-prev="baking.html" data-next="export-presets.html">
  <div class="scroll-progress" aria-hidden="true"></div>
  <header class="nav">
    <div class="wrap nav-inner">
      <a class="brand" href="../index.html"><img class="brand-mark" src="../img/bust-mark-44.png" srcset="../img/bust-mark-88.png 2x, ../img/bust-mark-132.png 3x" width="44" height="44" alt=""><span>SculptForge</span></a>
      <nav aria-label="Main">
        <a href="../index.html#features">Features</a>
        <a href="../index.html#demos">Demos</a>
        <a href="../brushes.html">Brushes</a>
        <a href="index.html" aria-current="page">Guide</a>
        <a class="nav-dl" href="../index.html#download">Download</a>
        <a class="gh" href="https://discord.gg/gWrYkEmQhH">Discord</a>
        <a class="gh" href="https://github.com/islandmed/SculptForge">GitHub</a>
      </nav>
    </div>
  </header>
  <div class="wrap guide-layout">
    <div class="guide-side">
      <button class="toc-toggle" type="button" aria-expanded="false" aria-controls="guide-toc">
        <span>Contents</span><span class="toc-current">Exporting, Unreal and Bridge</span></button>
      <div id="guide-toc" class="toc-panel">
        <div class="guide-search" role="search">
          <input type="search" id="guide-q" placeholder="Search the guide" aria-label="Search the guide" autocomplete="off">
          <div class="search-results" id="guide-results" hidden></div>
        </div>
        <nav class="toc" aria-label="User guide"><a class="toc-home" href="index.html">Contents</a><p class="toc-group">Getting started</p><ul><li><a href="welcome.html">Welcome to SculptForge</a></li><li><a href="first-sculpt.html">Your first sculpt in 10 minutes</a></li><li><a href="whats-new.html">What&#x27;s new</a></li><li><a href="quick-tour.html">Quick tour for experienced sculptors</a></li><li><a href="installing.html">Install SculptForge on Windows, macOS and Linux</a></li><li><a href="interface.html">The interface</a></li><li><a href="navigation.html">Navigating the view</a></li></ul><p class="toc-group">Sculpting</p><ul><li><a href="sculpting.html">Sculpting and brushes</a></li><li><a href="brush-lab.html">Brush Lab and sharing brushes</a></li><li><a href="brush-packs.html">Brush packs</a></li><li><a href="masking.html">Masking</a></li><li><a href="face-groups.html">Face Groups and visibility</a></li><li><a href="selection-sets.html">Selection sets and morph targets</a></li><li><a href="parts.html">Parts</a></li><li><a href="linked-duplicates.html">Linked Duplicates</a></li><li><a href="forge-spheres.html">Forge Spheres</a></li><li><a href="tube.html">Tube: draw in 3D space</a></li><li><a href="vertex-paint.html">Vertex Paint and materials</a></li><li><a href="texture-painting.html">Texture painting</a></li><li><a href="uv-editor.html">UV Editor</a></li><li><a href="pbr-painting.html">Material painting (PBR)</a></li><li><a href="fill-layers.html">Fill layers, Mesh Maps and Material Recipes</a></li><li><a href="layers.html">Sculpt layers and blend shapes</a></li><li><a href="facial-shapes.html">Facial shapes and live face</a></li><li><a href="subdivision-levels.html">Subdivision levels</a></li><li><a href="micro-levels.html">Micro levels: hundreds of millions of polygons</a></li><li><a href="dynamic-topology.html">Dynamic topology</a></li><li><a href="timeline.html">Sculpt Timeline and timelapse</a></li><li><a href="gizmo.html">Moving, rotating and posing (Gizmo)</a></li><li><a href="geometry.html">Subdivide, remesh, decimate and LODs</a></li><li><a href="cut.html">Cut: line, lasso, rectangle and polyline</a></li><li><a href="retopology.html">Quad retopology and detail projection</a></li></ul><p class="toc-group">AI and capture</p><ul><li><a href="generate-3d.html">Image and text to 3D</a></li><li><a href="splats.html">Gaussian splats</a></li><li><a href="scan-to-splat.html">Scan an object into a splat</a></li><li><a href="scan-to-sculptable.html">From scan to sculptable mesh</a></li><li><a href="phone-capture.html">Phone capture and AR</a></li></ul><p class="toc-group">Files and pipelines</p><ul><li><a href="baking.html">Baking normal and displacement maps</a></li><li><a href="exporting.html" class="current" aria-current="page">Exporting, Unreal and Bridge</a><ul class="toc-sections"><li><a href="#export-formats-at-a-glance">Export formats at a glance</a></li><li><a href="#export-a-model">Export a model</a></li><li><a href="#3d-printing">3D printing</a></li><li><a href="#lod-chains-for-games">LOD chains for games</a></li><li><a href="#send-to-unreal">Send to Unreal</a></li><li><a href="#exchange-models-through-the-bridge">Exchange models through the Bridge</a></li><li><a href="#blender">Blender</a></li><li><a href="#maya">Maya</a></li><li><a href="#see-also">See also</a></li></ul></li><li><a href="export-presets.html">Export presets</a></li><li><a href="blender.html">Working with Blender</a></li><li><a href="maya.html">Working with Maya</a></li><li><a href="projects.html">Projects, autosave and snapshots</a></li><li><a href="scripting.html">Scripting and automation</a></li><li><a href="packs-and-macros.html">Packs and macros</a></li><li><a href="studios.html">SculptForge for studios</a></li><li><a href="security.html">Security overview for IT reviews</a></li></ul><p class="toc-group">Reference</p><ul><li><a href="shortcuts.html">Keyboard and mouse</a></li><li><a href="performance.html">Performance and big meshes</a></li><li><a href="troubleshooting.html">Troubleshooting: tablets, display, crashes and FAQ</a></li><li><a href="glossary.html">Glossary</a></li><li><a href="discord.html">Show SculptForge on Discord</a></li></ul></nav>
      </div>
    </div>
    <main class="guide-main" id="top">
      <article class="guide-article">
<h1 id="exporting-unreal-and-bridge">Exporting, Unreal and Bridge</h1>
<p>This chapter covers getting your sculpt out of SculptForge: the export formats and what each one keeps, LOD chains for games, sending a mesh straight into a running Unreal Editor, and exchanging models with another sculpting application through the Bridge. To keep everything (Parts, layers, mask, vertex paint, brushes) use a project file instead; see <a href="projects.html">Projects, autosave and snapshots</a>.</p>
<h2 id="export-formats-at-a-glance">Export formats at a glance<a class="anchor" href="#export-formats-at-a-glance" aria-label="Link to this section">#</a></h2>
<p>Exports write every <strong>visible</strong> Part. Hidden Parts are left out. Exporting doesn&#x27;t rename the document or mark it saved, so your next <kbd>Ctrl</kbd>+<kbd>S</kbd> still saves the project.</p>
<div class="table-wrap"><table><thead><tr><th>Format</th><th>Where in the app</th><th>Keeps</th><th>Use it for</th></tr></thead><tbody><tr><td>glTF binary (<code>.glb</code>)</td><td><strong>File &gt; Export GLB...</strong> (<kbd>Ctrl</kbd>+<kbd>E</kbd>)</td><td>One node per Part, sculpt layers as morph targets, vertex paint as vertex colour, UVs and the painted texture (embedded)</td><td>Games, Blender, three.js, web viewers</td></tr><tr><td>LOD chain (<code>.glb</code> per level)</td><td><strong>File &gt; Export LOD Chain...</strong></td><td>As GLB, one file per level, blend shapes on every level</td><td>Game engines</td></tr><tr><td>OpenUSD (<code>.usda</code>, <code>.usdz</code>)</td><td><strong>File &gt; Export USD / USDZ...</strong></td><td>One Mesh prim per Part, quads, layers as UsdSkel blend shapes, vertex paint as <code>displayColor</code>, UVs (<code>primvars:st</code>) and the painted texture through a preview material (inside a USDZ), loaded splats</td><td>Film pipelines, Omniverse, Apple AR Quick Look</td></tr><tr><td>FBX for Unreal (<code>.fbx</code>)</td><td><strong>File &gt; Export FBX for Unreal...</strong></td><td>Unreal naming and scale, quads, UVs, LOD group, layers as blend shapes, the painted texture as a PNG beside it</td><td>Unreal Engine (by hand)</td></tr><tr><td>Wavefront OBJ (<code>.obj</code>)</td><td><strong>File &gt; Export OBJ...</strong></td><td>One <code>o</code> object per Part, quads, face groups as <code>g</code> groups, vertex paint as vertex colour, UVs, the painted texture through a <code>.mtl</code> (<code>map_Kd</code>) and a PNG beside it. Layers are baked into the current blend</td><td>Any 3D app</td></tr><tr><td>Bridge file</td><td><strong>File &gt; Bridge &gt; Export Bridge file...</strong></td><td>Quads, face groups, mask, vertex paint, UVs, the painted texture as a PNG beside it</td><td>The <a href="#exchange-models-through-the-bridge">Bridge</a></td></tr><tr><td>STL (<code>.stl</code>)</td><td><strong>File &gt; Bridge &gt; Export STL...</strong></td><td>Geometry only (triangles), visible Parts merged, in millimetres with Z up</td><td><a href="#3d-printing">3D printing</a></td></tr><tr><td>PLY (<code>.ply</code>)</td><td><code>export_ply</code> command</td><td>Geometry, quads and vertex paint, visible Parts merged</td><td>Scan tools, MeshLab, Blender</td></tr><tr><td>FBX (general)</td><td><code>export_fbx</code> command</td><td>One model per Part, quads, UVs, blend shapes, optional LOD groups, the painted texture</td><td>Other FBX pipelines</td></tr></tbody></table></div>
<p>The GLB, LOD chain and FBX for Unreal exports are also in the <strong>Tool</strong> palette under <strong>Export</strong>, together with the LOD and Unreal settings.</p>
<p>&quot;Quads&quot; means the quads the model came in with (or got from Plane, Cube, Subdivide or Voxel Remesh) are written as quads, the rest as triangles; see <a href="geometry.html#quads-and-triangles">Quads and triangles</a>. glTF and STL can only hold triangles.</p>
<figure class="shot"><a href="images/export.jpg" class="zoom"><img src="images/export.jpg" alt="The Tool &gt; Export sub-palette with a generated LOD chain and the Unreal Engine settings" width="320" height="740" loading="lazy" decoding="async"></a><figcaption>The Tool &gt; Export sub-palette with a generated LOD chain and the Unreal Engine settings</figcaption></figure>
<p>UVs are kept through OBJ, FBX, USD, glTF and Bridge files, in and out. A Part with a painted <a href="texture-painting.html">texture</a> is exported with it: the PNG is written next to the file as <code>&lt;name&gt;_color.png</code> (<code>&lt;name&gt;_&lt;Part&gt;_color.png</code> with several Parts) and referenced by the model, or embedded in GLB and USDZ files. Spaces in the file name become <code>_</code> in the names of the files written beside it (<code>my scene.obj</code> gets <code>my_scene.mtl</code> and <code>my_scene_color.png</code>), because OBJ and MTL separate file names with spaces. <strong>Tool &gt; Texture Map &gt; Auto UV</strong> gives any sculpt UVs before export. Normal, displacement and other maps come from <a href="baking.html">Tool &gt; Bake</a> as separate image files.</p>
<p>Textured exports are checked against other tools, not only read back by SculptForge: GLB files pass the Khronos glTF validator with no errors or warnings; USD and USDZ files pass OpenUSD&#x27;s validators (the USDZ files are uncompressed, 64-byte aligned and have the root layer first); FBX files load in ufbx&#x27;s strict mode with their textures connected; and in all four formats plus OBJ, the texture is sampled the right way up (each format&#x27;s UV convention), checked colour by colour against SculptForge&#x27;s own sampling. The scripts are in <code>tools/export_check/</code> in the source tree.</p>
<h3 id="scale-and-axes">Scale and axes<a class="anchor" href="#scale-and-axes" aria-label="Link to this section">#</a></h3>
<ul>
<li>
glTF, USD and OBJ are written Y-up with 1 unit = 1 metre, the same space you sculpt in.
</li>
<li>
FBX uses centimetres: <code>export_fbx</code> multiplies positions by 100 by default (<code>scale=</code>), so 1 unit = 1 m.
</li>
<li>
STL is written in millimetres with Z up, as slicers expect: a 0.3 m sculpt prints 300 mm tall, standing upright. <code>export_stl height_mm=80</code> scales it to a print height instead (see <a href="#3d-printing">3D printing</a>). Opening an STL converts back, so a downloaded print model comes in upright and at its real size. STL files from SculptForge 0.5 and earlier (metres, Y up) are recognised and open as they were saved.
</li>
<li>
PLY keeps positions as they are (no unit conversion).
</li>
<li>
USD files in other units (<code>metersPerUnit</code>, e.g. centimetres from Maya or Houdini) open at their real size.
</li>
<li>
For Unreal, <strong>Height</strong> sets the real-world size directly (see below).
</li>
</ul>
<h3 id="real-world-size-and-units">Real-world size and units<a class="anchor" href="#real-world-size-and-units" aria-label="Link to this section">#</a></h3>
<p>A part keeps the size it was opened with through every export:</p>
<ul>
<li>
OBJ, PLY and STL have no units. A scene opened from one of them remembers its unit: exporting OBJ or PLY writes that unit back (an STL opened in millimetres exports a 50 mm OBJ, not 0.05), and an STL written from an STL keeps its numbers. Decimal sizes come back exactly (12.7 stays 12.7). Projects remember the unit.
</li>
<li>
<strong>Edit &gt; Preferences &gt; Interface &gt; OBJ/PLY in</strong> says what OBJ and PLY numbers mean: <strong>m</strong> (the default; Blender and game tools), or <strong>mm</strong> for files made for 3D printing, <strong>cm</strong> or <strong>in</strong>. STL is always read as millimetres. From scripts: <code>open path=part.obj unit=mm</code> (<code>open_obj</code> and <code>part_append</code> take <code>unit=</code> too; <code>unit=in</code> reads an inch STL).
</li>
<li>
<strong>Edit &gt; Preferences &gt; Interface &gt; Units</strong> picks the unit sizes show in: mm, cm, m or in. The active Part&#x27;s width x height x depth shows under its name in <strong>Tool</strong>, the size the exports write in <strong>File</strong> (Import / Export), and the brush size by the brush ring.
</li>
</ul>
<h2 id="export-a-model">Export a model<a class="anchor" href="#export-a-model" aria-label="Link to this section">#</a></h2>
<ol>
<li>
Show the Parts you want to export and hide the others (the eye icon in <strong>Tool &gt; Parts</strong>).
</li>
<li>
Choose the export in the <strong>File</strong> palette and pick a file name.
</li>
<li>
The status line confirms the export (&quot;Exported ...&quot;).
</li>
</ol>
<p>A Part with <a href="subdivision-levels.html">subdivision levels</a> is exported at the level you are on. To write the base cage (or any other level) without stepping to it, use <code>subdiv_export path=base.obj level=1</code>.</p>
<p>From a script, each format is one command:</p>
<div class="code-block"><pre class="code"><code class="language-sh">sculptforge-cli -c &#x27;open path=bust.sfproj; export_glb path=bust.glb&#x27;
sculptforge-cli -c &#x27;open path=bust.sfproj; export_usd path=bust.usdz&#x27;
sculptforge-cli -c &#x27;open path=bust.sfproj; save_obj path=bust.obj&#x27;
sculptforge-cli -c &#x27;open path=bust.sfproj; export_fbx path=bust.fbx lods=3 ratio=0.5&#x27;
sculptforge-cli -c &#x27;open path=bust.sfproj; export_stl path=bust.stl; export_ply path=bust.ply&#x27;</code></pre><button class="copy" type="button" aria-label="Copy">Copy</button></div>
<h2 id="3d-printing">3D printing<a class="anchor" href="#3d-printing" aria-label="Link to this section">#</a></h2>
<p><strong>File &gt; Bridge &gt; Export STL...</strong> writes every visible Part as one binary STL, ready for a slicer (PrusaSlicer, Cura, Bambu Studio, OrcaSlicer ...). The status line gives the printed size, for example &quot;Exported lion.stl (47214 triangles, 320.8 x 206.6 x 436.4 mm)&quot;: width, depth and height as the slicer shows them.</p>
<ul>
<li>
<strong>Size:</strong> 1 unit in SculptForge is 1 m, so 1 unit becomes 1000 mm. To print at a given height, use <code>export_stl path=lion.stl height_mm=80</code>, or scale the model in the slicer.
</li>
<li>
<strong>One solid:</strong> overlapping Parts go into the file as they are, which some slicers and print services reject. <strong>Merge visible</strong> them (<a href="parts.html#merge-parts">Parts</a>) and <a href="geometry.html#voxel-remesh">Remesh</a> to turn them into one closed surface first.
</li>
<li>
<strong>Detail:</strong> printers resolve about 0.05-0.1 mm, so millions of triangles rarely help. <a href="geometry.html#decimate">Decimate</a> makes the file smaller without visible loss.
</li>
</ul>
<div class="code-block"><pre class="code"><code class="language-sh">sculptforge-cli -c &#x27;open path=bust.sfproj; export_stl path=bust.stl height_mm=120&#x27;
sculptforge-cli -c &#x27;open path=bust.sfproj; export_stl path=bust.stl scale=1 z_up=false&#x27;   # sculpt space as it is</code></pre><button class="copy" type="button" aria-label="Copy">Copy</button></div>
<h2 id="lod-chains-for-games">LOD chains for games<a class="anchor" href="#lod-chains-for-games" aria-label="Link to this section">#</a></h2>
<p>A LOD (level of detail) chain is the same model at decreasing triangle counts, so an engine can draw distant objects cheaply. SculptForge builds it with quadric decimation, keeping blend shapes on every level.</p>
<ol>
<li>
Open <strong>Tool &gt; Export</strong>.
</li>
<li>
Set <strong>LODs</strong> (2 to 6 levels, including LOD0) and <strong>Reduction</strong> (0.1 to 0.9: the triangle ratio from one level to the next, default 0.5).
</li>
<li>
Click <strong>Generate LOD chain</strong>. A table lists each level with its triangle count and its share of LOD0.
</li>
<li>
Click a level (<strong>LOD0</strong>, <strong>LOD1</strong> ...) to inspect it in the viewport; the wireframe turns on. Click <strong>Sculpt</strong> to go back to the editable mesh.
</li>
<li>
Export with <strong>LOD chain (GLB per level)</strong>, or send it to Unreal (below). Changing the sliders clears the preview; click <strong>Generate LOD chain</strong> to build it again.
</li>
</ol>
<p>The LOD chain export writes <code>&lt;name&gt;_LOD0.glb</code>, <code>&lt;name&gt;_LOD1.glb</code> and so on next to the path you choose. With several visible Parts, each Part is decimated on its own.</p>
<div class="code-block"><pre class="code"><code class="language-sh">sculptforge-cli -c &#x27;open path=rock.obj; export_lods path=out/rock.glb levels=4 ratio=0.5&#x27;</code></pre><button class="copy" type="button" aria-label="Copy">Copy</button></div>
<p>To reduce the sculpt itself instead of exporting copies, use <strong>Tool &gt; Geometry &gt; Decimate</strong>; see <a href="geometry.html">Subdivide, Remesh, Decimate and LODs</a>.</p>
<h2 id="send-to-unreal">Send to Unreal<a class="anchor" href="#send-to-unreal" aria-label="Link to this section">#</a></h2>
<p><strong>Send to Unreal</strong> exports an Unreal-ready FBX and imports it into a running Unreal Editor (5.x) on this computer or another one on your network. Nothing is installed into your project: it uses Unreal&#x27;s built-in Python remote execution.</p>
<div class="table-wrap"><table><thead><tr><th>Your sculpt</th><th>What arrives in Unreal</th></tr></thead><tbody><tr><td>No sculpt layers</td><td>A <strong>static mesh</strong> <code>SM_&lt;Name&gt;</code> with the LOD chain from <strong>Tool &gt; Export</strong></td></tr><tr><td>Sculpt layers</td><td>A <strong>skeletal mesh</strong> <code>SK_&lt;Name&gt;</code> with one <strong>morph target</strong> per layer (Unreal adds a single root bone)</td></tr><tr><td>Several visible Parts</td><td>One FBX model per Part, combined into one asset on import</td></tr><tr><td>Any</td><td>A material slot <code>M_Clay</code>, and the real-world size from <strong>Height</strong></td></tr><tr><td>A baked normal map (<a href="baking.html">Tool &gt; Bake</a>)</td><td>The texture <code>T_&lt;Name&gt;_N</code>, set up as a normal map (Unreal on this computer only)</td></tr><tr><td>A texture with <a href="pbr-painting.html">material channels</a></td><td><code>T_&lt;Name&gt;_BC</code>, <code>T_&lt;Name&gt;_N</code> (DirectX) and <code>T_&lt;Name&gt;_ORM</code> (occlusion, roughness, metallic), plus <code>T_&lt;Name&gt;_E</code> when emissive is painted, and a material <code>M_&lt;Name&gt;</code> built from them and assigned to the mesh (Unreal on this computer only; see <a href="export-presets.html">Export presets</a>)</td></tr></tbody></table></div>
<p>Sending the same asset again updates it in place (same name and folder), so references in your levels stay intact.</p>
<h3 id="one-time-setup-in-unreal">One-time setup in Unreal<a class="anchor" href="#one-time-setup-in-unreal" aria-label="Link to this section">#</a></h3>
<ol>
<li>
<strong>Edit &gt; Plugins</strong>: enable <strong>Python Editor Script Plugin</strong>, then restart the editor.
</li>
<li>
<strong>Edit &gt; Project Settings &gt; Plugins &gt; Python</strong>: tick <strong>Enable Remote Execution?</strong>.
</li>
</ol>
<p>That&#x27;s all when Unreal runs on the same computer.</p>
<h3 id="send">Send<a class="anchor" href="#send" aria-label="Link to this section">#</a></h3>
<ol>
<li>
Open <strong>Tool &gt; Export</strong> and find the <strong>Unreal Engine</strong> section.
</li>
<li>
Set <strong>Folder</strong> (the content folder, default <code>/Game/SculptForge</code>) and <strong>Height</strong> (the model&#x27;s height in Unreal, in centimetres; it starts at the model&#x27;s current height with 1 unit = 1 m).
</li>
<li>
For a static mesh, set <strong>LODs</strong> and <strong>Reduction</strong> above (default 4 levels).
</li>
<li>
Click <strong>Send to Unreal</strong>, or press <kbd>Ctrl</kbd>+<kbd>U</kbd>. The status line reports the result.
</li>
</ol>
<p>The line under the buttons tells you what will be sent: &quot;Static mesh with 4 LODs&quot; or &quot;Skeletal mesh with 2 morph targets&quot;.</p>
<h3 id="unreal-on-another-computer">Unreal on another computer<a class="anchor" href="#unreal-on-another-computer" aria-label="Link to this section">#</a></h3>
<ol>
<li>
On the Unreal machine, in <strong>Project Settings &gt; Plugins &gt; Python</strong>, open <strong>Advanced</strong> and set <strong>Multicast Time-To-Live</strong> to <code>1</code> and <strong>Multicast Bind Address</strong> to <code>0.0.0.0</code>.
</li>
<li>
In SculptForge, tick <strong>Unreal is on another computer</strong>.
</li>
<li>
Both computers must be on the same network, and the SculptForge computer&#x27;s firewall must allow incoming connections from the Unreal machine: the editor connects back to SculptForge to fetch the file.
</li>
</ol>
<h3 id="import-by-hand">Import by hand<a class="anchor" href="#import-by-hand" aria-label="Link to this section">#</a></h3>
<p><strong>Export FBX for Unreal...</strong> (in the <strong>File</strong> palette and in <strong>Tool &gt; Export</strong>) writes the same file. The file name becomes the asset name. Drag it into the Content Browser: static meshes pick up their LODs from the file&#x27;s LOD group; for skeletal meshes choose <strong>Skeletal Mesh</strong> and tick <strong>Import Morph Targets</strong>.</p>
<h3 id="from-scripts">From scripts<a class="anchor" href="#from-scripts" aria-label="Link to this section">#</a></h3>
<div class="code-block"><pre class="code"><code class="language-sh">sculptforge-cli -c &#x27;open path=statue.obj; unreal_send destination=/Game/Props height_cm=200 lods=4&#x27;
sculptforge-cli -c &#x27;unreal_editors network=true&#x27;                  # list editors on the network
sculptforge-cli -c &#x27;open path=statue.obj; export_unreal folder=out height_cm=200&#x27;</code></pre><button class="copy" type="button" aria-label="Copy">Copy</button></div>
<p><code>unreal_send</code> also takes <code>name=</code>, <code>project=</code> (pick one editor when several are open) and <code>network=true</code>.</p>
<aside class="callout callout-note"><p><strong>Note:</strong> Layered sculpts are sent as skeletal meshes without the LOD chain, because Unreal&#x27;s morph targets need a skeletal mesh (Unreal can generate skeletal LODs itself). The Unreal link has been tested against a stand-in editor that speaks the same protocol but not yet against every Unreal version. If an import fails, Unreal&#x27;s <strong>Output Log</strong> shows the importer&#x27;s messages.</p></aside>
<h2 id="exchange-models-through-the-bridge">Exchange models through the Bridge<a class="anchor" href="#exchange-models-through-the-bridge" aria-label="Link to this section">#</a></h2>
<p>The <strong>Bridge</strong> exchanges Parts with another sculpting application through a shared bridge folder, the way that application&#x27;s own exchange plug-in does, on Windows and macOS. The commands are in <strong>File &gt; Bridge</strong>:</p>
<div class="table-wrap"><table><thead><tr><th>Item</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Send</strong></td><td>Writes every visible Part to the bridge folder and tells the other application (starting it if needed). Each Part arrives as its own object. Turns on <strong>Receive automatically</strong></td></tr><tr><td><strong>Receive</strong></td><td>Loads what the other application last sent. Each object updates the Part it was sent from (one undo step), or becomes a new Part</td></tr><tr><td><strong>Receive automatically</strong></td><td>Checks once a second for a new send and receives it</td></tr><tr><td><strong>Custom bridge folder (optional)</strong></td><td>Use another bridge folder, for example inside a Wine prefix</td></tr><tr><td><strong>Import Bridge file...</strong></td><td>Opens a Bridge file, replacing the scene</td></tr><tr><td><strong>Export Bridge file...</strong></td><td>Writes a Bridge file. With several visible Parts, one file per Part next to the path</td></tr><tr><td><strong>Export STL...</strong></td><td>Writes a binary STL of the visible Parts</td></tr></tbody></table></div>
<p>On Windows and macOS the Bridge finds the shared exchange folder by itself; nothing to install. On Linux it needs a custom folder; Bridge files still import and export.</p>
<h3 id="a-round-trip">A round trip<a class="anchor" href="#a-round-trip" aria-label="Link to this section">#</a></h3>
<ol>
<li>
In SculptForge, choose <strong>File &gt; Bridge &gt; Send</strong>. The other application starts or comes forward with the Parts. If it was not running and does not import them, use its own import from the bridge.
</li>
<li>
Work there, then send the model back with its exchange plug-in.
</li>
<li>
SculptForge receives it automatically and updates the matching Parts. Each update is an undo step on that Part.
</li>
</ol>
<p>The Bridge keeps face groups, mask, vertex paint and UVs. Quads stay quads both ways: Wire shows them as quads. The format has no hidden-face flag, so hidden faces are sent like any others.</p>
<aside class="callout callout-note"><p><strong>Note:</strong> the Bridge is tested with files, not yet against every version of a live application. If a send does not arrive, export a Bridge file and import it by hand, and please report it (<strong>Help &gt; Report a problem</strong>).</p></aside>
<p>From scripts: <code>bridge_export path=</code>, <code>bridge_import path=</code>, <code>bridge_send</code>, <code>bridge_receive</code> and <code>export_stl path=</code> (see <a href="#3d-printing">3D printing</a> for its options).</p>
<h2 id="blender">Blender<a class="anchor" href="#blender" aria-label="Link to this section">#</a></h2>
<p>To sculpt Blender objects in SculptForge and send them back into the same objects, use the SculptForge Bridge add-on and <strong>File &gt; Blender</strong>: see <a href="blender.html">Working with Blender</a>. For a one-off exchange, OBJ, FBX and glTF all carry Parts, UVs and quads both ways.</p>
<h2 id="maya">Maya<a class="anchor" href="#maya" aria-label="Link to this section">#</a></h2>
<p>To sculpt Maya meshes in SculptForge and send them back into the same objects, use the SculptForge shelf for Maya and <strong>File &gt; Maya</strong>: see <a href="maya.html">Working with Maya</a>.</p>
<h2 id="see-also">See also<a class="anchor" href="#see-also" aria-label="Link to this section">#</a></h2>
<ul>
<li>
<a href="blender.html">Working with Blender</a>: the Blender add-on
</li>
<li>
<a href="maya.html">Working with Maya</a>: the Maya shelf script
</li>
<li>
<a href="projects.html">Projects, autosave and snapshots</a>: save everything, not just the mesh
</li>
<li>
<a href="parts.html">Parts</a>: which Parts are exported
</li>
<li>
<a href="layers.html">Layers and blend shapes</a>: what becomes morph targets
</li>
<li>
<a href="geometry.html">Subdivide, Remesh, Decimate and LODs</a>: decimate before exporting
</li>
<li>
<a href="splats.html">Gaussian splats</a>: saving splats
</li>
<li>
<a href="studios.html">For studios</a>: formats in a pipeline
</li>
</ul>
      </article>
      <nav class="pager" aria-label="Previous and next chapter"><a class="prev" rel="prev" href="baking.html"><span>Previous</span>Baking normal and displacement maps</a><a class="next" rel="next" href="export-presets.html"><span>Next</span>Export presets</a></nav>
      <p class="guide-meta fine">Also in the app: <strong>Help &gt; User Guide</strong> (<kbd>Shift</kbd>+<kbd>F1</kbd>).
        Found a mistake? <a href="https://github.com/islandmed/SculptForge/edit/main/docs/guide/exporting.md">Edit this page on GitHub</a>.</p>
    </main>
    <aside class="on-page" aria-label="On this page"><p>On this page</p><ul><li><a href="#export-formats-at-a-glance">Export formats at a glance</a></li><li><a href="#export-a-model">Export a model</a></li><li><a href="#3d-printing">3D printing</a></li><li><a href="#lod-chains-for-games">LOD chains for games</a></li><li><a href="#send-to-unreal">Send to Unreal</a></li><li><a href="#exchange-models-through-the-bridge">Exchange models through the Bridge</a></li><li><a href="#blender">Blender</a></li><li><a href="#maya">Maya</a></li><li><a href="#see-also">See also</a></li></ul></aside>
  </div>
  <footer class="footer">
    <div class="wrap footer-grid">
      <div>
        <a class="brand" href="../index.html"><img class="brand-mark" src="../img/bust-mark-44.png" srcset="../img/bust-mark-88.png 2x, ../img/bust-mark-132.png 3x" width="32" height="32" alt=""><span>SculptForge</span></a>
        <p class="fine">Copyright © 2026 The SculptForge contributors.<br>The SculptForge User Guide is part of
          SculptForge, licensed under the <a href="https://github.com/islandmed/SculptForge/blob/main/LICENSE">GNU GPL v3.0 or later</a>.</p>
      </div>
      <div class="links">
        <a href="../performance/">Performance</a>
        <a href="index.html">User guide</a>
        <a href="../supporters.html">Members</a>
        <a href="https://github.com/islandmed/SculptForge">Source code</a>
        <a href="https://discord.gg/gWrYkEmQhH">Community Discord</a>
        <a href="https://github.com/islandmed/SculptForge/issues">Report a problem</a>
        <a href="https://github.com/islandmed/SculptForge/blob/main/docs/ai-services.md">AI services &amp; privacy</a>
      </div>
      <p class="fine trademarks">SculptForge is an independent project. Product names are trademarks of their respective owners.</p>
    </div>
  </footer>
</body>
</html>