Connect, learn, and get help texturing your 3D assets.
Recently active
The Substance 3D team has put together a comprehensive introduction to OpenPBR aimed at 3D artists of all levels, across any discipline. This is a software-agnostic guide, covering the underlying model, how its layers and parameters work, practical material creation guidance, and an FAQ addressing common questions and pain points.It covers everything from the basics (what OpenPBR is, how dielectric and metallic materials differ) through to more advanced topics like transmission, subsurface scattering, thin-film, and more, as well as a section on how to avoid some of the most common mistakes.You can find the documentation right here!
Substance 3D at SIGGRAPH 2026: faster workflows, OpenPBR everywhere, and digital twins at scale We just posted our SIGGRAPH 2026 announcements over on the Adobe blog. The key points: OpenPBR is now supported right across the Substance 3D ecosystem — Painter 12.1, Designer 16, and Sampler 6 — with the entire Assets library (14,000+ materials, decals, and atlases) being converted too. Adobe has also released an open-source OpenPBR implementation on GitHub. Substance 3D Painter 12.1 delivers the long-requested Skew Map Painting, giving artists direct control over baking artifacts with brush, fill, and edge protection tools — alongside Auto Rebake, which speeds up iteration by only rebaking affected areas, a refreshed baking workspace, and a new Hard Surface Auto UV mode for mechanical assets. Substance 3D Designer 16 expands the procedural toolset with a redesigned Shape Splatter v2 node for scattering varied 3D forms procedurally, new SDF nodes for building and manipulating complex sha
Feature Request: Local Cage Offset Painting for BakingI'd love to see a Paintable Cage Offset feature in Substance 3D Painter, similar to Paint Offset in other programs.Currently, we can only adjust cage distances globally or import a custom cage. In many production scenarios, only a few small areas require additional projection distance. Being able to paint the cage offset directly on the low-poly mesh would:Reduce baking artifacts on complex assets. Eliminate the need to create custom cage meshes for minor issues. Speed up the baking workflow significantly. Work perfectly alongside the existing Skew Painting system.Ideally, artists could:Paint positive and negative cage offsets. Preview the offset cage live in the viewport. Blur/smooth the painted values. Rebake automatically while painting (similar to Auto Rebake). Store the offset map per Texture Set.This would make Substance Painter's baking workflow much closer to others programs while keeping everything inside Painter
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.
I have two issues with with my project, but I'm not sure if they're connected. When i import my model, I see an error in the log stating that part of the model has "faces in out of bounds UDIM indices [0, -1]". The part of the mesh with these problematic faces is named, but when I go back into Maya and check it, the faces on that mesh are not out of bounds at all. I'm trying to get ambient occulusion and curvature maps from substance painter to use in Mari, but when I do the bake with this same mesh, the result is completely messed up and I've never had this happen before, so I have no idea what's going on. Are the out-of-bounds faces causing this baking issue? Or is it something else? I've attached screenshots of the error message, the uv faces referenced, and the botched bake result:
I try to set few Display parameters :Environment Opacity Environment Exposure (EV) Environment Blur Environment Rotation Environment AlignmentI want to do that in Python by can not find a way to do that.Thanks in advance!
I’m coming to here a little pissed off after losing FOUR HOURS of work because apparently for the last hours of texturing, I hadn’t noticed the small red text (usually covered by my taskbar) that was letting me know that I was NOT saving my file. So, eventually, when substance painter inevitably crashed like it always does, I lost SO MUCH PROGRESS. PLEASE for the LOVE OF GOD, make it so whenever the program is unable to save, it appears as a POPUP, so people like me who usually don't check the error messages will be able to fix the issue before it overwrites progress. Yes, you can argue that I should always be checking the error messages, but I would argue for an issue as big as the FILE NOT SAVING, that it deserves an error popup window. Thank you.
ID Mask viewed in PhotopeaID Mask Viewed in Substance Painter Result of using a mask with that wrapping ID mask in Photopea to show where the green is wrapping fromResult of using the ID mask, showing a second material causing a seamExtra example in substance to show the wrapping despite ID mask being clean when viewed in Photopea. (There will be black wrapping onto the red section too)Simple reproduction:Use an edge-to-edge 0–1 UV island. Bake contrasting ID colours at opposite edges. Export the ID map. The exported image is pixel-perfect and contains no bleeding. Inside Painter, use Color Selection. The colour from the opposite edge bleeds into the generated mask.Re-importing the exported ID map as a regular texture and viewing it inside Painter displays the same wrapping/filtering at the edges.Maybe I am missing a setting or using this incorrectly, but the behaviour seems odd. I spent several hours trying different bake, padding and viewport settings before eventually exporting the
12.1.1 build 5594,The emission channel is ineffective in OpenPBR material mode, whereas it works when switching back to the previous material.
Hi. im trying to bake normal maps from my work and got some error log.In the project the mesh has 3 texture set lists. 2 of them use only one tile. but the other one has UDIM with 2 tiles.Mesh maps of all of them have been done sucessfully, i also checked Log '[StacksExporter] Map export ended' text to make sure. And during work, i didn't meet any problem. But when i tried to export final normal maps today, two mesh texture sets with no UDIM got it success, but the mesh texture with UDIM keeps failed and in the log i can only see two lines that is[MapExporter] Nothing could have been exported on the Cup stack:[MapExporter] The channel Normal is not available in the Cup stack.(Cup is a name of the texture set.) i did some tests. With the same mesh texture set, i tried changing output directory and file type and nothing worked. And did exporting other maps like rough or diffuse, or height with exr format and they all ok with exporting. of course the border of UV tiles has
## SummaryPlease add a Python API to set the active brush color (Base Color and other channels) on Paint Layers.## ProblemCurrently, there is no way to set the brush color of a Paint Layer through the Python API in Substance 3D Painter. The available APIs allow:- Reading and writing **Fill Layer** uniform colors via `_substance_painter.source.set_source_uniform_color()` and `set_fill_source()`- Reading and writing **shader parameters** via `alg.shaders.setParameters()` (but this only covers shader-level params like sssColor, not the active brush color)However, there is no public or private API to set the **active brush's Base Color** that gets applied when painting on a Paint Layer.## Use CasesThis limitation blocks many useful tools and workflows:1. **Per-stroke color picker / eyedropper plugins** - Sample colors from the viewport, a reference image, or a baked map (World Space Normal, Position, etc.) and apply them as the brush color for each stroke. This is critical for stylized tex
I brought my materials into Blender from Substance 3D Painter and everything lines up pretty nicely, besides this one part under the keypad. I did a high-low baking. I know the imprint is thanks to baking through to the blue part, but in Substance Painter, this is hidden by the keypad so it’s not a big deal. Even though the UVs and the models are identical, for whatever reason the textures don’t line up the same. Re-exporting the mesh from Blender and re-importing the mesh into Substance has no effect within substance and it still looks normal.I’m not sure if this is related but the corners of the objects also don’t smoothly connect like they do in substance painter either. I don’t know if I’m missing a setting or if there was a problem with the export.Material view in Substance 3D PainterMaterial view in Blender
I can’t open https://substance3d.adobe.com/education/ , as it leads to a “504 Gateway Timeout” error.
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 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
OS: Windows 11 GPU: NVIDIA GeForce GT 1030 (2 GB) CPU: Intel i5-10400F Works: Substance Painter 11.0 Broken: 11.1+ (and upwards) Symptoms: New and existing projects affected. Model initially appears white until a layer is toggled. Toggling a layer makes textures sharp. As soon as the camera rotates/pans/zooms, textures become permanently blurry. Texture Set resolution remains at the selected resolution (does not change). GPU usage stays around 20%. Already tried: Clean reinstall. Updated NVIDIA drivers. Verified Painter is using the GT 1030. Vulkan diagnostic tools run without errors. Problem only appears in versions using the Vulkan renderer. I don’t think it is my graphic’s card at fault since i even tried small texture sizes and light models and it still becomes extremely blurred (it’s not being overwhelmed), what do you guys think? Please help.
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
This is a simple question, not sure if its been implemented in this manner as its been a while since I have used painter. But, what i wanted to know was, similar to marmoset toolbag has a bevel shader, will or does painter have the ability to “bake” in a beveled edge as if replicating a high poly bake from a higher poly model along edges. thoughts? I understand it has a bevel filter, but I don’t recall it doing anything in that capacity.
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
I was unable to bake my carvature in v12. It turned out black. Same model baked well in v11.
Please add "Save and Compact" to the keyboard shortcuts menu so we can assign it a hotkey or overwrite the default Ctrl+S.Right now, the standard incremental save system balloons project files with dead data, making them way larger than they need to be. Often I’ll find files that are upwards of 800+MB that compress down to less than 100MB. The only way to purge this is by manually clicking through the file menu every time, because the action is completely missing from the shortcut settings.While I understand this isn’t the default as it can take longer on large files. I’ve found that for almost every file I’ve worked on it takes about the same length of time as saving normally. I work with other artists who constantly forget to do this manual step, which results in massive files that bloat our repos and seriously slow down our pipeline. If we could just tell the team to change their Ctrl+S shortcut to Save and Compact, this problem would be fixed immediately.It's incredibly frustrating
My biggest gripe with Substance Painter is not being able to isolate and view what an individual layer is doing. Once you have a lot of groups and layer stacks it becomes extremely combersome to toggle layers on and off. Could we utilize the drop down menu in the viewport that allows us to view individual maps and channels to give us not only a layer mask preview but the selected layer(s) as an option also? Better yet, just give us a node graph, please and thank you.
Hello Adobe Substance 3D Painter team,I would like to suggest a few features that I believe would significantly improve the hand-painted texturing workflow. One-click Color Picker Remove the confirmation click after using the Color Picker. When pressing P and clicking on a color, it should be selected immediately without requiring a second click to confirm. Hide Mesh Parts by UV Islands Add the ability to hide or isolate mesh parts based on UV islands. This would make it much easier to paint areas that are occluded by overlapping geometry without constantly changing camera angles or manually hiding meshes. Photoshop Live Connection Add a live connection between Substance Painter and Photoshop. This would allow artists to use Photoshop's advanced selection tools (such as the Lasso, Polygonal Lasso, Magic Wand, etc.) and have the changes update directly in Substance Painter. More Color Picker Layouts Add additional color picker interfaces, such as: Triangle color picker
Hello, I’m trying to use a grunge map as the base color of my material, then run it through a gradient map to color it. I wanted to use an anchor point before the gradient, to create a roughness map that matches the grunge I’m using as my base color. This works, but the the anchor point roughness map comes out much darker than the base color grunge that it is derived from. What is the reason for this? Shouldn’t the anchor point just directly copy the greyscale map? I made sure that the anchor point is BEFORE my gradient and AFTER my levels. Base color from grunge mapRoughness from grunge map anchor pointThanks for your help, On a side note, is this the best method to do this? I can’t find much about working like this online.
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
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.