If you work with Substance Designer, you probably use SBSAR and SBS files to create and share your materials. But do you know the difference between them and how to export and import them correctly? In this article, we'll cover some best practices for working with these files and avoiding common pitfalls.
SBSAR and SBS are two types of files that Substance Designer can generate. SBS stands for Substance Source, and it contains the source graph of your material, with all the nodes, parameters, and dependencies. SBS files are editable and can be opened in Substance Designer or Substance Alchemist. SBSAR stands for Substance Archive, and it contains a compressed version of your material, with only the exposed parameters and outputs. SBSAR files are not editable and can be used in any software that supports Substance, such as Unreal Engine, Unity, or Maya.
There's very critical information missing from this description. - SBS files are xml, and do NOT contain copies of referenced resources and graphs. - Many of the dependency file paths may be saved with a project specific "alias" which can only resolve to an absolute path when opened in the correct "context" (Designer Project Configuration). - SBSAR files are compressed, but also flattened archives containing all dependencies. These are designed to render in isolation, without the reliance on the Project Configuration / context described above. - SBSARs are usually used in Substance Automation solutions, Substance Engine integrations (DCC plugins), and other Substance Apps like Painter and Sampler.
To export your material as a SBSAR file, you need to expose the parameters and outputs that you want to control and view in other software. To do this, you can use the Expose Parameters and Expose Outputs buttons in the Graph toolbar, or right-click on any node or output and select Expose. You can also rename, group, and order your parameters and outputs in the Properties panel. Once you have exposed everything you need, you can go to File > Export Outputs as Bitmaps or File > Export with Dependencies and choose the SBSAR format. You can also adjust the quality, resolution, and format of your outputs in the Export dialog.
Be sure to create, manage, and maintain custom graph icons. These will be saved in the SBSAR and will be loaded inside of Painter. This will improve library asset readability on your project and will relieve Painter's resource crawler from having to generate icons on the fly.
To import a SBSAR file into another software, you need to make sure that the software supports Substance and has the Substance plugin installed. For example, in Unreal Engine, you need to enable the Substance plugin in the Plugins menu, and then drag and drop your SBSAR file into the Content Browser. In Unity, you need to import the Substance in Unity package from the Asset Store, and then drag and drop your SBSAR file into the Project window. In Maya, you need to install the Substance plugin from the Autodesk App Store, and then use the Substance menu to load your SBSAR file. Once you import your SBSAR file, you can adjust the parameters and outputs as you wish, and apply your material to your meshes.
To export your material as a SBS file, you need to save your graph in Substance Designer. You can also use the File > Save Package As command to save your graph and all its dependencies in a single file. This is useful if you want to share your source graph with other Substance Designer users or backup your work. However, be aware that SBS files are not compatible with other software, and they may contain proprietary or licensed assets that you cannot redistribute without permission.
SBS creation is not an export. It's the result of the application save command. This is an XML file, with very little embedded content. Additionally, it may require a "runtime context" of sorts in order for it's dependencies to resolve in later sessions or in other environments. SBSAR publishing can be considered an export. This flattens the graphs and embeds dependencies. This can be rendered via command line or in engine integration plugins. I generally recommend avoiding "Export with Dependencies". If you find yourself using this, you've likely done something wrong. Usually in one or more of the following ways: - Incorrect library management (project configuration) - In-effective folder structure and dependency management
To import a SBS file into Substance Designer or Substance Alchemist, you need to drag and drop it into the Explorer panel or use the File > Open command. You can also use the File > Import Resources command to import individual resources from a SBS file, such as bitmaps, functions, or filters. However, be careful not to modify or delete any resources that are linked to your graph, as this may break your material or cause errors.
SBS files are opened, not imported. When importing bitmaps, I almost always recommend using the "link resource(s)..." method. This will record the dependency as a referenced file path in the SBS (xml) instead of embedding it. This makes the files smaller, and easier to work with in automation environments.
You can export and import SBSAR and SBS files more efficiently and avoid common problems by using relative paths when linking resources to your graph and using the File > Clean command to remove any unused or duplicate resources. Additionally, you can use the File > Publish command to export your material as a SBSAR file with a preview image and metadata, the File > Export as Template command to export your material as a template for Substance Alchemist, and the File > Export to Project command to export your material as a SBSAR file and copy it to a specific folder or project. These steps will help make your material more attractive, informative, portable, and up-to-date.