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
+79Lines changed: 79 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,84 @@
1
1
# Change Log
2
2
3
+
## ? - ?
4
+
5
+
##### Additions :tada:
6
+
7
+
- Added option to ignore the `KHR_material_unlit` extension to force default lighting on tilesets.
8
+
9
+
## v1.17.0 - 2025-08-01
10
+
11
+
##### Additions :tada:
12
+
13
+
- Added support for Cesium3DTileset tile selection using orthographic views.
14
+
15
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.49.0 to v0.50.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
16
+
17
+
## v1.16.2 - 2025-07-01
18
+
19
+
##### Fixes :wrench:
20
+
21
+
- Fixed broken support for `TRIANGLE_FAN` primitives in tile meshes.
22
+
- Fixed editor crash when any scale component on `Cesium3DTileset` was set to zero.
23
+
- Fixed a bug where CameraFlyToController, after the user interrupted a flight, would jump to the middle of the flight path immediately upon starting the next flight.
24
+
25
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.48.0 to v0.49.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
26
+
27
+
## v1.16.1 - 2025-06-02
28
+
29
+
This release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.47.0 to v0.48.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
30
+
31
+
## v1.16.0 - 2025-05-01
32
+
33
+
##### Additions :tada:
34
+
35
+
- Added `CesiumUrlTemplateRasterOverlay` component, allowing a raster overlay to be added using tiles requested based on a specified URL template.
36
+
37
+
##### Fixes :wrench:
38
+
39
+
- Fixed a bug where credits would not display in the Game tab after entering Play Mode.
40
+
- Improved stability during AppDomain reloads by catching exceptions thrown while freeing tiles.
41
+
42
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.46.0 to v0.47.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
43
+
44
+
## v1.15.5 - 2025-04-01
45
+
46
+
##### Fixes :wrench:
47
+
48
+
- Fixed a bug that could cause a crash when reloading a scene or tileset repeatedly.
49
+
50
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.45.0 to v0.46.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
51
+
52
+
## v1.15.4 - 2025-03-03
53
+
54
+
##### Fixes :wrench:
55
+
56
+
- "External Tilesets" are now unloaded when they are no longer used. This will significantly reduce the growth of memory usage over time when using Google Photorealistic 3D Tiles and similar tilesets.
57
+
58
+
This release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.44.3 to v0.45.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
59
+
60
+
## v1.15.3 - 2025-02-12
61
+
62
+
This release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.44.2 to v0.44.3. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
63
+
64
+
## v1.15.2 - 2025-02-10
65
+
66
+
This release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.44.1 to v0.44.2. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
67
+
68
+
## v1.15.1 - 2025-02-03
69
+
70
+
This release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.44.0 to v0.44.1. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
71
+
72
+
## v1.15.0 - 2025-02-03
73
+
74
+
Cesium for Unity now requires Unity 2022 LTS (2022.3), Unity 6, or later.
75
+
76
+
##### Fixes :wrench:
77
+
78
+
- Exceptions in either C# or C++ code are now handled much more reliably.
79
+
80
+
In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.43.0 to v0.44.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.
81
+
3
82
## v1.14.1 - 2025-01-02
4
83
5
84
This is the last release of Cesium for Unity that will support Unity 2021 LTS (2021.3). Future versions will require Unity 2022 LTS (2022.3) or Unity 6.
Copy file name to clipboardExpand all lines: Documentation~/developer-setup.md
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,8 @@ This should be repeated if you modify Reinterop, or if you pull new changes that
53
53
54
54
For more details, see the [Reinterop README](../Reinterop~/README.md).
55
55
56
-
A common mistake is to open Unity before doing this step, which will cause Unity to delete `Reinterop.dll.meta` file because the `Reinterop.dll` file does not yet exist. Then, even after you publish `Reinterop.dll`, the `Reinterop.dll.meta` that Unity creates will be missing important information, and you'll get errors when Unity attemps to compile Cesium for Unity. If this happens to you, executing `git restore Reinterop.dll.meta` should fix it.
56
+
> [!IMPORTANT]
57
+
> A common mistake is to open Unity before doing this step, which will cause Unity to delete `Reinterop.dll.meta` file because the `Reinterop.dll` file does not yet exist. Then, even after you publish `Reinterop.dll`, the `Reinterop.dll.meta` that Unity creates will be missing important information, and you'll get errors when Unity attemps to compile Cesium for Unity. If this happens to you, executing `git restore Reinterop.dll.meta` should fix it.
Once this build/install completes, Cesium for Unity should work the next time Unity loads Cesium for Unity. You can get it to do so by either restarting the Editor, or by making a small change to any Cesium for Unity script (.cs) file in `Packages/com.cesium.unity/Runtime`.
88
89
90
+
> [!NOTE]
91
+
> If you receive compilation errors such as,
92
+
> ```
93
+
> IonTokenTroubleshootingWindowImpl.h:3:10: fatal error: 'DotNet/System/String.h' file not found
94
+
> ```
95
+
> Verify that Reinterop has generated the required `.cpp` and `.h` source files. These should be located in `com.cesium.unity/native~/Runtime/generated-Editor/` and `com.cesium.unity/native~/Editor/generated-Editor/`.
96
+
> If those directories are not present, you may force Reinterop to run by adding a comment or other minor change to `./Runtime/ConfigureReinterop.cs`
97
+
and `./Editor/ConfigureReinterop.cs` .
98
+
> ```
99
+
> cd cesium-unity-samples/Packages/com.cesium.unity
100
+
> echo "" >> ./Runtime/ConfigureReinterop.cs
101
+
> echo "" >> ./Editor/ConfigureReinterop.cs
102
+
> ```
103
+
> (Alternatively, one may open both `ConfigureReinterop.cs` files from within Unity or any text editor, make a whitespace or other minor change, and save the files.)
104
+
> Once those changes have been saved, go back to the Unity editor. It should detect the file changes and cause Reinterop to generate the required C++ source files.
105
+
89
106
## Building and Running Games
90
107
91
108
When you build and run a standalone game (i.e. with File -> Build Settings... or File -> Build and Run in the Unity Editor), Unity will automatically compile Cesium for Unity for the target platform. Then, by hooking into Unity build events, Cesium for Unity will build the corresponding native code for that platform by running CMake on the command-line. This can take a few minutes, and during that time Unity's progress bar will display a message stating the location of the build log file.
0 commit comments