Bug Reports

import substance_painter as spcurrent_stack = sp.textureset.get_active_stack()selected_layers = sp.layerstack.get_selected_nodes(current_stack)for layer in selected_layers:    if layer.get_type() == sp.layerstack.NodeType.GroupLayer:        # this always returns an empty list, regardless of the number of effects on the group layer        layer_effects = layer.content_effects()

After updating to version 12.2.0, I received a notification upon launching the program stating that I needed to update my graphics drivers to the latest version. I did so and then launched the program; however, issues arise as soon as I try to work with masks or layers—the program itself remains active, but the viewport stops responding. I am using an RTX 4070 with the 621.01 Game Ready driver.

Hello! I am trying to Run Adobe Substance Painter 2025 on my Macbook, through Steam. I have tried everything to make it work yet it continues to crash on the startup. I have submitted a Log.TXT to see if it can be diagnosed. System Specs:  (Image removed)

So i posted this a while back before but the Post has been removed for some reason…. i guess because being inactive on the post. but yeah this happens when using the Pen Tool more you use it. adds artifacts to your Height and the only fix for this was to Down Grade to 2025 11.0.3… Any Higher that that Version the Bug still remains there…… shocking its still there in 2026 Video example i made for the old post  

Since upgrading to 12 and above, I’ve had nothing but graphical bugs and corruption with my textures in the viewport. Previously, in 11 and below, I’d never encountered any of this. Admittedly, I am using an old graphics card still - the GTX 1080, which is using the latest drivers. I’ve tried uninstalling Substance Painter and reinstalling, but it doesn’t fix the issue. I’ve also tried disabling the Sparse Virtual Texture in the settings.The video recorded and attached demonstrates perfectly the kind of graphical corruption I keep getting. At the moment, I’m using 12.1.5.Graphical Corruption

Error example:[BakingProcess] Can’t create a resource from the baker result: tile (0,0): couldn’t find surface in resource world space normal *name of asset*When starting a new file, baking completes as expected without any error. But upon making shader application or UDIM lay out changes to the asset in Maya and re-importing the mesh, baking fails on all mesh map bakes.Error seems to be stemming from UDIMs changing texture sets/UV coordinates.Tests/Attempted Solutions:1) Not moving any UV’s, and only applying a different shader in Maya (Error)    • Seems to not matter if texture set stays enabled or gets disabled in Painter2) Not applying a different shader/texture set, and only moving a UV island to a new UDIM (Error)3) Making a new Painter scene and using the mesh with the changes (Bakes as expected)4) Tested with different assets, all give the error5) Tested with Substance Painter 11.0.3 (Bakes as expected)6) Instead of using “Re-import Mesh”, I tried going to Project Configuration

Version: Substance 3D Painter 12.1.2 (build 5641, Windows, Vulkan)OS: Windows 11Steps to reproduceCreate a new project with Color management set to "Adobe ACE - ICC". Save the project. Close Painter with the project still open.ResultPainter crashes during shutdown and the crash report window appears. It happens on every exit. It does not happen when no project is open, or when the project uses Legacy color management. Reproduced with all third-party plugins disabled.Crash detailsAccess violation (0xC0000005) reading freed memory in ACE.dll+0x24715, on the main thread, while the main window is being destroyed:main> Alg::S4GuiApplication_ destructor> Alg::S4MainWindow destructor> Alg::MainWidget destructor> ... (PaintEditorToolBar children)> Alg::ToolBarSourceColorPickerView destructor> Alg::GrayScaleButton destructor> Alg::ColorManagement::ACEColorSpaceTransform destructor> ACE.dll (transform unreference) <- crashThe ACEColorSpaceTransform held by the toolbar

Problem with baking rounded objects (but this apply to many other cases).Example with this Cactus Sculpt. Here is one layer of the upper flower _high, viewed from side and from above: Automatic cage (experimental), works amazingly well for tons of complex objects, but not for some simple ones like the example above. If I bake with Cage type set to: Automatic (experimental), it feels like the Max rear distance is infinite and catches anything behind faces. If I bake the more traditional way with a hand-made cage mesh, or with the basic Distance-based Cage type, it works perfectly fine: So basically, there’s an issue with Automatic (experimental) Cage type. The automatically calculated “Max rear distance” cannot be controlled by the user, and the one that’s calculated automatically seems to go indefinitely, baking everything on the opposite side of my polygons normals direction.Of course there are tons of workarounds. But it just doesn’t feel right. Esepcially given how much of a revolut

Tested this on a dummy file and i'm getting the same issues, images attached below. So I just built a new PC and started working in substance again only to realize some of my bakes are completely broken. AO in particular has these weird artifacts appearing all over the model. The model and UVs are fine and my GPU drivers are updated to latest. At my wits end trying to fix this. PC spec is 7600x3d and 7900xtx with 32 gigs of ram. Windows 11. I'm using Substance Painter 2022 Steam Edition. 

If I press the Tab key, it’ll hide the UI like it should, but if I press it again, the program crashes. It happens in every 12. version, pls fix

Since 12.1 (this is 12.1.1) the VRAM usage of Substance Painter is crazy. There's another bug report about performance issues but for me it wasn't clear if it's VRAM related.What happens:While working on a very small scene which only uses like 3GB of VRAM it skyrockets to the max in the matter of minutes while working on it.This is 100% a memory leak and happens as well with version 12.1.1My system is nothing special, Win 11, 64GB, i9-9900K but what makes it a bit more special is the fact I have 2 GPUs, a 3090 and 4090 both with 24GB VRAM.I tried to force using the 3090 using the options inside Windows Display > Graphics options but that doesn't help, it only switches the issue to the 3090. I'm currently at the Nvidia 610.62 Studio Drivers.If I quit Substance Painter while it hugs the 24GB it will roughly empty 12GB and after like a minute it gives me back another 10GB of VRAM.It also doesn't really matter what I do, the screenshot attached is a storyboard where I only hide/unhide m

