- Substance 3D home
- Home
- Getting Started
- Getting Started overview
- Activation and licenses
- System requirements
- Project creation
- Export
- Export overview
- Export window
- Export presets
- 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 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 10.1
- Version 10.0
- Version 9.1
- Old versions
- 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
Crash or freeze during startup
This page list known issues and their solutions related to the application not starting up properly.
Software conflicts
Take a look at the following page for a list of all the known software that may create conflicts: Software conflicts.
Running on the wrong GPU
If the application doesn't start on the right GPU it might lead to stability issues. See this page for more: Painter doesn't start on the right GPU.
Outdated GPU Drivers
Using old GPU drivers can lead to freezes and/or crashes. We recommend to use the latest GPU drivers when available. See: GPU has outdated drivers.
White screen and unresponsive
If the application freeze right when starting up on Windows (leading to a white screen) it can be of a few reasons:
- An external application is creating a conflict, see Software conflicts to know which ones.
- Some windows of the application were opened on another monitor. Restoring the interface to its default layout allow to start the application normally:
- Open the registry editor (regedit from the start menu)
- Navigate to the application preferences (see: Preferences and application data location)
- Expand the Adobe Substance 3D Painter key
- Select the Main window 2018 key and delete it
- Restart the application
Crash because of incorrect system Path/Python Path
The application checks the system Path to load Python modules and environment settings. If the system has an incorrect setup it can lead to a crash during the startup.
On Windows:
- Open the Start menu
- Search for and select the System (Control Panel)
- Click on Advanced system settings
- Click on Environment Variables
- Under System Variables find the PATH variable
You can then edit the variable to verify its content. For example if the variable contains this kind of following characters it will lead to a crash
ï–›éŒ à €è¸€ì‡ì‡ç¿¹
Windows 10 Updates
Some update of Windows 10 may sometimes create instabilities. Use the diagnostic tools provided with Windows to detect any potential errors in the system.
We recommend running the Deployment Image Servicing and Management (DISM) and the System File Checker (SFC) tool. DISM is useful to recover the replacement files needed by SFC in order to fix corrupted or missing system files.
Running DISM :
- Open the Start menu
- Search for Command Prompt
- Right click on the result and choose "Run as Administrator"
- Type the following command : DISM /Online /Cleanup-Image /RestoreHealth
- Press Enter
Running SFC :
- Open the Start menu
- Search for Command Prompt
- Right click on the result and choose "Run as Administrator"
- Type the following command : sfc /scannow
- Press Enter
Restart your computer after both commands to apply updates.
For more information on this subject see: Use the System File Checker tool to repair missing or corrupted system files.
Crash when starting up on older versions
On Windows, version 2018 (4.x) or older may not start because one of the dll file provided with the installation folder is too old for the operating system. This crash can be fixed by manually replacing the file with a more recent version.
To do so:
- Navigate to Substance Painter installation folder.
- Rename the file libeay32.dll in backup_libeay32.dll.
- Download the following file: updated_libeay32.zip.
- Extract the dll file from the zip file into the installation folder (next to Substance Painter.exe file).
- Start the application.