Issue Downloading and Installing Cesium for Unity

Hello Cesium Support Team,

I am having trouble downloading and installing Cesium for Unity for use in Unity 2022.3 LTS. Here is a summary of everything I have tried:

1. Tried Git URL in Unity Package Manager:

Used: GitHub - CesiumGS/cesium-unity: Bringing the 3D geospatial ecosystem to Unity and #v1.17.0

Unity Package Manager either failed to add the package or showed an “update required” message repeatedly.

The Package Manager itself sometimes fails to work in my project.

2. Tried downloading .tgz from GitHub releases:

Versions: com.cesium.unity-1.18.0.tgz and com.cesium.unity-1.17.0.tgz

Download fails around 90 MB on multiple devices (PC and tablet).

Tried multiple browsers (Avast Secure Browser, Chrome) — download crashes or shows “Failed – Unknown server error.”

Tried mobile data — download also fails.

3. Tried using Source Code zip/tar.gz from GitHub releases:

Downloaded successfully, but importing into Unity causes hundreds of compile errors (~259 errors) because Unity attempts to compile everything including Editor scripts.

4. Checked environment and dependencies:

Unity version: 2022.3.62f1 (LTS)

Git version: 2.50.1.windows.1 (latest)

Network: Stable, has successfully downloaded larger files (Unity and Unreal installers), so issue seems specific to GitHub/Cesium download.

5. Other attempts:

Tried clearing Unity cache for packages.

Tried fresh Unity project with URP and without.

Tried both v1.17.0 and v1.18.0.

Current Situation:

I cannot get the Cesium package to install via Package Manager.

Direct download via .tgz fails on multiple devices and networks.

Using the source code directly produces too many compile errors to work.

Could you please advise a working method to get Cesium for Unity installed on Unity 2022.3 LTS?

Thank you for your help!

Hi @Abdelrahman_Moussa, welcome to the community!

In our Quickstart tutorial, we usually advise people to install Cesium for Unity from a scoped package registry. Could you try that method and see if that works? We also just released a new package version, so perhaps that one will be more successful.

If you try rebuilding from source again, here are our Developer Setup instructions. It can be complicated to do it this way, because you will have to deal with the Reinterop system that generates C# handlers for our native C++ code. But as long as you have the required software and follow each step, you should be able to get it to compile.

Let us know how it goes!