- Substance 3D home
- Home
- Getting Started
- Getting Started overview
- Activation and licenses
- System requirements
- Project creation
- Export
- Export overview
- Export window
- Output templates
- Export overview
- Glossary
- Performance
- Getting Started overview
- Interface
- Assets
- Substance 3D Assets
- Color picker
- Display settings
- History
- Layer stack
- Main menu
- Project configuration
- Properties
- Settings
- Shader settings
- Texture Set
- Toolbars
- Viewport
- Miscellaneous
- Assets
- Painting
- Painting overview
- Tool list
- Straight line
- Lazy mouse
- Symmetry
- Fill projections
- Presets
- Presets overview
- Creating and saving presets
- Creating particles presets
- Photoshop brush presets (ABR)
- Dynamic strokes
- Advanced channel painting
- Vector graphic (.svg & .ai)
- Text resource
- Effects
- Baking
- Content
- Creating custom effects
- Importing assets
- Creating custom effects
- Features
- Automatic resource update
- Automatic UV Unwrapping
- Physical size
- Smart Materials and Masks
- Subsurface Scattering
- Dynamic Material Layering
- UV Reprojection
- UV Tiles
- Color Management
- Post Processing
- Iray Renderer
- Plugins
- Sparse Virtual Textures
- Custom Shaders
- SpaceMouse® by 3Dconnexion
- Universal Scene Description (USD)
- Send to
- Technical Support
- Performance Guidelines
- Configuring Pens and Tablets
- Exporting the log file
- Exporting a DXDiag
- Technical issues
- GPU Issues
- Crash when working with overclocked GPU
- Forcing the external GPU on Mac OS
- GPU drivers compatibility
- GPU drivers crash with long computations (TDR crash)
- GPU has outdated drivers
- GPU is not recognized
- GPU is not recognized and is mentionned as GDI Generic
- Issues with Nvidia GPUs on recent Mac OS versions
- Multi/Bi-GPU
- Running on integrated GPU
- Painter doesn't start on the right GPU
- Startup Issues
- Rendering Issues
- Stability Issues
- Miscellaneous Issues
- GPU Issues
- Workflow Issues
- Export Issues
- Tools Issues
- Project Issues
- Library Issues
- Viewport Issues
- Plugins Issues
- License Issues
- Pipeline and integration
- Installation and preferences
- Configuration
- Resource management
- Scripting and development
- Scripts and plugins
- Shader API Reference
- Shader API overview
- Changelog - Shader API
- Libraries - Shader API
- Lib Alpha - Shader API
- Lib Bayer - Shader API
- Lib Defines - Shader API
- Lib Emissive - Shader API
- Lib Env - Shader API
- Lib Normal - Shader API
- Lib PBR - Shader API
- Lib PBR Aniso - Shader API
- Lib Pom - Shader API
- Lib Random - Shader API
- Lib Sampler - Shader API
- Lib Sparse - Shader API
- Lib SSS - Shader API
- Lib Utils - Shader API
- Lib Vectors - Shader API
- Parameters - Shader API
- Shaders - Shader API
- Release notes
- Release notes overview
- All Changes
- Version 11.0
- Version 10.1
- Version 10.0
- Old versions
- Version 9.1
- Version 9.0
- Version 8.3
- Version 8.2
- Version 8.1
- Version 7.4
- Version 7.3
- Version 7.2
- Version 2021.1 (7.1.0)
- Version 2020.2 (6.2.0)
- Version 2020.1 (6.1.0)
- Version 2019.3
- Version 2019.2
- Version 2019.1
- Version 2018.3
- Version 2018.2
- Version 2018.1
- Version 2017.4
- Version 2017.3
- Version 2017.2
- Version 2017.1
- Version 2.6
- Version 2.5
- Version 2.4
- Version 2.3
- Version 2.2
Layer management
Painter computes the layer stack from the bottom to the top. So, if you make changes to the top layer on the stack, Painter only needs to compute the changes of that layer. However, if you make a change to a layer at the bottom of the stack, Painter needs to compute all of the layers above that layer to calculate the final result.
There are various options you can use to decrease the performance cost of making changes to layers lower in the stack:
Geometry masks are your best optimization tool. Whenever you can isolate a part of your mesh to work on, do so, either by masking layers or folders. Geometry masks work by isolating either by UDIM or by mesh part, so areas that are not in the mask are not processed, improving performance. As a bonus, you can also isolate those parts visually in the viewport for easier texturing.
You can learn more about geometry masks with this tutorial, or by referring to the documentation.
In order to avoid slowdowns when making changes at a lower level in the layer stack, you can hide layers above the edited layer until you have finished making your adjustments. Painter doesn't process hidden layers, so if all the layers above your layer are hidden, it's as if you're editing the top layer in the stack. This way, the layers above will only be computed once, when you unhide them, rather than after every change you make.
Just like hiding layers, the disable blend mode will prevent layers from being calculated. It can be helpful to set low impact layers to the disable blend mode while modifying areas where they are unimportant.
Try to group layers whenever possible, as folders act like an invisible caching point. If you are making any changes below or above a given folder, the layers inside the folder won't all be recalculated individually, but rather their group result will be recalculated.
Filters can be expensive. If it's necessary to use a filter near the top of the layer stack, use geometry masks to decrease their performance cost.
Passthrough is frequently used with filters or brush stroke layers. It is a costly blending mode because it looks at all the layers underneath and transforms their result, instead of overriding the result like normal blending mode. Whenever using passthrough, try to combine it with Geometry masks and folders to minimize the performance impact.
With any tool or mode that has a Projection depth setting (warp, planar, path, etc), keep the Projection depth value as small as possible. The further the Projection depth extends, the less performant it is.
Brushes and tools with an orange tag have a dynamic parameter. This dynamic parameter can be set to "Unlimited", which means that every stamp in a stroke will be unique. This can have a substantial performance impact if using hundreds or thousands of brush strokes. In most cases, it's difficult to tell the difference after 16-32 variations, so generally speaking going beyond that is unlikely to have much visual impact.
Decreasing document resolution is the fastest way to improve performance. Doubling the resolution means a 4 times larger map, so going from 1k to 2k means up to a 4 times increase in performance cost. As a result, it's often useful to work at a lower resolution for as long as possible.