Bug Reports

## SummaryIn the native Linux build of Substance 3D Designer, the mouse scroll wheel does not behave as intended when the desktop session is running under **Wayland**. Under an **X11** session, behavior is correct. This affects both the 2D node graph view and the 3D viewport.## Affected versions- Substance 3D Designer 2025 — confirmed- Substance 3D Designer 2026 — confirmed (identical behavior)- Substance 3D Designer 2022 — **not affected** (correct behavior under Wayland)This indicates a regression introduced sometime between the 2022 and 2025 releases, coinciding with viewport/rendering changes (2025/2026 logs show a Hydra-based viewport, `LayaHydraEngine` / `HdEclairRendererPlugin`).## Environment- OS: Arch Linux- Desktop: KDE Plasma 6, Wayland session (native, not XWayland-forced)- GPU: NVIDIA GeForce RTX 3090, proprietary driver 610.43.03 (Vulkan)- Qt platform plugin loaded by Designer: `xcb` (confirmed via `QT_DEBUG_PLUGINS=1`; the Designer window itself renders through XWayland/

I haven't used Designer in a little while (busy at work), but I booted it up yesterday, only to see that Tessellation Factor is now gone. And the base high-res plane has nowhere near enough geo to be of any use without tessellation. Why on earth was this removed?  I know I could make a super dense plane in Max etc, but I really shouldn't need to. I see parallax occlusion mapping is also now gone. Again, why? This makes no sense.

I have a material where I use a RTAO node. In substance designer the material looks correct, but when I import it via Substance 3D Plugin in UE and generate a material from it, the textures are broken.Here are some examples of Substance Designer:(Working base color)(Correct normals) (Wrong base color after import to UE via Substance 3D Plugin)(Wrong normals, it is as if the normals have not been calculated further than before the first RTAO node) When swapping the RTAO with a HBAO node it is working but of course does not have the same look.I’m using substance designer steam edition:Version: 13.1.2 build 7745 commit 1e6555a8 Release (04/06/2024) - Steam editionEngine Version: [Direct3D 11] 9.0.3 commit 0x41325881 (04/06/2024)Bakers Version: 2.5.7 commit 0xe9235188Substance in UE5 Plugin Version: 5.7.1 The Substance Designer sbs is attached.

