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.

35.4 KB
Raw Blame
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Performance and big meshes - SculptForge User Guide</title>
  <meta name="description" content="SculptForge is built to sculpt tens of millions of polygons. Brushes, normal updates and the picking structure run on every core of your processor, a stroke sends the graphics card only the part of the mesh it changed, and undo stores only the vertices a stroke touched, so it stays quick however big">
  <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/performance.html">
  <meta property="og:type" content="article">
  <meta property="og:title" content="Performance and big meshes - SculptForge User Guide">
  <meta property="og:description" content="SculptForge is built to sculpt tens of millions of polygons. Brushes, normal updates and the picking structure run on every core of your processor, a stroke sends the graphics card only the part of the mesh it changed, and undo stores only the vertices a stroke touched, so it stays quick however big">
  <meta property="og:image" content="https://sculptforge.app/img/social-preview.png?v=5">
  <meta property="og:url" content="https://sculptforge.app/guide/performance.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="shortcuts.html" data-next="troubleshooting.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">Performance and big meshes</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">Exporting, Unreal and Bridge</a></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" class="current" aria-current="page">Performance and big meshes</a><ul class="toc-sections"><li><a href="#what-to-expect">What to expect</a></li><li><a href="#edit--preferences--performance">Edit &gt; Preferences &gt; Performance</a></li><li><a href="#your-hardware-tier">Your hardware tier</a></li><li><a href="#the-hardware-profile">The hardware profile</a></li><li><a href="#working-with-big-meshes">Working with big meshes</a></li><li><a href="#dynamic-topology">Dynamic topology</a></li><li><a href="#proof-mode-see-it-for-yourself">Proof mode: see it for yourself</a></li><li><a href="#measuring-your-own-machine">Measuring your own machine</a></li><li><a href="#see-also">See also</a></li></ul></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="performance-and-big-meshes">Performance and big meshes</h1>
