I’ve imported a substance package into my project. Using the materials and maps all works fine. The issue is when I’m reopening the project, all the substance materials do not display correctly. I can’t tell if the system is trying to use a previous version of the materials or if it just buggy (I’ve made a lot of adjustments to these substances). Anyway, right clicking the Substance Instance Factory asset and selecting “reimport” fixes all the issues.
However, the engine won’t let me reimport the asset until I’ve had the project open for some period Time, usually around two minutes it seems.
It’s not a horrible bug, but it is rather inconvenient.
Thanks
I’ve found that sometimes when that happens I need to resave the assets before closing editor. It’s not the best solution but it works. I figured it out because every time I edited one the star would reappear in the content browser.
Hello GaryDoesThings,
I have a couple of questions to clarify what you are doing.
1.) Are these files from Substance Painter or Designer? Is this a packaged SBAR file?
2.) Would be willing to share the files in question?
3.) Would you link your DxDiag (System Spec’s)?
After I have this information I will continue to investigate this issue?
Thank you for providing the files and a link to your DxDiag. I ran some tests with your files. I applied some materials in viewport and re built the lighting. I then saved the project and reopened. I do not see any difference in the viewport or the content browser.
I ran these tests on a Windows 10 machine. What specifically about your materials do not display correctly?
Would you provide some screenshots illustrating this issue.
The materials seem to be darker and interact with the lighting in a strange way. Almost as if it the metallic channel were augmented somehow.
Before
After
There were no changes to the level nor lighting builds between these two screenshots. Just before and after I reimport the sbsar. Ignore the tile seams on the after picture, that’s expected behavior at the moment.
Thank you
Interesting. I did not see this within my test.
Please make a copy of your project before trying this
Deleting your Intermediate, Saved, and Derived Data Cache from your projects root folder(main folder where you project is saved) will force your project to rebuild it’s base files. This will cause your shaders to recompile the next time you open your project. This may fix the issue by cleaning up any information that your project is trying to load that is older than the current information.
Let me know if this fixes the issue.
I could not find a “Derived Data Cache” folder in my project, but I deleted the other two folders. I still had the same thing happen. I’ve imported other Substance packages since and they all appear to load just fine. So it may just be a one-off fluke of an issue. Ultimately it’s not a major issue for me as these particular material assets are easily replaced. So unless you think it’s indicative of a larger issue, I’m willing to just cut losses.
FYI - This is a major issue with Source control. The substances get checked in with the previous, older versions of the substance. This makes it a major bug.
Hi GaryDoesThings and Clapfoot -
Are you experiencing this issue specifically with source control and if so, what type of source control are you using?
Note: I re-tested the initial issue and was only able to replicate the issue if I changed the Substance Graph Instances and saved the Graph, but did NOT save the resulting changes made to the textures in the editor. However that would be expected behavior as the changes to the uasset textures were not saved.
Thank You
Ketchum
