Spine runtimes crash UE4 Editor on opening the map.

Nantuk

My UE4 version is 4.15.3 (latest non-beta version). I have a UE4 map with a spine object in it (the "powerup" example provided by Spine) that was exported by Spine 3.5. I updated the Spine Editor and Spine runtimes for my project to the latest version, 3.6, and upon opening that map, the editor crashes. I tried replacing the exported "powerup" example with a newly exported version of it from 3.6, but it still crashes upon opening that map file. To fix it, I reverted Spine back to 3.5, opened the map file successfully, deleted that "powerup" spine object from the map, saved it, then updated back to Spine 3.6, and now the map file opens successfully. It was ok this time, since I am just starting to integrate spine, but eventually, one might have dozens of spine objects in the scene, and a crash like this would devastate production. Please let me know if you have any ideas as to something I may have done wrong, or some way I could have fixed this without reverted and deleting, or if the fix would be on your end. As well, if you need more info, I'll try to provide it.

Here is the stack trace given by the "Unreal Engine 4 Crash Reporter".

KERNELBASE
UE4Editor_Core
UE4Editor_Core
UE4Editor_Core
UE4Editor_RuntimeMeshComponent_Win64_DebugGame!URuntimeMeshComponent::SerializeRMCSection() [e:\code\unreal projects\blank1 4.10\plugins\runtimemeshcomponentplugin\source\runtimemeshcomponent\private\runtimemeshcomponent.cpp:2071]
UE4Editor_RuntimeMeshComponent_Win64_DebugGame!URuntimeMeshComponent::SerializeInternal() [e:\code\unreal projects\blank1 4.10\plugins\runtimemeshcomponentplugin\source\runtimemeshcomponent\private\runtimemeshcomponent.cpp:2003]
UE4Editor_RuntimeMeshComponent_Win64_DebugGame!URuntimeMeshComponent::Serialize() [e:\code\unreal projects\blank1 4.10\plugins\runtimemeshcomponentplugin\source\runtimemeshcomponent\private\runtimemeshcomponent.cpp:1967]
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_ContentBrowser
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_Core
UE4Editor_Core
UE4Editor_Core
UE4Editor_Core
user32
user32
UE4Editor_Core
UE4Editor
UE4Editor
UE4Editor
UE4Editor
UE4Editor
kernel32
ntdll

Nantuk

Mario

Sorry for the troubles! It appears that UE4s serializer couldn't deal with the object layout changes between 3.5 and 3.6. I see if I can future proof this better. Thanks for reporting, I'll add this as a test case for my release tests!

Nantuk

thanks. I should add that if I run in debug mode, it breaks on line 2071 of RuntimeMeshComponent.cpp, being

UE_LOG(RuntimeMeshLog, Error, TEXT("Attempted to serialize a vertex of unknown type %s"), *MeshSections[SectionIndex]->GetVertexType()->TypeGuid.ToString());

where the crash happens because all the "MeshSections" are null.

Mario

Thanks, that's valuable information. Previously, we extended ProceduralMeshComponent. In 3.6, we extend RuntimeMeshComponent. While the two should be compatible, it appears the auto serializer doesn't think so. If we ever change the class hierarchy again, I'll make sure to 1) document it properly and 2) see if there are workarounds. I don't see this happening though, as RuntimeMeshComponent is fantastic.