1.Open new project2. switch shader to pbr-material-layering or pbr-material-layering-10-mats3. assign all materials to any material that has distinct normal map(e.g. Stylized Wood Bark)4. Normal map is visibly blank/totally flat - buginterestingly enough, while no materials in the basic library work, some materials from substance 3d assets do work, this one for example :https://substance3d.adobe.com/assets/collections/1b1c286f3c9fd90f5aaca37388d9c7371c4d0753/asset/4186eaeaf99dc95f06c4cc2e164ce0fb5d3c3150 

The Steam perpetual version of Substance 3D Painter 2026 has significant lag and stuttering every few seconds. I saw patch notes claiming this has been fixed, but it has not been fixed on the Steam version it seems.Specs:OS: Windows 11GPU: NVidia RTX 5090CPU: Intel Core Ultra 9 285KRAM: 64GB DDR5Storage: 2TB+ NvMEThings I’ve Tried:ReinstalledClose Logitech lamp array servicesRestart PCForce Substance to use dedicated GPUAny way that Adobe could look into this issue would be great. It’s negatively impacting my ability to work.

Even if I change the autosave settings such as the 'autosave interval' and press save, the settings revert to the default when I restart the application.Please make the autosave settings remain as configured even after restarting.

Environment: Substance 3D Painter 12.1.3, Windows 11 22631, RTX 5080 (NVIDIA 610.62 / 610.74 / 616.56 — identical on all three), Wacom Cintiq 22 as primary display, Windows Ink enabled per Adobe's pen guide. Reproduces since 12.1.0.Symptom: during a normal painting session the viewport stops updating permanently. Menus, panels and the layer stack keep working; Windows never flags the app as unresponsive. F, view toggles, resize, dock re-attach, minimize/restore do not recover it. Only a restart does.Conditions (several dozen occurrences over two months):- Only while using the pen. Never with the mouse — zero occurrences in mouse-only sessions.- Almost always during camera navigation (Alt+drag), not during strokes.- Often preceded by a sudden camera jump. Worse after Alt+Tab and back.Evidence collected on one instrumented occurrence (2026-09-07 20:10):- Minidumps (6 total): the "SAL Render Thread" is parked in std::condition_variable wait (ntdll!NtWaitForAlertByThreadId → RtlSleepCondit

I’m unsure what is causing the issue. Before latest update to 12.1.0, I have not experienced any issues like this. I’m on win11 pro latest updates as of 2026/07/03. Painter is installed on a 2tb gen4 nvme (its my OS drive) and my work files are done on a gen5 samsung pro 9100 drive. Previously saving files was fairly quick, even files over 5gb in size. But now when I save I have to wait as it hangs for a while (1-1.5 minutes) before the save completes. This only happens on large files that is over 1gb in size. When I exit after working, then it also hangs a while before closing, or it just hangs indefinitely and I have to force close painter with task manager. I’m unsure if it is a windows issue, or gpu driver issue, or painter issue. My drivers are up to date. Latest Nvidia studio drivers (v.610.62) through nvidia app. Nvidia app overlays are disabled and no performance settings for apps are done through the nvidia app. System: r9 9950x3d, 64gb ddr5, Rtx 5070ti and above mentioned nvm

On Linux, Substance 3D Painter 2025 has a regression in version 11.1.2 where the color picker modal window no longer appears.Versions 11.1.1 and 11.0.3 work correctly on the same system.Since Steam does not allow downgrading, could you please expose 11.1.1 as a beta branch so Linux users can continue working while the regression is investigated?This would be extremely helpful for production use.i have nvidia rtx 5090

I found a reproducible regression in glTF transparency export between Substance 3D Painter 10.1.2 (2024) and 12.1.2 (2026).I have already submitted this issue using Painter's built-in Bug Report function.Bug Report Reference: ADB-46817980-K2B5Environment Adobe Substance 3D Painter Steam Edition Windows Painter 10.1.2 (2024): works correctly Painter 12.1.2 (2026): issue occurs ProblemI created a very simple FBX containing only two polygon planes and tested the exact same FBX and textures in both Painter versions.For transparency, I used: Opacity channel pbr-metal-rough-with-alpha-blending shader Base Color textures Opacity textures Transparency is displayed correctly inside Painter in both versions.However, the glTF export result is different.Painter 10.1.2The exported glTF contains:"alphaMode": "BLEND"Transparency works correctly in external glTF viewers.Painter 12.1.2The exported glTF contains:"alphaMode": "OPAQUE"Transparency does not work in external glTF viewers.The exp

지난주까지 문제 없이 작업이 됐던 한글 경로에 있던 프로젝트 파일 실행이나, 한글명 파일 모두 작업이 안됩니다심지어 작업 표시줄에서 바로 프로젝트 파일이 불러와지지 않고 그냥 실행자체가 안됩니다.어떤 로그도 나타나지 않고 그냥 프로그램이 거지고있어요

I wish to open a substance file my friend had sent me but it says i need to update my substance painter to verison 9.0.0 to do so. There is no update button on my steam 2022 substance painter help tab. I dont know what to do.

it happens so often, i mean holding the click and drag things in general sometimes it works and other times dosent, i tried using the trackpad and mouse and its the same result

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