Cesium for Unreal, HoloLense2

Cesium for Unreal
1

Hi,

is it possible to run Cesium for Unreal (UE 4.27) on the HoloLense2.

I set up an example and could compile and deploy it, but got a black window on the hololense.

Regards

Rüdiger

1 Like
2

I use unreal 4.27.2, Cesium for Unreal 1.24.0 (because of 4.27 ?)

Example from here:

Cesium for Unreal v1 Quickstart – Cesium

Cesium for Unreal Quickstart – Cesium

1 Like
3

Any chance you’re able to update to the latest?

We don’t support UE 4.x anymore and your plugin version is fairly old…

Latest:

  • Cesium For Unreal v2.4.0
  • Latest Unreal (5.3.2)
4

Hi,

ok - but don’t you know the last compatible Version with UE 4.x - due to project conditions I can’t change the UE version

Regards

Rüdiger

5

Got it.

So everything is black on the HoloLens 2, does the same project seem to run fine in the Unreal Editor?

Also, when running on the HoloLens, do you see anything related in logs that could indicate a connection error?

6

Hi @Ruediger_Brand,

As Brian mentioned, we no longer support UE 4.27, and it will be difficult for our team to support you because our development environments have long since changed.

But you can check out Project Anywhere XR, a proof of concept demonstrating how to use large-scale datasets (loaded through Cesium) in a HoloLens 2 application. This was built with UE4, so hopefully it will still load and you can use it as reference for your own projects.

Best of luck! :smile:

7

Hi Janine, Brian,

ok - I tried Cesium on UE 5.2.1, because the hololense isn’t supported on 5.3

Packaging to Hololense I got an error:

UATHelper: Packaging (HoloLens): LogCook: Error: [AssetLog] D:\UE5\CesiumQuickStart\Content\CesiumQuickStart.umap: Failed to cook /Game/CesiumQuickStart for platform HoloLens. It imports class /Script/CesiumRuntime.CesiumGeoreference, which is in a module that is not available on the platform.
PackagingResults: Error: [AssetLog] D:\UE5\CesiumQuickStart\Content\CesiumQuickStart.umap: Failed to cook /Game/CesiumQuickStart for platform HoloLens. It imports class /Script/CesiumRuntime.CesiumGeoreference, which is in a module that is not available on the platform.

So I will check my installation with VS …

Regards

Rüdiger

8

I didn’t get it - also ProjectAnywhereXR not.

I got some mistake

UATHelper: Packaging (HoloLens): Reflection code generated for ProjectAnywhereXR in 9,9608018 seconds
UATHelper: Packaging (HoloLens): ERROR: Missing precompiled manifest for ‘CesiumRuntime’. This module was most likely not flagged for being included in a precompiled build - set ‘PrecompileForTargets = PrecompileTargetsType.Any;’ in CesiumRuntime.build.cs to override.
UATHelper: Packaging (HoloLens): Took 14,5136536s to run UnrealBuildTool.exe, ExitCode=6
UATHelper: Packaging (HoloLens): UnrealBuildTool failed. See log for more details. (C:\Users\bma\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_4.27\UBT-ProjectAnywhereXR-HoloLens-Development.txt)
PackagingResults: Error: Missing precompiled manifest for ‘CesiumRuntime’. This module was most likely not flagged for being included in a precompiled build - set ‘PrecompileForTargets = PrecompileTargetsType.Any;’ in CesiumRuntime.build.cs to override.
UATHelper: Packaging (HoloLens): AutomationTool exiting with ExitCode=6 (6)
UATHelper: Packaging (HoloLens): BUILD FAILED
PackagingResults: Error: Unknown Error

but I didn’t have this file - so I stopped

9

Maybe this is too obvious, but did you try to modify \CesiumForUnreal\Source\CesiumRuntime.build.cs in the way it describes?