Substance 3D Designer

When an SBSAR has embedded presets containing boolean parameters, these are not being set properly in Designer when enabling those presets. Works fine in SBS and in SBSAR in other hosts, but not for SBSAR being used in Designer.

I've made a decal material for Unity with a series of custom inputs for the user to control, with one of them being a float slider to determine the value of the height mask. However, when I import to Unity, every input is visible and working except the height slider, which doesn't even show up. Is there something I'm doing wrong? Or is it because it's a decal material?

Hi! Since the latest update I can no longer send substance model graphs to Stager. If lathe is used anywwhere in the model, Stager just recieves/produces a lowpoly ball. 

About 2 years ago I created a bat file that uses the Substance Automation Toolkit.When I update the .sbs file that the bat file references with the latest Substance Designer, I get a warning and can no longer process the file.When I update the Substance Automation Toolkit to the latest (Substance_Automation_Toolkit_Pro-12.1.0-1081-msvc14-x64-adobe), I get the same warning.What should I do?  b'[WARNING][SBSMutator]Application is too old to open URL\r\nURL : "file:///D:/****.sbs"\r\nCurrent application manages format version "1.1.0.202201" instead of "1.1.0.202204"\r\nCannot load: D:/****.sbs\r\n[ERROR][SBSMutator]At least one input file cannot be correctly loaded.\r\n[ERROR][SBSMutator]Terminating...\r\n'  

