User Guide Cancel

Warnings from dependencies | Substance 3D Designer

Warnings from dependencies

This page lists warnings and error messages which may be triggered by dependencies in Substance 3D Designer, and offers common troubleshooting steps for each.

Dependencies are other files referenced by a Substance 3D file (SBS). They include resources and other Substance 3D files referenced by graph instance nodes.


(error) Invalid dependent package

A dependency package cannot be loaded, because it is missing, corrupted or incompatible with the version of Designer being used.

(tick) Solution

There are two main ways of correcting this issue:

  1. Make the dependency load successfully

    Check the dependency package exists at the location specified in the warning message. If it does not, find the file and put it back at that location, or recreate it in place. If the file exists, try to load it in Designer and look out for any warnings or errors related to that package. Refer to troubleshooting steps for those specific issues an fix them accordingly.

    Then, reload the host package by clicking RMB on it in the Explorer panel and selecting the Reload option in the contextual menu.

    'Invalid dependent package' solution 1

  2. Relocate the dependency in the package

    You can relocate the dependency using the Dependency manager . C lick RMB on the host package in the Explorer panel and select the Dependency Manager option in the contextual menu.

    Find the missing dependency in the Dependendy Manager's list, click RMB on it and select the Relocate... option. Find the dependency package using the file browser dialog and click Open.

    Then, reload the host package by clicking RMB on it in the Explorer panel and selecting the Reload option in the contextual menu.

    'Invalid dependent package' solution 2


(error) Check the alias 'X' is defined in your project

One of the package's dependencies or resources is being loaded from a location which is aliased in the Substance 3D file (SBS) data under the alias reported in the warning, although that alias is not defined in the current project files.

(tick) Solution

At least one of the project files should define the alias that which is reported in the warning.

'Check alias is defined' solution


(error) No file that matches this resource can be found

The files matching the UDIM template for a Bitmap resource cannot be found.

(tick) Solution

When a Bitmap resource is linked and Designer detects a UDIM naming taxonomy in its filename – e.g. 0x1 in my_texture_0x1.png, it offers to link it as a UDIM template, so that Bitmap nodes can automatically switch to other bitmaps in a UDIM set using that taxonomy, when using a UDIM workflow in Designer. In that case, Designer links the Bitmap resource in a different way which takes the UDIM numbering template into account.

There are two main ways of correcting this issue:

  1. Restore the files

    Go to the location specified by the resource's File Path attribute and check that files following the template exist. If they do not, restore or recreate them.

    'No file that match resource' solution 1

  2. Relocate the files

    If the files were moved or renamed, relocate them by clicking RMB on the resource item in the Explorer panel and select the Relocate option to link that resource to the first file in a set of UDIM images of the same type.

    'No file that match resource' solution 2


(error) Linked file not found

The file referenced by a linked resource does not exist at the location specified by its File Path attribute.

(tick) Solution

There are two main ways of correcting this issue:

  1. Restore the file

    Go to the location specified by the resource's File Path attribute and check that the file exists. If it does not, restore or recreate it.

    'Linked file not found' solution 1

  2. Relocate the file

    If the file was moved or renamed, relocate it by clicking RMB on the resource item in the Explorer panel and select the Relocate option to link that resource to another file of the same type.

    'Linked file not found' solution 2


(error) Color space not found

A Bitmap resource references a color space which cannot be found in the current color management environment. This may be an ICC profile or a color space in an OCIO configuration.

(tick) Solution

The list of options for the Color space attribute is automatically populated with available valid color space. Change the color space value for that resource to any other entry in the list.

Alternatively, add that color space to the current color management environment, then restart Designer. This may be an ICC profile or a color space in an OCIO configuration.

Note:

This warning is only triggered when using a color management mode other than Legacy (which is akin to disabling color management). You may enable color management in the Color Management section of the Project settings.

'Color space not found' solution


(error) Reference resource not found

The graph assigned to the UV tile of a 3D mesh resource cannot be found at the location reported in the warning.

(tick) Solution

There are two main ways of correcting this issue:

  1. Restore the graph

    Check the contents of the package in the Explorer panel for the graph specified in the UV Tiles list. If it does not exist, restore or recreate it.

    'Reference resource not found' solution 1

  2. Select another graph

    Assign another graph in the package to the UV tile.

    'Reference resource not found' solution 1


(error) UV tiles are assigned multiple times

A UV tile for a 3D mesh resource is assigned more than once to a Substance graph.

(tick) Solution

For each UV set of a 3D mesh resource, make sure no UDIM index is present more than once in the UV Tiles list.

'UV tiles are assigned multiple times' solution


(error) Invalid UV tiles

A UV tile listed for a 3D mesh resource is not defined in the mesh or corrupted.

(tick) Solution

For each UV set of a 3D mesh resource, make sure all items in the UV Tiles list refer to UDIMs which exist in the linked resource.

Note:

This warning cannot be triggered through the user interface, since it only lists the UDIMs detected in the linked resource. Only modifying the data in the Substance 3D file (SBS) directly can result in this warning being triggered.

'Invalid UV tiles' solution

Get help faster and easier

New user?