Substance 3D Painter

Hi everyone,For the past few weeks I've been having serious performance issues with Substance Painter, starting right after the latest updates.The app takes a very long time to open, and often gets stuck on the splash screen Once it does open, it's extremely slow and freezes, even with very light projects, not just heavy files Running the app as Administrator improves things slightly, but it's still noticeably slow overallSystem specs:OS: Windows GPU: RTX 3070 TI (drivers updated at the latest version) RAM: 32GB Substance Painter: latest versionWhat I've already tried:Full uninstall and clean reinstall of Substance Painter Full uninstall and clean reinstall of Creative Cloud Clearing the cache Checking for GPU/overlay conflicts (Nvidia overlay, mouse software overlay) no change Running as Administrator (minor improvement, but issue persists)Nothing has fully resolved it so far. Has anyone else run into this after the recent updates? Any suggestions on logs I should check, permissions t

After applying a smart material with a black mask and using polygon face fill mode to select a specific area of the mesh I want to, this sometimes happens and its really annoying, I cant seem to find a fix for it, nor have I seen anyone with the issue. Ive ran into this with other models in the past, so this isnt a first time issue for me. I will go ahead and drop the model for anyone to look at so you can check my UV coordination to see if anything is wrong, or if its something I have to do in the software itself to solve the issue. Thanks in advance

My normal workflow has always been to store my project on a network location. The network storage is a local network not cloud based. Previously I have been able to import assets (fbx, png, spsm, etc) to the project with no issue.However recently I have noticed that it consistently fails to import if the source file resides on a network location, even if the network location is the same as the Substance file.If I relocate the file to be imported to a local drive, leaving the Substance file on the network location, then the import succeeds. Has there been a change in behaviour of imports?

Bug Report: Substance 3D Painter 12.1.2 — Export Fails to Network (Synology SMB) DrivesSummaryExporting texture maps in Substance 3D Painter 12.1.2 fails when the export destination is a mapped network drive pointing to a Synology NAS share. The export process reaches the "Finalizing export" stage and then fails for every map in the batch simultaneously. The issue does not occur when exporting to a local disk or to a mapped drive on a QNAP NAS. Rolling the application back to 12.1.1 resolves the issue completely with no other changes to the system.This strongly indicates a regression introduced in the 12.1.2 release affecting how the exporter finalizes (writes/renames) files on certain network/SMB destinations.EnvironmentApplication: Substance 3D Painter Affected version: 12.1.2 (issue present) Working version: 12.1.1 (issue not present — confirmed by rollback) OS: Windows 11, version 25H2 (identical build on both test machines, same update history) Export destination: mapped network d

**Product:** Adobe Substance 3D Painter 12.1.2 (build 5641)**OS:** Windows 11 Pro, Version 25H2 (OS Build 26200.8457)**CPU:** Intel Core i9-14900F**RAM:** 128 GB**GPU:** NVIDIA RTX 4090 (24 GB VRAM)**GPU Driver:** NVIDIA Studio Driver 610.88 (clean install)---**Issue Summary**Substance Painter crashes repeatedly with heap corruption. The crash occurs when working with materials, especially dragging/moving/reordering them in the layer stack. However, it also crashes when simply opening files. The crash is NOT limited to one project or custom materials.**Exception Details**- Windows Event Viewer: - Faulting module: `vulkan-1.dll`, version 1.4.341.0 - Exception code: `0xc0000409` - Fault offset: `0x00000000000dce55`- Microsoft Sysinternals ProcDump: - Multiple C++ exceptions (`E06D7363`) - Final exception: `C0000374` (STATUS_HEAP_CORRUPTION) - Process Exit Code: `0xC0000374`This indicates an application/Vulkan/graphics-related memory corruption issue rather than a damaged project or

We’ve noticed that Roughness map (Specular Roughness) fails to export when packed with other maps. The only solution we found for it to export properly was by first using document channels export preset, which seems to be loading the texture into memory, THEN exporting with any other preset.

When I use a FBX file it uses correctly the Material Name that is assigned to the Mesh:Assignment in the Maya Model file:When I use a USD file it uses the Shading Group not the Sader as a Name: I checked my USD and the Shader is still assigned:  It would be great to have only one way of naming here either for both the material name or for both the shading group name, but mixed is confusing our pipeline when exporting the texture files. Thank you!Best regards,Timo

Windows 11 | Painter 11.1.3 | Nvidia GeForce RTX 3080Ti | 128 GB RAM | ADM Ryzen 9 5900X 12 Core When I create a new File I set a OCIO (Custom, ACES 1.2 or ACES 2.0 doesn’t matter). Then I load in external texture files and set their Output color space. It doesn’t matter if I set this manually or automatic via OCIO rules All good and works like that:After saving and reopen the file I lose all the “Output color space” OCIO rules/settings. It displays not compatible and only the defaults are available. When I check the Project Configuration it is still using the correct OCIO file and there is also no Error/Warning in the LOG: Does anyone else has this issue? It is a critical Bug in our case because textures load wrong and are not correctly exportet. Also it is very confusing. Sadly we can’t go to Painter Version 12 yet because of the python version switch. Best regards,Timo

Hello! It's more an issue with Steam pricing, but Valve to this day refuses to adress it - so it can only be adjusted by the developer/publisher. The core of the problem is Multi-Variable Conversion method that Substance 3D Painter uses on Steam; this conversation uses outdated data that punishes some regions.Poland is the prime example for this issue - in case of Substance, which base price is 199.99$, the Polish people have to pay almost 250$ for the purchase. Higher then Norway while our economies are far from comparable. Pictures below.​​So for no reason we pay 24% extra for software on steam.https://polishourprices.pl/ describe the problem the best. Best case scenario would be to match the base price (199.99$). Thanks for understanding and any help regarding this issue! 

I was unable to bake my carvature in v12. It turned out black. Same model baked well in v11.

When importing compatible ABC files into Substance Painter, mesh names for geometry masks come in with incorrect extra leading forward slashes. For example, with an ABC hierarchy of…foobarbaz...the mesh names come into Substance Painter like so:/foo/bar/baz While this could be considered just an inconvenience, it causes a practical issue.  The same source exported as FBX does not result in this same extra leading forward slash; and so if a project is set up to use mesh names for geometry masks and the model is updated between ABC and FBX, then the geometry masks will not be preserved after the model update.This can be worked-around by restricting a file to only use the model format it started with; but this seems to be a limiting restriction.

12.1.1 build 5594，The emission channel is ineffective in OpenPBR material mode, whereas it works when switching back to the previous material.