Feature Requests

When having several graphs eligible for publication as SBSAR into a same package, it is currently not convenient to select which one will be published. We have to make sure each graph is disabled for publication and only the right one is enabled. To make selection of the published graph more convenient, I'd suggest the following:In the dialog shown when publishing a graph (named "Substance 3D asset publish options"), add a checkbox in front of each exposed graph, only the graphs checked will go into the sbsar.By default, checkboxes will be checked for graphs having publication enabled in their properties. Unchecking the checkbox into the publishing dialog will not change this property, the effect would only be local for this publication.Add butons to check/uncheck all graphs in this dialog box.

Allow nodes in the graph to be toggled off/on without breaking the data flow—meaning the input connection passes directly to the output of that node, effectively skipping its operation but not severing downstream links.

The cooking process makes the reactivity of a graph significally slower than its "cooked" counterpart (sbsar running in other app than Designer). This makes the process of testing a graph (editing its parameters) much slower in Designer than in other platforms. I would suggest to add a "cooked" mode in Designer that would enable to test our graph with the best performance, provided the graph would not be editable in this mode. An alternative could be to open the cooked version in another app (Viewer?) with a single button click. I would like to avoid the tidious process of building the sbsar then opening another app and opening the sbsar.

Similar to Substance Painter, it would be helpful to be able to save UI layouts and designate which one you want by default.An example of this being useful is when using a single ultra-wide monitor I regularly switch between 50/50 split windows, and 70/30 split windows, and depending on which screen layout I'm using, is how I arrange/scale my Substance Designer windows.

It would be incredibly useful for validation tooling (in studios) to be able to select a list of nodes via the python api. Example being - running validation on a graph and finding nodes that don't match some specification and being able to select the nodes so a user can address them in whatever way is necessary 

It would be nice the Designer API enables plugins to add content to the app's context menus, like on nodes, graph objects and maybe other items.

Hi everyone,I'm currently working with Substance 3D Designer 14.0.0 and trying to write a Python script to automatically modify a parameter (e.g., a "Scale" float) and export a sequence of outputs from a specific Output node (with the identifier basecolor).However, I've run into a major issue: I can't seem to retrieve the graph object via the sd.api module.Almost every method I tried from the documentation—like sd.getContext(), getPackageMgr(), getGraphFromIdentifier() —returns an error or doesn’t behave as expected.It seems that either the API structure has changed in this version, or something is missing in how the Python environment is initialized. As a result, I cannot even access the graph object, which blocks all downstream operations like modifying parameters or exporting outputs.Has anyone successfully used the Python API in 14.0.0 to access the graph and automate exports?If so, could you please share how you set up the script environment and retrieved the graph?Thanks in advan

I have the need to use substance 3D Designer to make sequence frames of special effects. I hope to export sequence pictures in batches during the process of changing parameters of a node to form continuous special effects. I also used ChatGTP to try Python to solve this problem, but I could not solve the error when I called the API. I am a Chinese user, so there may be errors when using the translation software for the above words. I hope you can get a reply

I'm working almost exclusively with the Pixelprocessor and FX-Map Nodes in Designer, because these Nodes are fantastic to create custom tools and effects. But lately I'm touching the limits of both Nodes very frequently. I try to find workaraounds and hacks, which is fun but it brought up the idea of this feature in Designer.   The Scripting - Node   Let's call it Scripting Processor which actually allows the user to load a script and the Node compiles this into a "Pixelprocessor" or "Shader" like Node.   Blender has a similar Node for the Shader Editor (Open Shading Language - Blender 4.3 Manual) which is fantastic, for shaders. In Substance Designer it should have more the behaviour of a Pixelprocessor, but instead of the Substance Function Input (which is unfortunately sometimes very limited, when it comes to complex functions) it could load a scripting file, which allows the user to create very complex nodes. It doesn't have to OSL it also can be GLSL or even py

It's so annoying  to relocate files one by one.    Make an option to relocate all files from same folder at once please.      

When adjusting parameter values in Substance Designer with the mouse wheel, turning it normally changes the value in 1/100 increments, and holding the Ctrl key adjusts it in 1/10 increments.It would be great if there were an option to adjust values in 1/1000 increments as well—for example, by holding the Shift key while scrolling.

Could you please add callbacks to the Python API when a new package/graph is loaded/created/removed? There are such equivalent in Painter where we can be notified of various events related to the project content/creation/loading.

I often need to save  8 bit tga for a game and  16/32 bit  pngs for archiving and using as input for other materials .   Would be really nice to have it Designer .

