Hello everyone,
I’ve seen some similar issues but rather related to some server/cesium ion side problems:
In our packaged apk one specific tileset is not visible/existing (MaxScreenSpaceError = 1). Neither added on runtime with or as a static tilesets as seen in the editor screenshot.
No matter if this is a local tileset or streamed from a company URL the tileset remains invisible.
For the runtime imort on VR we set up logging, that prints the load progress of each tileset on tick.
The progress starts with 0% jumps to 11.1% and then to 100%
All other tilesets load slowly as expected.
In the Editor and the packaged Windows version (Also tried starting in PC-VR) the Tileset is loading correctly, both as a static tileset or a runtime import.
Most confusing thing is that not even the statically imported tilesets is visible in the installed app on the Quest 3.
We are using UE5.2 with Cesium v2.4.0 + v2.9.0
Tested in all engine scalability settings from low to epic.
We went back to a git branch serveral months ago (where the tilesets was 100% visible, we have still a working apk from this state) and the problem appears to be the same when we package it now.
This was then tried in UE5.1 with Cesium 2.4.0.