Hello. I noticed that several of my graphs, which I created from scratch with no element pulled from anywhere else, somehow end up locked, and I can no longer edit them. That usually happen after I've published the sbsar, and it's not consistent or happens immediately after the publishing (I can actually republish several times, edit, and suddenly, it's locked). Is there a way to unlock the graph since I'm the author, and what can I do to prevent this from happening (other than keeping several copies in case one gets locked, but it's too late for some of my work). Thank you.

Here :It is NOT the same issue as seen here :https://community.adobe.com/t5/substance-3d-designer-discussions/exposed-parameters-in-dependency-not-show-up-in-main-graph/m-p/12771040 I do have read the documentation, all "glitched" exposed parameters come from an Histogram Range, which is not limited. They're regular floats like any other float.I can see all exposed parameters I exposed last week, but since today, I can't expose anything. Not a color or any float, nothing more exposes.What is happening here ? (Using Substance 13.2.0 build 6140)

The resolution/bit depth text in the Blend - 2D View is black and unreadable against the background. Please FIX!!!! Version 12.2.1

Thumbnails are not updated and images cannot be exported.Also, the 2d view is not updated even though the display output is pressed in the 2d view. You can't even export images. I tried reinstalling it and clicking Recreate Thumbnails, but it didn't work. It's been working fine until now, and when I put together a heavier and more complicated node than this, it worked fine, so I don't think there's a problem with the computer's machine specs. Please let me know if there is a solution.

I have a full RGBA exr with alpha.  The alpha only appears pure white.If I import the full RGBA as a psd, I DO indeed see the alpha data. Am I missing something for getting an EXR alpha to come through on import?

hello, i have photogrammetrated an object in metashape. created a high poly mesh (30mio faces) with texture. imported this into blender and created a low poly. i set the scale to 1 in each case. then exported both again. in designer i now want to bake from the hp to the lp. i bake height, normals, ao, and texture. normals are baked very quickly, but the map remains black, the ao remains white. the others work. what could be the reason for this?

I’m not sure why I can’t even open my project to fix the issue. but I get a pop up window that says “substance failed to load” when i click ok or hit the close button it wont go away. It wont let me exit this warning so I can never even open my project. I can't even quit out of cinema 4d its stuck on this error message.

Just recently the program would crash and close everytime I would open it. I reinstalled and restarted numerous time and the issue continues. Is there another way to fix this?

Hi gang,I'm diving into functions and I think I've discovered a bug with the comparison routine:So the greater than compares "a > b", so in this case it tells us that -15 is higher than 10. Because the outcome of this is -15, not the expected 5. Proof of concept graph is attached. The moment I instance this I get -15. Also tried to re-start Designer, the moment I open it again and load my package.. -15.  Finally: still somewhat new to functions (but digging in quite deep ;)) I also set up a scene where I didn't re-use the -15 integer: same results. I suspect a bug, can someone reproduce? Thanks for reading & any possible feedback!

I recently bought a substance designer, installed it, did not change anything. I loaded a standard material into the graph and in 2D and 3D form some kind of white image/material. In Library brown color in my 2d/3d view much more brightness My friends, who are on the old version of the substance designer, do not have this. What I must do? What is it. Why is it? And why is it in the default setting.

In the latest build (12.2.0 Build 5912) I am having issues of nodes that are 16-Bit with 16Bit inputs output 8-Bit results randomly.(Windows 10) No noticed node in particular, have confirmed with Blend node, Slpoe Blur and Non- Uniform blur. However it is not consistent - When I notice it has happened, I can copy the node and find that the copy works fine (shown in attached example).I have been working mostly in 4k.I went to test 2k to see if the issue still occured, and found that after changing to 2k, some nodes are not updating resolution either - example attached.Please advise if there is a fix / if other info etc required.Thanks!Stan Brown  

I have a fairly simple brick wall texture, but when going to publish, I get the following:SDApiError.ItemNotFound [MSG][1578][CompGraphModel]Infinite Loop Detected: [MSG][1579][CompGraphModel] 'pkg:///Substance_graph?dependency=1451679580' already contains current function. [ERR][1580][Python]Traceback (most recent call last): [ERR][1581][Python] File "E:\Productivity/Adobe Creative Cloud/Adobe Substance 3D Designer/resources/python\designer\appinterop\appinteropui.py", line 190, in __onActionTriggered [ERR][1582][Python] [ERR][1583][Python]self.__callback() [ERR][1584][Python] File "E:\Productivity/Adobe Creative Cloud/Adobe Substance 3D Designer/resources/python\designer\appinterop\appinteropui.py", line 476, in __onPublish [ERR][1585][Python] [ERR][1586][Python]dialog = SBSARPublishDialog( [ERR][1587][Python] File "E:\Productivity/Adobe Creative Cloud/Adobe Substance 3D Designer/resources/python\designer\appinterop\sbsarpublishdialog.py", line 521, in __init__ [ERR][158

when i run this command over CMD"C:\Program Files (x86)\Steam\steamapps\common\Substance 3D Designer 2022\sbsrender.exe" render E:\WorkSync\Infusion\Tech\expandMargin.sbsar --input-graph expand_margin --output-name $Concrete_Hallwall_0_Straight_Outer__n --output-path E:\Development_2\Workspace\Timelapse Vertigo\Data\Locale\Sprites --set-value '$outputsize@12,10' --set-value '$randomseed@0' --set-entry mask@E:\Development_2\Workspace\Timelapse Vertigo\Data\Locale\Sprites\$Concrete_Hallwall_0_Straight_Outer__h.png --set-entry unbleedTex@E:\Development_2\Workspace\Timelapse Vertigo\Data\Locale\Sprites\$Concrete_Hallwall_0_Straight_Outer__n.pngI get[ERROR][SBSRender]Input file "Vertigo\Data\Locale\Sprites\$Concrete_Hallwall_0_Straight_Outer__h.png" cannot be read : The system cannot find the path specified.how to handle white space in the set-entry

Hi!Cliking on publish sbsar file does nothing.I got severals issues in the console. I've not been able to find a solution yet. Some help would be much appreciated.[ERR][1272][Python]Traceback (most recent call last): [ERR][1273][Python] File "C:/Program Files/Allegorithmic/Adobe Substance 3D Designer/resources/python\designer\appinterop\appinteropui.py", line 190, in __onActionTriggered [ERR][1274][Python] [ERR][1275][Python]self.__callback() [ERR][1276][Python] File "C:/Program Files/Allegorithmic/Adobe Substance 3D Designer/resources/python\designer\appinterop\appinteropui.py", line 481, in __onPublish [ERR][1277][Python] [ERR][1278][Python]pkg, publishParams, self.__uiMgr.getMainWindow()) [ERR][1279][Python] File "C:/Program Files/Allegorithmic/Adobe Substance 3D Designer/resources/python\designer\appinterop\sbsarpublishdialog.py", line 531, in __init__ [ERR][1280][Python] [ERR][1281][Python]if AppInterop.isAnyDependencyModified(package): [ERR][1282][Python] File "C:

I am attempting to use the Distance Node to create a voronoi-like pattern with cells containing different values. The output of the node seems to be artifacting in a matter it should not be compared to outputs I have seen while doing research on the technique. Is this a bug in the current Designer build? Or possible a settings/configuration issue? See screen snip below for example of the (bugged?) output. System specs:Ryzen 5900X, 32GB DDR4 3600, Radeon RX 6700XT, Windows 10 Pro 21H2.  

I have Substance Designer 12.1.1 build 5825 When I use such schemeinput bitmap is in .exr format (32bit float or 16bit half-float) panorama Rotation (all parameters are at default values)blend node with subtract option - there are differences, but the images must be the same! Under differences I mean histogram Used Range values (see below)They are quite big (maybe with this current image), but this is math: if no changes - there must be no difference.If I connect input bitmap to both blend node inputs that range is 0;0, and that is correct.The same error persists in any different resolution and with .hdr format images. Only one thing I've found so far - when inserting exposure node just after the image and make exposure lowering - the error gets smaller too, but it is not 0 in any way. 

Eveytime I open packages I have created and saved I get the update window saying it needs to update but it also says when it's saved it won't do it again, but everytime it is opened it has to update everything, sometimes this can take 10 or so minutes. Is there a solution to this?

Hi,  So I noticed that the option to View Outputs in 3D View after program restart, or scene reload doesn't work for all the machines. It means when the scene is reloaded, you have to manually redo this action for each graph - on some machines.Is this a Designer preferences issues? Also does this option is available in Python API - as we can't find it there.Thanks, Józef 

Hello Substance team, First off, thank you for including sbsbaker in the latest release ! Much appreciated. Question > I am building an python-based automated Substance baking/texturing pipleline system and am seeing a small x/y pixel offset with bakes using sbsbaker between windows & linux. This happens with the older SAT sbsbaker and the new one now included in Substance Designer. Anything I should know here to prevent this ? Any thoughts on why this might be happening ? I'm using the latest version (12.1.1) of Substance on each platform (linux version via steam). Images attached for the same ao bake on each platform. A quick difference overlay will show the offset clearly. Thank you for your time. - Scott Windows 10 Pro 21H2Ubuntu 20.04.4 LTS 

I noticed that Ubuntu 20.04 was the latest officially supported version for Designer.  Is there a plan for official 22.04 support?I am able to get Painter to launch on Ubuntu 22.04, but Designer crashes on startup (on a fresh install too) on both Wayland and Xorg.  Both required me to manually install two libxcb package dependencies to start, but once I was able to do that they both at least hit the launcher.  When Designer crashes, a black window briefly appears after the launcher dialog disappears and then the crash reporter appears.  The logs don't indicate any warnings or errors as far as I can tell.  (I have submitted a proper bug report through the crash reporter).  I have an AMD GPU and with the default (mesa?) drivers.