You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGES.md
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,35 @@
1
1
# Change Log {#changes}
2
2
3
-
### ???
3
+
### v2.20.0 - 2025-10-01
4
+
5
+
##### Additions :tada:
6
+
7
+
- Added support for rendering glTFs with line primitives.
8
+
- Added `UCesiumGoogleMapTilesRasterOverlay`.
9
+
- Added `AssetOptions` property to `UCesiumIonRasterOverlay`.
10
+
11
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.51.0 to v0.52.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
12
+
13
+
### v2.19.1 - 2025-09-02
14
+
15
+
##### Fixes :wrench:
16
+
17
+
- Fixed a bug that could cause incorrect ellipsoid parameters to be used when loading a level.
18
+
19
+
### v2.19.0 - 2025-09-02
20
+
21
+
##### Additions :tada:
22
+
23
+
- Added assets for the IAU2015 Moon and Mars ellipsoids under `Content`.
4
24
5
25
##### Fixes :wrench:
6
26
7
27
- Added a missing `CesiumRuntime.h` include in `CesiumPropertyAttribute.cpp` that broke compilation in v2.18.0 on Windows.
28
+
- Fixed a bug in `FCesiumVectorStyle` that made polygons use the color mode from `LineStyle` instead of `PolygonStyle`.
29
+
- Fixed a bug that could cause a crash when undoing and redoing deletion of a `CesiumRasterOverlay` component.
30
+
- Fixed a crash in `UCesiumLoadGeoJsonDocumentFromIonAsyncAction` that occurred when a Cesium ion server was not specified. The action will now fall back to the default ion server, similar to `ACesium3DTileset`.
31
+
32
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.50.0 to v0.51.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
Copy file name to clipboardExpand all lines: Documentation/developer-setup-windows-gotchas.md
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,13 +46,30 @@ With that, all builds invoked by Unreal Build Tool should use the chosen compile
46
46
47
47
If you've followed the instructions above, and Unreal Build Tool is now building Cesium for Unreal with v14.38 of the compiler, then you will likely get linker errors because the cesium-native and third-party dependencies are both still built with the newer version of the compiler.
48
48
49
-
vcpkg has hard-coded logic to choose the very latest version of the compiler that you have installed. It completely ignores all the usual ways that different compiler versions can be selected, such as setting the defaults file (`"C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\Microsoft.VCToolsVersion.default.props"`), setting environment variables or running the `vcvarsall` script. The _only_ way to choose a compiler for vcpkg to use, as far as we know, is by explicitly specifying it in a vcpkg triplet file. So, to build with 14.38, edit the `extern/vcpkg-overlays/triplets/x64-windows-unreal.cmake` file in the `cesium-unreal` repo and add this line to the end of it:
49
+
vcpkg has hard-coded logic to choose the very latest version of the compiler that you have installed. It completely ignores all the usual ways that different compiler versions can be selected, such as setting the defaults file (`"C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\Microsoft.VCToolsVersion.default.props"`), setting environment variables or running the `vcvarsall` script.
50
+
51
+
The easiest way to select a compiler for vcpkg to use is to set the `VCPKG_PLATFORM_TOOLSET_VERSION` environment variable. Despite the name, this is not built-in vcpkg functionality, but is instead something that our `x64-windows-unreal.cmake` triplet file looks for explicitly. To set it, run the following in a PowerShell window:
52
+
53
+
```powershell
54
+
$env:VCPKG_PLATFORM_TOOLSET_VERSION = "14.38"
55
+
```
56
+
57
+
Or in a CMD prompt, run:
58
+
59
+
```bat
60
+
set VCPKG_PLATFORM_TOOLSET_VERSION=14.38
61
+
```
62
+
63
+
This environment variable must be set before running CMake to configure the `cesium-native` project.
64
+
65
+
Alternatively, you can explicitly specify the toolset version in the vcpkg triplet file. To build with 14.38, edit the `extern/vcpkg-overlays/triplets/x64-windows-unreal.cmake` file in the `cesium-unreal` repo and add this line to the end of it:
50
66
51
67
```
52
68
set(VCPKG_PLATFORM_TOOLSET_VERSION "14.38")
53
69
```
54
70
55
-
Be careful not to commit this change!
71
+
> [!warning]
72
+
> Be careful not to commit this change if you edit the triplet file directly! Using the environment variable is safer.
56
73
57
74
vcpkg won't always automatically rebuild everything it needs to rebuild after making this change. To force a rebuild, delete the following:
58
75
@@ -105,7 +122,8 @@ It should look like this (though your names and `visualStudio` properties may be
105
122
"toolset": "host=x64,version=14.38"
106
123
},
107
124
"environmentVariables": {
108
-
"VCToolsVersion": "14.38.33130"
125
+
"VCToolsVersion": "14.38.33130",
126
+
"VCPKG_PLATFORM_TOOLSET_VERSION": "14.38"
109
127
}
110
128
},
111
129
{
@@ -119,7 +137,8 @@ It should look like this (though your names and `visualStudio` properties may be
0 commit comments