- Substance 3D home
- Home
- Getting Started
- Interface
- Tutorials
- Common issues
- Release notes
Error: Substance 3D viewer has encountered a problem and needs to close.
If you encounter this dialog, it means that Substance 3D Viewer (Beta) experienced an error it was unable to recover from and the application closed, or crashed.
In all cases, the best action is to use the dialog provided to share information about what you were doing when the app crashed and send a crash bug report. This will allow the development team to track the cause of the crash and resolve it!
Tips to prevent crashes from memory
Application crashes can occur for many reasons, but one of the most common is that the system is running out of memory. These types of crashes are common on devices that do not have shared system memory and use traditional VRAM, and especially when dedicated VRAM is relatively low.
Note that 8 GB of VRAM is the minimum required to run Viewer, while 16GB or more is recommended. See the full system requirements.
- Use Activity Monitor (Mac) or Task Manager (Windows) to track your overall system memory usage.
- If your system memory usage is getting high:
- Close unneeded applications
- Restart the device to clear caches and temporary files
- If your app memory usage is still high you can reduce Viewer’s memory consumption by:
- Reducing the size of images used in Viewer including background image
- Reducing the size of Substance materials by editing the resolution property
- Reducing the size of the canvas and render frame
- Reducing the size of textures or removing extra textures from standard material formats
Note: It is normal for graphics programs to consume high amounts of memory. It is unique to each document on the total amount of memory that will be used based on the number of 3D objects, materials, textures, and images. Images consume more memory than 3D objects, so optimizing materials by reducing duplicate materials, reducing resolution, and removing unneeded textures will have the most memory impact.
At some point there is a limit to what any hardware can do. If you are continuously experiencing crashes with high memory consumption, you may need to evaluate your hardware for your project needs.