As the title states we are finding than once a cartographic polygon tool is added in UE5 it cannot be saved. Meaning we can delete it but saving then crashes the editor:
Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\Templates\Casts.cpp] [Line: 10] Cast of CesiumCartographicPolygon /Game/Seattle_Project/Levels/Cesium-BingMapAerial.Cesium-BingMapAerial:PersistentLevel.CesiumCartographicPolygon_UAID_3CECEF77A2E62E2901_1946255554 to MetaData failed
Any thoughts on how to debug this?
We are wondering if this has to do with Source Control/Perforce.
To clarify, you’re experiencing a crash when you save your level after adding a cartographic polygon?
Could you try to replicate the issue in a new project, with just Cesium World Terrain and the cartographic polygon in the level? That will help us figure out if it’s something up with your level/project or the plugin itself.
Sure thing, for us it’s as simple as adding a new cartographic polygon from cesium, then deleting it.
Then saving = crash. Deleting any others that we are using = crash.
To be clear about our project setup we are also using World Partition.
Cesium for Unreal is not currently compatible with World Partition, however it shouldn’t be crashing, so we will look into this.
You mentioned you have already tested on multiple machines, and in multiple different projects. One more option you might try is reinstalling Unreal Engine completely. I’d be surprised if it worked, considering you tested on multiple machines, but it’s worth a try.
To help us get to the bottom of this issue, can you provide additional information about your setup? Specifically:
System information for the impacted machines
Version of Unreal Engine 5 that you are using
Any additional plugins or code modifications that you may be using
You can provide this information to me here or post it directly on the issue.
We’ve reproduced this on multiple machines with dual A6000s and RTX3090s and threadripper processors with UE 5.0.2 and 5.0.3 and the public github of 5.1
The crash happens with the polygon likely because it spans multiple load stream zones in World Partition and the one file per actor/external actors part of world partition can’t work with this.