Hello! I'm having an issue where every time I open my document an rgb-a_split.sbs dependency can't be found and needs to be located, and it's looking for it in an old version of the project. I use that node several times in my file, but theres one that has 0 occurances and the path never saves. It always reverts to that old location. When I right click and select remove, nothing happens. If I right click and select update, it lets me relocate the sbs, but the path doesn't update in the dependency manager and I keep getting the prompt to locate it when I open my working document.
I'm also wondering why there are so many of this node listed in the files column, should it just be iterated in the occurance column? Lastly, I see there are some listed as rgba_split.sbs and some are listed as rgb-a_split.sbs. As far as I can remember I'm just adding these nodes using the UI in the substance graph.
Sorry, I may have spoken too soon. Closed the file and reopened and this time it was resolved. I need to keep better track of these issues so I can get you the proper infortion, because I've been having this problem a lot.
I also realize now that rgba_split is a different node than rgb-a_split. Still curious why the rgb-a_split nodes are listed multiple times. There are others like this in the list. Some follow a path, and others are located at sbs://
It would be nice to just reference the nodes at sbs:// rather referencing a duplicate elsewhere. I'm sure theres a good reason for this. Any help understanding would be appreciated. Thanks.
Thank you for the detailed post. Indeed, when dependencies are removed from a package using the Dependency manager or by removing all nodes referencing it, it is safer to then reload the package.
All dependencies are loaded along with a package, and they are still loaded after removing them through the interface. Thus, they may still be detected as loaded and referenced by the package at that time. Reloading the package unloads and reloads dependencies, which forces an update of what is referenced in the package.
We understand this is confusing, and we are working on ways to both handle dependencies better and give users a better way to understand and control them.
Regarding the rgb-a_split node dependency issue you described, I can take a look at the Substance 3D file (SBS) referencing them and try to understand what happened. Can you share that file?
Luca Giarrizzo | QA Analyst, 3D & Immersive | Adobe