Hi,
the issue appeared after We upgraded from the Substance Plugin Version 4.24.0.1 to the current version. An upgrade from Unreal 4.23 to 4.24 didn't cause any problems, so it might be related to the plugin itself. We fixed it by downgrading the plugin to 4.24.0.1 from another PC, where we did not install the current version. But I fear the moment, when we upgrade to 4.25...
Hi,
Are you experiencing the same issue as posted above where you are getting a video memory error? We are looking into this problem to see what the cause but the team is needing to find a way to reproduce this. The Substances in your project, are they coming from Substance Source?
I have more information from the dev team.
We are now using UE4's serialization for anything new that is added to the plugin such as utexture2d and material instances. However, we are still needing to do manual serialization of data stored for the Substance object imported. This could cause issues if data was stored differently between versions. We have not been able to completely remove the manual serialization, as it would break some projects across all versions of our plugin.
The way its working with the 4.24.0.3 update.
Assets created in 4.16 or before will be missing data, these can persist if the project has been updated through versions. The missing data can cause issues with the new 4.24.0.3 plugin since we have to update the objects to be compatible with utexture2d and material instancing changes.
Can you please let us know the following?
1. The version number of UE4 the substance materials were first added to the project. Was it 4.16?
2. How much vram does your GPU have?
3. How big are the substance materials in your project? Do they have embedded or nodes set to (absolute) generate high resolutions such 4K?
Cheers,
Wes