I am upgrading a project from UE4.27 to UE5.0.3, but every time I attempt to open the project in 5.0.3 it crashes. The only way for me to avoid this appears to be to disable the substance plugin before upgrading. If I re-enable the plugin after upgrading then the project begins crashing on startup again.
This is the crash message:
Fatal error: [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\GenericPlatform\GenericPlatformMemory.cpp] [Line: 221] Ran out of memory allocating 11601047749729923958 bytes with alignment 0. Last error msg: The operation completed successfully..
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_SubstanceCore!USubstanceTexture2D::SerializeTexture2DMip() [D:\build\U5M-Marketplace\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\Substance\Source\SubstanceCore\Private\SubstanceTexture2D.cpp:181]
UnrealEditor_SubstanceCore!USubstanceTexture2D::SerializeCurrent() [D:\build\U5M-Marketplace\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\Substance\Source\SubstanceCore\Private\SubstanceTexture2D.cpp:117]
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll
I am unsure what is causing this, or what I can do to remedy it. Any guidance or assistance woiuld be appreciated.
Converting to 5.0 gives an impossibly large memory error, and 5.2 gives a serialization error. I’m not sure if these issues are separate or stem form the same source. Either way I’m not sure how to approach them aside from deleting all substance files and reimporting them. I would like to avoid that if possible however, as this is a huge project. I’ve also tried the usual solutions of deleting the build folder and saved folder.
That was good suggestion, but unfortunately it looks like migration isn’t an option either. There is some additional info in the crash report, but I am unsure if it is relevant to the core issue.
I found the issue. I had two invalid substance 2D textures in my project file. It took me some effort to hunt them down, but now that they are removed the transition is happening smoothly.
The invalid textures had a few things in common. They did not update if I made a change in the substance factory, and when I opened the texture there was no image displayed. It did say it was invalid somewhere (after opening the file) but I do not remember where in the UI that message was located.
I found them by migrating different sections into a blank 4.27 project with the substance plugin activated and then attempted to open it in 5.2. (I always had to made sure that the substance plugin was still enabled if the opening in 5.2 was successful. There where a few false positives because of this.) I had a specific process to make it a bit more efficient, but I don’t know that it bears repeating here. Basically I did it by process of elimination. You could also look into using Unreal’s asset/data validation tools - I do not have any experience using these, but I imagine they are likely designed for scenarios like this.
