Can we get rid of the error you get for having an SBSAR file in a project?

It’s been a while since built-in support for Substance was removed. But if a project contains any SBSAR files, you still get this console every any time you open Unity:

Can we turn off this error please? I’d just like to have control over how my content is organized. To that extent, I like to have my SBS, SBSAR, and the resulting exported textures all in the same place. But because of this error, it means I need to put my SBSAR files somewhere else, outside of Assets, which is annoying.

If Unity isn’t ready to completely get rid of this message, can we add some kind of “Scripting Define Symbol” entry to suppress it?

Also note: I don’t want to use the Substance Plugin. I’m not trying to make use of SBSAR files within my project. I just want the option to keep my SBSAR files in the same directory that contains my SBS files and my textures, without Unity spamming errors.

In the mean time, pro tip (maybe you don’t know about it): if you can put them in a separate folder, and you don’t have anything in the same folder to import into your project, put a ~ at the end of the folder name. Unity will ignore the folder, it won’t try to import anything from there.
So Assets/Sbsars~ for example will be completely ignored. Obviously it’s not the same, but one step closer.

1 Like

That’s really interesting. Thanks. I don’t mind sticking the SBSARs in a subdirectory. Much better than my current approach.

1 Like