Hi,I've been with support for hours and hours trying to get the Exclude Pattern in the Preferences > Projects > Library paths to work with no success. My objective is to specify a root directory for an asset library which has a bunch of assets shared among artists. I want Recursive enabled so it would automatically scan the subdirectories for all the assets. LibraryRoot/Asset1/LibraryRoot/Asset2/LibraryRoot/Asset3/...Each asset subdirectory will look something like:LibraryRoot/Asset1/asset.sbsLibraryRoot/Asset1/WIP/asset1.sbsLibraryRoot/Asset1/WIP/asset2.sbsLibraryRoot/Asset1/WIP/asset3.sbs... WIP will contain development save iterations of the asset and should be excluded from the Recursive scan.I've tried the following Exclude Patterns:WIPWIP/*/WIP/**/WIP/*.*[\\\/](?:WIP)(?:[\\\/].*)?$also with and without quotations. Nothing works, it seems like it's completely ignoring everything in this field. Can anyone confirm if this works or doesn't work for

When selecting the Rasterizer Renderer, baked normal maps does not render correctly on symmetric models. The OpenGL can render it correctly, but it was recently marked as deprecated and added a warning that it will be removed.Updating drivers didn’t made any change.No issues with the normal map on any other app, including PainterOn Substance Painter the maps looks fine. 

Hi, recently I upgraded to Substance Designer 15, and now when I try to create a new project or open an existing one, the program crashes. It seems like an issue with the 3D view because when the crush window appears, my 3D view is blank.What I tried so far:updated drivers for my video card (put studio drivers for Nvidia) reinstalled substance changed to OpenGl and Iray  checked python libraries installed and uninstalled ReShade libraries because saw it as a potential fix from another post

Hello from Ukraine!:)  I have an issue with SD 15 - it started to crash on loading the project.Yesterday I worked on a several projects, and all was well. Then, today I tried to open SD (I tried my projects, and even blank new scene, doesn't matter), and it crashes on loading.  After some tests I discovered that this is caused by rasterizer renderer initializing. If I disable 3d view before loading the project, I can use Designer, move and connect nodes and see 2D outut, all works as before. But if I initialize 3d view (no matter - using rmb on Output node or from window>new 3d view), it shows me black 3d view for a second and then crashes. I even can't switch to OpenGL, even if I set OpenGL as default renderer in settings, it still tries to initialize Rasterizer first (why?). The issue is I've already updated all my important projects to 15 version so I even can't open them in older versions of Designer. I tried 14 version, it works well with OpenGL ev

Title says it all. I’d provide more information if I could. I wish designer would tell me what exactly the problem is but I just get a small window that tells me: “Error publishing package. Check the console for details”. And if I check the console nothing is there. Where should I look?Thanks in advance

This is just ugly now, could you move either one of the Previews to align with each other? 

Hello,The new Color.Raytraced baker does not render the correct material colorsIt worked correctly in v14 but chooses random colors in v15.   Additionally, Color.Raytraced does not function correctly through the SAT.  If left to the default, or set to mesh_color through the --color_source flag, it renders a black image.  Example command: <path_to_baker>/substance3d_baker.exe Color.Raytraced --inputs <path_to_low>\low3.fbx --output_path <out_path>\ --high_scene_paths <path_to_high>\new_colors7.fbx --output_size 1024,1024 --output_name ID_Test --padding_radius 10 --projection.max_height .5 --projection.max_depth .5 --color_source mesh_color Assigning vertex colors to the high poly fbx and changing the color_source flag to vertex renders out the vertex colors correctly.  I have tested most of the other bakers through the SAT with no issue after updating the new flags, but mesh_colors seems broken both in Designer and through

I can launch and use Substance Designer 2025 and Work with it. 3D View renders normal. But as soont as i try to resize/reopen the 3D View Panel, SD crashes.If i close 3D View, i can resize the other Panels.I tryed switching Render engines, Updatet my Drivers, Stopping the Render engine before resizing.Always the same result. Can’t get it to run. Im Using Adobe Substance 3D 2025 Standlone Steam edition. Version 15.1.2

The version 15 update introduced updated versions of some noise nodes. The problem is that the scale input of the gaussian noise node is now hard clamped to 64, whereas before it was possible to override the range to scale it to values far above that limit. This feature is necesary to achieve a lot of effects without needless workarounds, and also unnecesarily breaks old graphs using the gaussian noise node with higher scale values

Running into workflow blocking issues with Designer Baker UI. SImilar issues were previously present in Painter, but have been fixed.When relative to bounding box is unchecked, parameters which should be set to physical scene units (cm) and be well above 1 or 100 cannot be set. The UI prevents the user from supplying WS values.Ambient Occlusion, Curvature, and Thickness may be affected. I’ve only tested AO  

It seems that using document channels in filters are broken - they are not picked up and the default value on the node is used instead.Here I have started with the ‘Specific filter’ template and use the roughness channel as a mask for a blend:In painter: roughness channelApplying the filter:basecolor is NOT affectedusing another texture as maskUsing another texture works fine: I was trying to use the user channels and not roughness but then I noticed that not even the default channels seem to work.If this is a user error, please let me know! (if it is, it might make sense to raise a warning !!)This is using the latest versions of Painter and designerSubstance 3D Painter, version 11.1.2Build 5115 - 5faba39802156445fcb0e2b9673b9805f16bd43515.1.1 build 10305 commit 12408c79 Release (01/15/2026) Thanks for looking into this,seb  

Hello, I'm having trouble using any painter channels within a 'specific filter'(https://helpx.adobe.com/substance-3d-painter/content/creating-custom-effects/channel-specific-filter.html )For anything I try, not the channel in Painter but the inputs default value in the designer graph is used.I wanted to use the user channels initially but failing that I tried to simply make the Specific Filter - Painter sample work, but here the same thing happens.This the small modification I made to the sample, using the roughness channel to blend the base color with noise): Roughness channel:Result (should use roughness but uses white value from graph): I checked with others who experienced the same issue. It might still be a user error, but if it is, it might be good to make it more obvious that something is wrong 🙂 This is using the latest designer and painter versions:Substance 3D Painter, version 11.1.2Build 5115 - 5faba39802156445fcb0e2b9673b9805f16bd43515.1.1 build 10305 commit 12408c79 Relea

Baking textures on Mac and PC has a different outcome and I really don’t know why. Is this an Apple Silicon Problem?   Rendering on a MacBook Pro M3 Max 64GB RAM, macOS 15.7.3 all renders (HDR) are darker, especially the Bent Normals and the Normal WS passes are almost black   Rendering on Windows 11 with an GeForce RTX 3060 all looks fine. Please see attached images.

Hello,I am running into an issue where the textureTransfer bake doesn't preserve the alpha of the texture.  I am fairly certain this used to work.  Is that a bug, does the new baker not support alpha transfer, or am I just overlooking something somewhere?  I was running throught the SAT, but it also just results in a white alpha channel when baking manually in designer.Thanks,Chris

Hello, My Substance Designer crashes every time I try to open a new or old scene. I tried several methods to fix it that I found online, but nothing worked, and I am out of solutions. What I've tried:- Completely uninstalling and re-installing SD           - With a clean wipe- Updating Graphics Driver to the latest version- Switched to Studio driver - Switched to Intel iGPU for a test- Renamed several folders to reset the settings- Paused the OneDrive sync- Checked the log but didn't get much from it. The image includes my email address, if it makes it easier for you to locate the crash logs I sent. Thanks,Raz

! pops up when use the directional warp node.

Limited testing so I could be wrong.I noticed sometimes ctrl+B doesn't work to open the Export Outputs window for some graphs. I noticed whenever I edit the Pattern field from its default settings, ctrl+B stops working, even when I change it back to the default $(graph)_$(identifier)  i.e. this T_  

While works fine in 2023 Steam version and also works just fine  in Adobe subscription  version ? I love my Steam 2025  version because I have all my favorites, custom tools  and project settings there .      I had w10 extended security update  before I  first  noticed that 2025 Steam  15.0.3 version  issue  :right click menu shows something , but next left click to confirm do nothing at all.  My guess Microsoft  update might be  a culprit   since I saw no Designer updates  recently .  I would be appreciative  for any advice .

Thanks to your reports, we've established a conflict between Discord's Game Overlay and Substance applications.   We're currently looking for solutions, but in the meantime, if you're facing functionality issues with Designer/Painter buttons, please disable Discord's Overlay.  

tried different setups, Sbsrenderer can only render up to 8192x8192 resolution, which is quite not enogh. Please help.

So not all of the UI responds to mouse actions in Substance 3D Designer 14.1.2 Steam Version. A few days ago everything was working just fine. I’ve noticed that all commands execute normally when launched via keyboard.