UE5 Failed to pack Hololes

yangjiahaoTemp · October 24, 2022, 6:51am

The following problems occur when UE5 packages Hololens:Error: Failed to cook /Game/NewWorld for platform HoloLens. It imports class /Script/CesiumRuntime.Cesium3DTileset, which is in a module that is not available on the platform.

Kevin_Ring · October 24, 2022, 7:20am

Hi @yangjiahaoTemp,

Cesium for Unreal does not currently support HoloLens.

You may be able to build it for that platform yourself by following the Developer Setup Guide. I’m not aware of anything that should prevent it from working. We haven’t tried it, though, so there will likely be small or large problems along the way.

Kevin

rakhishah · January 9, 2023, 6:00pm

Hi @Kevin_Ring,

I’m also facing the same issue as @yangjiahaoTemp. I was trying to package my 3dFlightVisualizer application for the HoloLens 2 in UE5. I’ve used Cesium for Unreal plugin to add cesium world terrain, cesium sunsky and cesium OSM buildings in my project. Is your team planing to do work on supporting it? If yes can you give me a timeline for it? If no can we expect in near future your team will take a look on it?

I’m getting this error (Please refer attached snapshot) in unreal engine. If I use unity will it work?

Kevin_Ring · January 10, 2023, 2:25am

Cesium for Unreal works with HoloLens remoting, but it can’t currently run directly on the device. We don’t have any current plans to address that, but would welcome a pull request if you work on it yourself. I don’t think there should be any major barriers to compiling ceisum-native and Cesium for Unreal for HoloLens. Start with the Developer Setup instructions and adapt for the platform:

github.com

CesiumGS/cesium-unreal/blob/ue5-main/Documentation/developer-setup.md

## Overview

This is a summary of a setup and workflows for developers who want to work with the *Cesium for Unreal* plugin. Such a setup consists of three main components:

- [`cesium-native`](https://github.com/CesiumGS/cesium-native) : A collection of engine-independent libraries for 3D Tiles, geospatial, etc. Most of the functionality of *Cesium for Unreal* is built based on these libraries.
- [`cesium-unreal`](https://github.com/CesiumGS/cesium-unreal) : The source code of the actual *Cesium for Unreal* plugin.
- An Unreal project that uses the plugin. We will use the [`cesium-unreal-samples`](https://github.com/CesiumGS/cesium-unreal-samples) as an example here, to get started quickly. It contains sample levels for different use cases, and can therefore be used to quickly check for possible regressions of feature changes.

> Note: It is generally possible to work with `cesium-native` *independent* of `cesium-unreal`. But any modification in `cesium-native` will have to be checked carefully for possible breaking changes in the API or the build process. So the following describes the developer setup from the perspective of someone who wants to work with `cesium-native` mainly in the context of `cesium-unreal`.

## Principles

There are detailed instructions for setting up a Cesium for Unreal development environment on each platform. But if you're already used to doing this sort of thing, you can probably use whatever workflow you like as long as you follow some important principles:

- To build Cesium for Unreal, you must first compile and cmake-install cesium-native and its dependencies to `Plugins/cesium-unreal/Source/ThirdParty`.
- cesium-native is built and installed using CMake and the `CMakeLists.txt` found in the `cesium-unreal/extern` directory, _not_ the one in the `cesium-unreal/extern/cesium-native` directory. When installing from this directory, the default install path will put cesium-native where Cesium for Unreal expects to find it.
- You must use the same compiler to build cesium-native and Cesium for Unreal.
- On Windows, packaging the Cesium for Unreal plugin on Windows requires Visual Studio 2017. This means you must also build cesium-native with Visual Studio 2017 in order for plugin packaging to be successful. But if you're not concerned with packaging, you can use Visual Studio 2019 exclusively.
- The Unreal project "DebugGame" configuration tries to use the debug build of cesium-native if one is built and installed, and falls back on the release build otherwise. The "Development" and "Shipping" configurations use the release build exclusively.
- Our CI build process checks for formatting using clang, and fails if code is improperly formatted. To run clang on all source code before committing, run `npm ci` to install node modules, then `npm run format`.

This file has been truncated. show original

rakhishah · January 13, 2023, 11:58am

Hi @Kevin_Ring,

Thanks for your quick reply. Will packaging application using Cesium for Unity work?

Kevin_Ring · January 13, 2023, 12:11pm

No, the situation is much the same in Cesium for Unity. There’s no reason it can’t be made to work, probably isn’t very hard, but it doesn’t currently work out of the box.