You don’t seem to have any debug symbols, so the call stack doesn’t have much information. But the presence of “DisplayClusterEditor” implies you might be using the nDisplay plugin. We’ve previously seen some incompatibilities with that - due to that plugin and the Cesium one using similar third-party libraries, but different versions of them - so it may be worth trying to disable that plugin and see if it helps.
okay…I deactivated the ndisplay plugin, which I’m not sure why it was even on. However, now my project file crashes when I attempt to open it! Not good. anyway I can reactivate the plugin so I can open my project file?
i was able to recover the project through perforce, but I had to reactivate the nDisplay plugin to get it to work… Unfortunately, this puts me back t square one. Anyway I can deactivate nDisplay without crashing the project crashing ? Any help on this would be appreciated.
I tried enabling the nDisplay plugin and capturing a movie with the sequencer in 5.0.3, and it seemed to work ok, so I’m not sure yet what might be going wrong for you.
Which version of the Cesium for Unreal plugin are you using? Do you have this problem with the Cesium for Unreal Samples project as well, or only with your own project? What platform are you on? Can you install the Unreal Engine debug symbols so that we get a more useful call stack?
Yeah the call stack is much more helpful now that you have debug symbols. Can you tell me exactly which version of Cesium for Unreal you’re using, though, so I can match up the line numbers? You can find the version under Edit → Plugins.
Yes we release a new version at the beginning of each month. Sometimes more often if there’s an important bug fix. I don’t expect the upgrade to fix the problem you’re having, but it’s certainly worth a try.
But with your call stack and v1.15.1, the crash is happening on this line:
Honestly, that doesn’t make a lot of sense. It’s just using Unreal Engine’s built-in Actor iteration mechanism to loop through the Sequences in your level. I’d be looking for some kind of memory corruption - not necessarily related to the Cesium plugin at all - that is making basic operations like this unreliable.
Can you reproduce this problem in a minimal level that you can share with us? That’s probably the only way we’ll be able to debug it.