Delighter Issues

Why is the Image to Material (AI Powered) and the Delighter missing from the filter list?

These filters require specific hardware. Verify you respect the minimum requirements by looking at the System requirements.

The application crash when using the Image to Material (AI Powered) and Delighter filter

These filters require a lot of available VRAM (at least 1Go). If you have a GPU Card with only 2Go of VRAM available and working in 2K/4K resolution, we won't be able to allocate enough memory to execute the filter and it occurs a crash.

Performance Issues

The user interface of the application lags when I interact with the layer stack or any UI elements.

We identified an issue when Wacom drivers are installed. Uninstall your Wacom drivers can solve the issue and make Substance 3D Sampler runs fast and snappy.

The color picker takes a very long time to open the first time.

We identified an issue when Wacom drivers are installed. Uninstall your Wacom drivers can solve the issue and make Substance 3D Sampler runs fast and snappy.

Recurring Crashes

The application crash when exporting a material

Crash at export can occur when exporting a material created in Substance 3D Sampler. This crash can be the result of a lack of VRAM available on the GPU when launching the export process (especially with materials using the delighter filter).

UI Issues

The Substance 3D Sampler interface is transparent.

Deactivate the FXAA anti-aliasing setting in the drivers of your GPU card and restart Substance 3D Sampler.

The fonts are not displayed correctly.

If you're on Windows 10 Enterprise and use the Block Untrusted Fonts feature, you can follow this tutorial to exclude Substance 3D Sampler of the list of untrusted apps for untrusting font blocking.

Data/Project Issues

Materials are missing after upgrading from the beta version to the 2019.1 release

Content produced with the beta version 0.8.1 or older is not compatible with version 2019.1 or newer. However, nothing is lost and this data can still be accessed by launching version 0.8.1. Content created with 0.8.1 and 2019.1 are separated. Working on one version won't affect the other.