It would be great if we could specify colors for referenced graph nodes from other graphs in the current graph in Substance Designer. Currently, referenced graphs are displayed in the same red color (#a21318) as default nodes, which is not very intuitive.While allowing users to customize the color would be ideal, if it disrupts the consistency of the user experience, it would be better to represent them with a distinct fixed color instead.For example, a highly saturated red color like #f01c24, similar to the bright green (#86f047) used for sbsar nodes.

 Hi, I was wondering what would be the best way to recreate this kind of texture? Thanks

focusGraphNode() is only focusing on SDNodes, can you please extend the functionality to focus on any graph object (i.e frame, pin, comment etc.)? 

Hi Substance team!Loving the new Substance Designer 14.1 update!One feature that I was really excited about was the alignment tools, but I find them a little bit hard to use right now. I am often selecting the bunch of nodes I want to align, hovering over those new icons and see which one I need to pick, click it and then repeat.It would be much better to have them appear in the Shortcuts panel to assign our own shortcuts to them.Personally, as someone who is working in Unreal, I am used to the Shift+WASD for the alignment of nodes and think that if it doesn't clash with any of the current keyboard shortcuts, this could be a good default keyboard shortcut for it. But the option to change them should still be there.I'm sure anyone working in Designer would agree with this!Thank you!

It would be really useful if there was an 'export all graphs' or 'export selected graphs' option. If I have a substance file with a bunch of graphs that I need to batch export, I'd like to select them all and do export selected, or something similar. I don't see any way of doing this and you need to run through them all one by one exporting, as it currently stands.

When exporting textures the export window stays open afterwards, and the program will not take any more inputs until it is manually closed. I do not see the point, it's just an extra bunch of clicking for no reason. Can we have an option to make the window disappear after you've exported and you can carry on. This might not seem like a big deal but with no option to batch export graphs you find yourself having to constantly close the window and it's just redundant clicking.

At the moment if you have let's say 3 texture nodes and you want to set a common property, such as, 'relative to parent' for example, you need to click the texture, change the properties, go to the next texture,  click it, change the properties, etc...As they ALL share this common property why can't we just select all 3 nodes and change it once and have it apply to all of them? This applies for just about anything in the properties panel, this would be a great feature in my opinion, color/grayscale etc, etc. 

Currently I see nothing like in game when set material roughness  in Designer.    That "panorama" default background  HDRI produces  so dull highlight spot for the sun being only 16 degree high  I wonder how anyone could call it Phisycally based.    I know we could check in iRay to get more adequate look but  why we couldn't just have same "ultra" settings  like in PAinter.     I constantly do  darker roughnes than necessary due to so dull preview in 3d pane.  

Like one in Photoshop color settings.    I can't export areas of a texture supposed to have specific gray values in -game  shader  is needed  without some exte noise.      It's too tiresome to fix it in Photoshop .      If anyone knows a workaround  please share.   I tried to posterize the result in 255 steps before converting  to 8 bits.   Looks ok  in 2d view   but again  noise after export.

Issue: Packed maps are not displaying correctly in the 3D view as intended.   Details:In my case: ORM Map: R = AO, G = Roughness, B = Metallic Normal + Height Map: RGB = Normal, A = Height (or RG = Normal, B = Height) While the full texture is correctly applied to the corresponding material property, the specific channels (e.g., R, G, B, or A) defined in the Output node's "Usage" tags panel are not being used as configured. Instead, the entire texture appears to be applied indiscriminately.   Steps to Reproduce: Right-click in the node canvas and select "View Outputs in 3D View." Each output routes to the correct material parameter (e.g., AO, Roughness, Metallic), but the individual channels specified in the Output node's "Usage" tags panel are not isolated as expected. This can be observed in the accompanying screenshot.   Relevance: For game development, utilizing packed maps is a standard optimization technique to minimize texture memory usage. Accurate channel ma

I'm creating quite a few materials with exposed parameters using the Painter Filter (w/ additional mesh maps) template. This works great, as I can load a model in, bake the relevant maps (usually AO & curv), fine tune everything, then replace the baked images with my inputs and export to Painter. However, if I want to tweak anything after, I have to go through the process of swapping the links back to the bakes, editing, back to exposed parameters, export. Since all of these inputs are empty (black/trasnparent) by default, it would make a lot more sense for SD to default to your baked maps as an override to these inputs, or at least offer the option to.

When you edit a function, pixel processor or sub-graph   would be nice to have slelected  top level  sliders always be  available as on screen widgets so you can chang the math  or blending and istantly check how would it respond to  top level changes without necessety to go up and down all the time.   I mean from value/pixel processor to main graph and back .