Cesium causes hundred of errors when shifting from Binary to Source Unreal

Hey,

Pretty much all is in the title …
Changed version (From Unreal 5.3.2 Binary from epic games launcher, to Unreal Source Build 5.3 from their github) to avoid packaging errors, but now I have errors comming from Widget.h, UserWidget.h, ScreenCreditsWidget.h…
If I disable the plugin (from the .uproject file), there are no more errors.


Most of them are “Can’t instance abstract class”, or "syntax error ‘)’ "

Pretty new to cpp as I use only blueprints, so don’t really know how to fix it (if it is possible)

Hi @Asityx, welcome to the community!

We only test with official builds from Epic, but I don’t know of any reason that source builds wouldn’t work. You’ll have to build the plugin yourself, though. The easiest way to do that is to remove it from the Engine Plugins directory and include it in the project’s Plugins directory instead.

As for those specific errors, I really don’t know. Many of those header files you listed are Unreal-provided, not Cesium headers at all. To have a guess, I’d probably need to see the complete build log (preferably as text, so I can translate it if necessary). The problems tab tries to summarize the problems, but often tends to obscure them instead.

Hi Kevin,
Thank you for your reply,

I will try to manually include the plugin as you said.

Here are the 2 build log files, the only thing I changed between the 2 of them is value of “Enabled” of “CesiumForUnreal” in my .uproject (expiring on 08/31, let me know if you need them again)

https://filesender.renater.fr/?s=download&token=ba77062b-556b-45f1-9831-d9b3b592c302

Thanks.

Hi again,

Just to let you know, including the plugin in the project’s Plugins directory didn’t change the outcome, and I still have those errors, in which Cesium is explicitly involved in 4 of them. (Even though I suppose they all are related between them)

Hope this can help, let me know if you need any file in addition.

Well I took a look at your log, and I don’t know what to say other than nothing appears to be working at all. My best guess is you’re missing essential components for your Visual C++ installation, or it is somehow corrupt. There are all kinds of errors about very basic headers missing that are usually included with the C standard library (like stddef.h). Are you able to compile Unreal C++ code at all on this machine? Epic has lots of information about setting up your Visual Studio environment for Unreal here:
https://dev.epicgames.com/documentation/en-us/unreal-engine/setting-up-visual-studio-development-environment-for-cplusplus-projects-in-unreal-engine

By the way, in your “Success” log, a lot of these same strange errors occur, but then I don’t see it ever actually trying to build any C++ code. So the fact that it “works” before you enable Cesium doesn’t necessarily prove the problem is with Cesium. It’s just that enabling the Cesium plugin forces your computer to compile C++ code, which it seems unable to do.

I doble checked the installation and it compiles just fine. I tried to clone CesiumSamples project, build it with the source version and it worked and I was able to open project in unreal, so C++ install should be fine.
I guess my first project might have outdated build settings or something. I’ll take a look.
Thanks again