Started with a 5.1 project, installed cesium, everything ran/built fine, was able to generate a Windows package.
Yesterday, updated to UE 5.2.
Looks like Cesium got updated as well. Also, I have already updated cesium. Still getting the same link errors.
Getting these link errors when I try to do a package in UE, does not matter what level, development, shipping, does not matter.
In Visual Studio, I can only compile with Development Editor. Other build types fail with linker errors as well.
While it says that cesium was updated to cesium 5.2 (and I did update per what this pic indicates), is it possible that my project is using the wrong version? And of so, how do I find out if it is and what is the best way to correct it? Asking about possibly using the wrong version because I noticed that someone else had a linker issue, but ended up being that they had the wrong version.
We build the cesium-native portions of Cesium for Unreal using VS2019. Here are the relevant lines from our CI build that produced the v1.27.0 version:
-- Building for: Visual Studio 16 2019
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.20348.
-- The CXX compiler identification is MSVC 19.29.30148.0
-- The C compiler identification is MSVC 19.29.30148.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped
Visual Studio versions are shockingly confusing, but this article helps:
If I’m reading all this right, we build v1.27.0 with the very latest version of VS 2019.
However, if you installed Cesium for Unreal from the Epic Launcher, you got a version of the plugin built by Epic, not by us. So what did they use? It’s hard to say. Typically they’d use the oldest supported compiler, but there’s really no way to be sure.
So I can think of a few of things to try:
Uninstall the plugin from the Epic Launcher, and install it manually from our releases page. Just in case Epic is building with a newer MSVC for some reason. Releases are here: Releases · CesiumGS/cesium-unreal · GitHub
Make sure you don’t have any older toolchains installed, just in case Unreal is somehow picking up the wrong one.
Thanks for the feedback… I did download Cesium from the epic store. I was able to get past the build error going a different route.
I pulled the Cesium plugin out of the Epic.…\plugins file structure,
I put it in my project\plugins folder.
I deleted all the saved, intermediate etc folders and created a fresh set VS project files
Opened VS build the project
Opened UE 5.2, confirmed that everything ran in the PIE
Then did a Shipping Package Build.
That all seemed to work great.
Then I took the entire plugin out of my project and coped it back into the Epic.…\plugins folder structure.
Deleted the saved, intermediate etc folders
Created a fresh set of VS project files
Retested everything again…
This all worked for me.
I’ll give your method a try as soon as I can as well!
Thank you so much for your support, it’s really appreciated!
(BTW, would love to install VS 2022, but not an option for our org at the moment)