Issue with exposed parameters

[DanHutchinson]

Hi All,

I'm noticing that some of my exposed paramters are not visible via a published .sbsar file when used as a node in a graph however when using the .sbs file as a node in the graph all the parameters are now visible... 

Is this a known issue and if so is there currently a workaround or is it requiring a system fix from the devs?

Thanks,

Dan

[davescm · Accepted solution]

There are limitations on exposing certain specific parameters in SBSAR - see the documentation here (scroll down to see limitations):

https://substance3d.adobe.com/documentation/sddoc/exposing-a-parameter-102400062.html

Dave

[Luca Giarrizzo · Accepted solution]

Hello Dan,

 
As @davescm stated, there are indeed limitations caused by the difference between static and dynamic properties.
 
Some node properties are static, which means they cannot be computed on the fly once the graph is processed (or cooked). A significant consequence of this is these properties – and any parameters which contribute to their computation – will not be exposed in a Substance 3D asset (SBSAR) published out of this graph.
 
These properties still appear as editable in Designer because graphs are recooked each time a modification is made in a stream. However, graphs in published Substance 3D assets (SBSAR) are cooked and compiled. In addition to the link that Dave kindly provided, you can learn more in the SBSAR limitations section of this page.
 
Other commonly encountered static properties are the Blend node's Blending mode and Cropping area, the Uniform color node's Color mode and the Text node's Text.
 
We understand this is a frustrating limitation, which is inherent to the current implementation of these atomic nodes and the Substance engine. I will update our documentation in the coming days to both give this limitation more visibility and flesh out the static parameters list into an exhaustive list. Thank you for your patience!
 
Best regards.