<p>SculptForge is built to sculpt tens of millions of polygons. Brushes, normal updates and the picking structure run on every core of your processor, a stroke sends the graphics card only the part of the mesh it changed, and undo stores only the vertices a stroke touched, so it stays quick however big the model is. This chapter explains what to expect, the settings in <strong>Edit &gt; Preferences &gt; Performance</strong>, and how to get the most out of a big sculpt.</p>
<p>What we&#x27;re building next, and how each piece works: <a href="https://sculptforge.app/performance/" rel="noopener">Performance: what we&#x27;re building</a>.</p>
<figure class="shot"><a href="images/performance-panel.jpg" class="zoom"><img src="images/performance-panel.jpg" alt="Edit &gt; Preferences &gt; Performance after a stroke: antialiasing, Fast Navigation, multithreading, what the stroke cost per dab, and memory" width="535" height="780" loading="lazy" decoding="async"></a><figcaption>Edit &gt; Preferences &gt; Performance after a stroke: antialiasing, Fast Navigation, multithreading, what the stroke cost per dab, and memory</figcaption></figure>
<h2 id="what-to-expect">What to expect<a class="anchor" href="#what-to-expect" aria-label="Link to this section">#</a></h2>
<p>On a 2021 laptop (Apple M1 Pro, 10 cores, integrated GPU), with X symmetry on and a medium Size:</p>
<div class="table-wrap"><table><thead><tr><th>Mesh</th><th>One dab of a medium brush</th><th>Turning the view</th></tr></thead><tbody><tr><td>4 million triangles</td><td>about 2 ms</td><td>about 350 frames a second</td></tr><tr><td>16 million triangles</td><td>about 4.5 ms</td><td>about 170 frames a second</td></tr><tr><td>33 million triangles</td><td>about 7.5 ms</td><td>about 110 (4x antialiasing), 270 with Fast Navigation</td></tr></tbody></table></div>
<p>Turning the view stays smooth at 100 million triangles: about 50 frames a second with 4x antialiasing, 100 with Fast Navigation. These figures are for closed models (no holes); see &quot;Closed meshes draw faster&quot; below.</p>
<p>A dab is one step of the brush along the stroke; the app draws several per frame when you move fast. Under 16 ms per dab a stroke keeps up with a 60 Hz display. Very large brushes cost more, since they move more vertices: a brush covering a tenth of a 33 million triangle sphere (about a million vertices per dab with symmetry) takes about 45 ms per dab with Standard, 21 ms with Smooth and 15 ms with Move, of which sending the change to the graphics card is about a third.</p>
<p><a href="https://github.com/islandmed/SculptForge/blob/main/docs/performance.md" rel="noopener">Performance figures</a> has the full measurements, and how to run the same benchmark on your own machine.</p>
<h2 id="edit--preferences--performance">Edit &gt; Preferences &gt; Performance<a class="anchor" href="#edit--preferences--performance" aria-label="Link to this section">#</a></h2>
<p>Open <strong>Preferences</strong> and click <strong>Performance</strong>.</p>
<div class="table-wrap"><table><thead><tr><th>Control</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Antialiasing</strong> (Off, 2x, 4x, 8x)</td><td>How many samples per pixel the 3D view uses to smooth edges. 4x is the default. More samples look smoother and cost more on huge meshes. If the graphics card can&#x27;t make room for them, the view quietly uses fewer and the panel says so</td></tr><tr><td><strong>View resolution</strong> (100%, 75%, 50%)</td><td>Draws the 3D view at a share of the window&#x27;s resolution and scales it up: 75% draws about half the pixels and 50% a quarter. Try it on slow or integrated graphics and big screens. <strong>Save Render</strong> always renders at full resolution. Also in <strong>View</strong></td></tr><tr><td><strong>Fast Navigation</strong></td><td>While you rotate, pan or zoom a scene bigger than the hardware profile&#x27;s motion proxy threshold (see below), draw it without antialiasing and draw big meshes as a lighter version with about a fifth of their triangles, so the view keeps up. The full mesh, smooth again, is back as soon as the view stops. On by default</td></tr><tr><td><strong>Predictive Strokes</strong></td><td>The brush is worked out on its own thread while the view keeps drawing at full speed. The dabs it hasn&#x27;t finished show at once as a preview on the surface, and the brush cursor and the stroke&#x27;s head are drawn where the pen is about to be, so on a heavy mesh the surface moves under the pen straight away and lifting the pen never waits. The finished sculpt is exactly the same as with it off. On by default (painting, masking, dynamic topology, Move, Tendril and the drag strokes work as before)</td></tr><tr><td><strong>Draft Strokes</strong></td><td>With Predictive Strokes: while you sculpt, the brush only moves the surface, the moved part is shaded from its facets, and the smooth shading, the cavities and the rest are worked out once when you lift the pen. Lighter on laptops and on battery. Inflate and the plane brushes use the surface&#x27;s direction from the stroke&#x27;s start, so the result can differ slightly from a full stroke. Off by default</td></tr><tr><td><strong>Live Move</strong> (experimental)</td><td>The Move brush&#x27;s drag is drawn by the graphics card from where the surface started, so it follows the pen at the view&#x27;s frame rate on any mesh size; the move is applied once, exactly, when you lift the pen. Not with masks, hidden parts, sculpt layers, micro levels, Connected Only or View falloff (Move works as before there). Off by default</td></tr><tr><td><strong>Background Preview</strong> (experimental)</td><td>On meshes of 2 million vertices or more a big brush is worked out on its own thread; with this on, the dabs still being worked out show as a preview under the pen. The finished sculpt is exactly the same either way. Off by default</td></tr><tr><td><strong>Fast Upload</strong> (experimental)</td><td>While you sculpt, the changed part of the mesh goes to the graphics card through memory both can see and the card copies it into place, instead of the driver copying it during the frame. The sculpt and the view are exactly the same either way. Needs OpenGL 4.4 buffer storage (otherwise it does nothing). Off by default</td></tr><tr><td><strong>Multithreading</strong></td><td>Run brushes, normal and picking updates and project saving on every core (the number of threads is shown beside it). The results are exactly the same with it off; turn it off only to compare speeds or rule it out when something goes wrong</td></tr><tr><td><strong>Last stroke</strong></td><td>What your last stroke cost per dab: <strong>Brush</strong> (finding and moving the vertices), <strong>Normals</strong> (shading), <strong>BVH</strong> (the structure that finds the surface under the cursor), and the <strong>GPU upload</strong> per frame</td></tr><tr><td><strong>Memory</strong></td><td>What the scene holds: the meshes, the BVHs, the subdivision levels kept for stepping between them, the undo history (up to 1 GB; the oldest steps are dropped beyond that) and, roughly, the graphics card&#x27;s buffers</td></tr></tbody></table></div>
<h2 id="your-hardware-tier">Your hardware tier<a class="anchor" href="#your-hardware-tier" aria-label="Link to this section">#</a></h2>
<p>On top of the profile below, SculptForge sorts your computer into a <strong>tier</strong>, so the bigger features switch on by themselves where your machine can carry them, and never where it can&#x27;t. Every tier sculpts smoothly: the higher ones give more room for detail.</p>
<div class="table-wrap"><table><thead><tr><th>Tier</th><th>For</th><th>What it adds</th></tr></thead><tbody><tr><td><strong>Essential</strong></td><td>every computer SculptForge runs on</td><td>settings tuned for the machine; Focus Detail keeps 512 MB of full-resolution detail close by</td></tr><tr><td><strong>Standard</strong></td><td>16 GB of memory, 6 or more threads and a 4 GB graphics card (or graphics that share the memory)</td><td>twice the Focus Detail memory, streamed in faster</td></tr><tr><td><strong>High</strong></td><td>32 GB, 8 or more threads and an 8 GB graphics card (or 32 GB shared, such as an Apple Pro or Max)</td><td>2 GB of Focus Detail, 16K paint and bake textures</td></tr><tr><td><strong>Extreme</strong></td><td>64 GB, 16 or more threads and a 16 GB graphics card (or 64 GB shared)</td><td>4 GB of Focus Detail, the most of everything</td></tr></tbody></table></div>
<p>A graphics card or processor that measures slow keeps a lower tier, whatever its memory says.</p>
<p>The first time SculptForge starts (and when you change the graphics card or the memory), a small card in the corner of the 3D view says what it found, for example <em>Your machine: RTX 3060, 12 GB VRAM, 32 GB RAM. Tier: High</em>, and what that turns on. Click <strong>Got it</strong>; it doesn&#x27;t show again on this computer. The tier is also in the top bar, next to the bolt: click it to open <strong>Edit &gt; Preferences &gt; Performance</strong>.</p>
<p>There, at the top:</p>
<div class="table-wrap"><table><thead><tr><th>Control</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Tier</strong></td><td>your machine, its tier, what the next tier would need, and <strong>What this turns on</strong></td></tr><tr><td>Auto / each tier</td><td>choose the tier yourself. A tier above the detected one is allowed; the memory guard still watches it</td></tr><tr><td><strong>Turbo</strong></td><td>the same switch as the bolt (below)</td></tr><tr><td><strong>Graphics card</strong></td><td>on a computer with two (a laptop&#x27;s built-in and gaming graphics, or two cards): which one draws SculptForge. <strong>Auto</strong> takes the fastest one. It applies the next time SculptForge starts; if that card can&#x27;t start, SculptForge goes back to the system&#x27;s choice and says so</td></tr><tr><td><strong>Compute</strong></td><td><strong>Auto</strong>, <strong>CPU</strong> or <strong>GPU</strong> for the heavy work. Each task shows where it runs; the ones that have no graphics card version yet say <em>CPU only for now</em>. Auto uses the graphics card only where it measured faster, and never on the Essential tier</td></tr></tbody></table></div>
<p><strong>Free memory is watched.</strong> If your computer runs low on memory while you work (another program, a huge scene), SculptForge steps the tier down one level and says so in the status bar; detail streams in a little later and nothing is lost. When there is room again for a minute, it steps back up.</p>
<h3 id="turbo">Turbo<a class="anchor" href="#turbo" aria-label="Link to this section">#</a></h3>
<p>The small bolt in the top bar (also <strong>View &gt; Turbo</strong>, <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>T</kbd>) gives everything your computer can safely spare to sculpting speed: while you sculpt or orbit, the view draws without antialiasing and with a lighter version of big scenes, and the tier&#x27;s top budgets apply. The moment you stop, the view is back at full quality. It turns orange while on, and a line in the status bar says what it changed. Turn it off and every setting is exactly as you left it. SculptForge remembers it on this computer.</p>
<h2 id="the-hardware-profile">The hardware profile<a class="anchor" href="#the-hardware-profile" aria-label="Link to this section">#</a></h2>
<p>The first time you start SculptForge, a small window says <strong>Getting to know this computer</strong> for a second or two: it checks how fast your graphics card draws and receives data, how fast a brush runs and how fast the memory is, and picks settings to match. It does this once, and again only when you change the graphics card, update its driver or install a new version. Press <kbd>Esc</kbd> or <strong>Skip</strong> to skip it; the settings then come from the type of graphics card and the memory sizes. Nothing is sent anywhere: the results stay in your settings folder.</p>
<p>There are two main profiles and a safe mode:</p>
<div class="table-wrap"><table><thead><tr><th>Profile</th><th>For</th><th>What changes</th></tr></thead><tbody><tr><td><strong>Laptop / Budget</strong></td><td>laptops and most desktops: 8-32 GB of memory, a 2-8 GB graphics card, most Apple Silicon Macs</td><td>a moderate number of triangles drawn while the view moves; brushes shade continuously on mains power</td></tr><tr><td><strong>Workstation</strong></td><td>64 GB of memory or more, and a graphics card with 16 GB or more or an Apple Silicon Max / Ultra (or another chip whose graphics share the memory) that measures as fast</td><td>more triangles drawn per frame, larger textures and subdivision limits, shading updated with every dab</td></tr><tr><td><strong>Software</strong> (safe mode)</td><td>no graphics driver, so the drawing happens on the processor (llvmpipe)</td><td>the lightest settings, no antialiasing</td></tr></tbody></table></div>
<p>On a laptop running on battery, whatever its profile, SculptForge sends less data to the graphics card per frame and aims for 60 frames a second, and the status bar says so; plugged in again, it goes back.</p>
<p>At the top of <strong>Edit &gt; Preferences &gt; Performance</strong>:</p>
<div class="table-wrap"><table><thead><tr><th>Control</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Detected ...</strong></td><td>the graphics card, its memory and the profile, and why</td></tr><tr><td>Measured numbers</td><td>triangles drawn per second, upload speed, the cost of a brush dab, memory speed, the processor and the system</td></tr><tr><td>Settings</td><td>how many triangles the view draws per frame, from what size big scenes use their lighter version while moving, memory and upload budgets, texture and subdivision limits, threads, the target frame rate (60, or 120 / 144 on a fast display)</td></tr><tr><td><strong>Frame Governor</strong></td><td>while the view moves, watch how long frames take and draw big scenes&#x27; lighter version sooner or later to hold the target frame rate. It only changes what you see while moving, never the model. On by default</td></tr><tr><td><strong>Re-calibrate</strong></td><td>measure again (your overrides are kept)</td></tr><tr><td><strong>Manual overrides</strong></td><td>choose the profile yourself, or set any of the numbers (empty = automatic); <strong>Back to automatic</strong> clears them. Overrides are saved at once and kept when you re-calibrate</td></tr></tbody></table></div>
<p>From a shell, <code>sculptforge --calibrate</code> measures and prints the result as JSON.</p>
<p>Like the other preferences, these save themselves for the next start. Every setting is also in the <kbd>F3</kbd> command palette (type &quot;antialiasing&quot;, &quot;fast navigation&quot; or &quot;multithreading&quot;).</p>
<h2 id="working-with-big-meshes">Working with big meshes<a class="anchor" href="#working-with-big-meshes" aria-label="Link to this section">#</a></h2>
<ul>
<li>
<strong>Sculpt at the lowest level that holds the detail.</strong> With <a href="subdivision-levels.html">subdivision levels</a> you can shape the forms a few levels down and only go to the top for fine detail. Each level down is four times lighter.
</li>
<li>
<strong>Hide what you&#x27;re not working on.</strong> Hidden Parts aren&#x27;t drawn and hidden parts of a Part aren&#x27;t sculpted (<strong>Tool &gt; Visibility</strong>). A hidden Part costs no drawing time at all.
</li>
<li>
<strong>Memory.</strong> A divided model takes about 85 bytes per triangle: about 37 for the sculpting mesh, 17 for its BVH and 29 for its subdivision levels. A 33 million triangle sculpt with levels needs about 3.4 GB of memory, a 100 million one about 9 GB (and a little more while dividing). Opening a project needs only a little more than the model itself. A mesh without levels (an import, a remesh) takes about 60 bytes per triangle for the mesh. Project files over 4 GB are saved in the ZIP64 format.
</li>
<li>
<strong>How far Add Level goes</strong> depends on the memory: about 160 million triangles on a computer with 32 GB.
</li>
<li>
<strong>The graphics card.</strong> A mesh needs about 15 bytes per triangle on the graphics card (vertex paint and a mask add about 3; the wireframe, while it is on, about 4; the lighter version Fast Navigation draws, once you move the view, about 1.5). If a Part doesn&#x27;t fit, SculptForge doesn&#x27;t draw it and says so in the status bar instead of failing: hide other Parts or step down a subdivision level.
</li>
<li>
<strong>Closed meshes draw faster.</strong> Parts of a mesh that face away from you are skipped when the mesh is closed (no holes or hidden parts) and you look at it from outside. A mesh with holes, hidden polygons, or a view from inside it draws everything, which can take about twice as long on huge meshes. <strong>Tool &gt; Display &gt; Backface culling</strong> (#68, off by default) skips the back faces of any mesh, open or closed, from any view: an open scan seen from behind then draws almost nothing (8M triangles: 3.1 ms down to 0.7 ms a frame), and you see through its openings. Brushes then work only on the faces drawn.
</li>
<li>
<strong>Undo</strong> keeps only what each stroke changed, so a stroke on a 33 million triangle mesh undoes in a few tens of milliseconds, and the history holds many such strokes within its 1 GB.
</li>
</ul>
<h2 id="dynamic-topology">Dynamic topology<a class="anchor" href="#dynamic-topology" aria-label="Link to this section">#</a></h2>
<p><a href="dynamic-topology.html">Dynamic topology</a> only works where the brush is, so its speed depends on how many triangles the brush covers rather than on the size of the mesh: on an M1 Pro a medium dab takes 9 to 13 milliseconds on a one-million-triangle sphere. It gets slower when a big brush (or a low Detail) has to merge many small triangles at once; it then spreads the work over several dabs. Undoing a stroke rebuilds the mesh&#x27;s connections, which takes about a tenth of a second per million triangles. <code>sculptforge --bench --bench-dyntopo</code> measures it on your machine.</p>
<h2 id="proof-mode-see-it-for-yourself">Proof mode: see it for yourself<a class="anchor" href="#proof-mode-see-it-for-yourself" aria-label="Link to this section">#</a></h2>
<p><strong>Help &gt; Benchmark</strong> (or <code>sculptforge --benchmark standard-15m</code>) shows how responsive sculpting is on your own computer, measured the way it feels rather than the way a developer measures it. Its <strong>standard scenes</strong> are the ones the <a href="https://sculptforge.app/benchmarks/" rel="noopener">benchmarks page</a> lists: a procedural head of 15 million (<code>standard-15m</code>) or 33 million (<code>standard-33m</code>) triangles, the same on every computer, sculpted with a fixed stroke set: Clay at 25, 60 and 120 pixels, Move, Smooth and a 240-pixel brush, then a turn of the view (<code>standard</code> runs both sizes). Each reports frame time (p50, p95, p99), how far the stroke trails the pointer in pixels, the worst stall (the longest the screen froze), and peak memory and graphics memory.</p>
<p>Without a scene name (<code>sculptforge --benchmark</code>, or <strong>Spheres</strong> in the dialog) it runs the older size sweep: for each size, 5, 20 and 33 million triangles (and 100 million when there is enough free memory), it builds a sphere with subdivision levels, then plays a scripted pen stroke into the same code your mouse and pen go through, 240 pointer samples a second: a figure eight with a 60-pixel brush, the same with a 240-pixel brush, then a turn of the view. It replaces the scene, so save your work first; <kbd>Esc</kbd> stops it.</p>
<p>While it runs, a panel in the corner shows:</p>
<ul>
<li>
<strong>fps</strong> and the <strong>frame time</strong>: the median (p50), and the 95th and 99th percentile, the slow frames you would notice as a hitch.
</li>
<li>
<strong>Stroke trails pointer</strong>: how far the stroke on screen is behind the pointer, in milliseconds (from the pointer sample the newest drawn dab belongs to until that frame is handed to the display; the display&#x27;s own refresh comes on top) and in pixels along the path.
</li>
<li>
The memory SculptForge uses.
</li>
</ul>
<p>Vertical sync is off during the run so frame times aren&#x27;t capped at the display&#x27;s rate (tick <strong>Keep vertical sync on</strong> to measure with it). At the end a table sums up each mesh and phase, and two files are written: a video of the run with the panel in it (needs <a href="https://ffmpeg.org/" rel="noopener">ffmpeg</a>; recording costs a millisecond or two per frame) and a JSON file with the results, your processor, graphics card, memory, operating system and the SculptForge version and commit. In the app they go to the <code>benchmarks</code> folder in SculptForge&#x27;s settings folder (<strong>Open folder</strong> in the results); from the command line, to the current folder:</p>
<div class="code-block"><pre class="code"><code>sculptforge --benchmark standard-15m --benchmark-out mine.json --benchmark-video mine.mp4
sculptforge --benchmark --benchmark-sizes 5,20,33 --benchmark-out spheres.json</code></pre><button class="copy" type="button" aria-label="Copy">Copy</button></div>
<p><code>--benchmark-no-video</code> skips the video, <code>--benchmark-vsync</code> keeps vertical sync on, <code>--benchmark-seconds 6</code> sets the length of each stroke, and <code>--size 1920x1080</code> the window (a tiling window manager may choose another size; the result records the one used). Share a result on the <a href="https://sculptforge.app/benchmarks/" rel="noopener">benchmarks page</a> as its <a href="https://github.com/islandmed/SculptForge/blob/main/docs/benchmark.md" rel="noopener">format description</a> explains.</p>
<h2 id="measuring-your-own-machine">Measuring your own machine<a class="anchor" href="#measuring-your-own-machine" aria-label="Link to this section">#</a></h2>
<p><code>sculptforge --bench</code> builds a sphere at 4, 16 and 32 million triangles and measures every brush, undo, stepping subdivision levels, saving and opening a project, and turning the view, then prints a report. <code>sculptforge-cli --bench</code> measures the same without the graphics card. Options:</p>
<div class="table-wrap"><table><thead><tr><th>Option</th><th>What it does</th></tr></thead><tbody><tr><td><code>--bench-sizes 4,16,32</code></td><td>The sizes, in millions of triangles</td></tr><tr><td><code>--bench-dabs 40</code></td><td>Dabs per test stroke</td></tr><tr><td><code>--bench-brushes large</code></td><td>Only the brushes whose name contains the text (here the large-radius ones)</td></tr><tr><td><code>--bench-no-project</code></td><td>Skip saving and opening the project (which needs twice the memory)</td></tr><tr><td><code>--bench-view</code></td><td>Measure only what the view costs: uploading to the graphics card, a few strokes, and turning the view</td></tr><tr><td><code>--bench-out report.md</code></td><td>Write the report to a file</td></tr></tbody></table></div>
<p>When nothing changes, SculptForge draws nothing: the graphics card and processor rest until you move the mouse, press a key, or something finishes in the background. <code>sculptforge --measure-idle 5</code> sits idle for five seconds (after a short start) and prints the frames drawn and the processor time used. If the view ever stops updating when it should (a driver that misbehaves), start SculptForge with the environment variable <code>SF_CONTINUOUS_REDRAW=1</code> to draw every frame as versions before 0.9.5 did, and please <a href="troubleshooting.html#report-a-problem">report it</a>; <code>SF_REDRAW_LOG=1</code> logs why each frame was drawn.</p>
<p>On a very dense mesh a dab can cost more than a frame. The dabs of a stroke then wait in a queue that SculptForge works through for a few milliseconds each frame, reading the pen or mouse in between, so a fast curve stays a curve; once more than about 50 ms of dabs are waiting, every second waiting dab is left out (a wider spacing), so the brush stays close to the pointer and stops soon after you lift the pen. <code>sculptforge --run &quot;new_sphere&quot; --measure-stroke 3,200</code> draws a fast circle for three seconds with a 200-pixel brush and prints how far the dabs strayed from it and the frame times. <code>SF_STROKE_IMMEDIATE=1</code> places every dab as soon as the pointer moves (versions before 0.9.6), <code>SF_STROKE_BACKLOG=0</code> never leaves dabs out, and <code>SF_STROKE_LOG=1</code> logs the queue each frame (with Predictive Strokes, each batch the brush thread places and what packing it for the graphics card cost). <code>SF_PREDICTIVE_STROKE=0</code> / <code>1</code> and <code>SF_DRAFT_STROKE=0</code> / <code>1</code> override the two preferences, and <code>SF_FRAME_LOG=16</code> logs every frame slower than 16 ms with where its time went. <code>tools/bench_strokes.sh</code> in the source runs the stroke measurement on 5, 21 and 33 million triangle spheres and prints the frame times (mean, 95th and 99th percentile), how far the surface and the preview trail the pointer, press and release, for one build or two side by side.</p>
<p>The <code>perf_info</code> command (also in the <a href="scripting.html">Console</a>) prints the threads in use and the memory the scene holds; <code>set_multithreading enabled=false</code> turns multithreading off from a script.</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="subdivision-levels.html">Subdivision levels</a>
</li>
<li>
<a href="troubleshooting.html">Troubleshooting and FAQ</a>
</li>
<li>
<a href="glossary.html">Glossary</a>
</li>
</ul>
      </article>
      <nav class="pager" aria-label="Previous and next chapter"><a class="prev" rel="prev" href="shortcuts.html"><span>Previous</span>Keyboard and mouse</a><a class="next" rel="next" href="troubleshooting.html"><span>Next</span>Troubleshooting: tablets, display, crashes and FAQ</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/performance.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="#what-to-expect">What to expect</a></li><li><a href="#edit--preferences--performance">Edit &gt; Preferences &gt; Performance</a></li><li><a href="#your-hardware-tier">Your hardware tier</a></li><li><a href="#the-hardware-profile">The hardware profile</a></li><li><a href="#working-with-big-meshes">Working with big meshes</a></li><li><a href="#dynamic-topology">Dynamic topology</a></li><li><a href="#proof-mode-see-it-for-yourself">Proof mode: see it for yourself</a></li><li><a href="#measuring-your-own-machine">Measuring your own machine</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>