Load local terrain，Someone help me，save me！

Cesium for Unreal
1

It can be loaded by using the cesiumlab publishing service，But I can’t load it when I publish it with nginx。I’m going crazy！Loading into cesium is OK, but loading into cesium for UE4 is not OK。

2

Does it show any error messages when you want to load it? (In the output log, via the “Window” Menu → Developer Tools → Output Log). Or does it simply not show anything? Otherwise: Can you provide more details about the terrain (i.e. the type and structure of the terrain, its format or other technical information)?

3

error messages

LogCesium: Loading tileset from URL http://127.0.0.1:666/test/layer.json
LogCesium: Loading tileset from URL http://127.0.0.1:666/test/layer.json done
LogCesium: Warning: [2021-08-04 18:02:04.619] [warning] [TileContentFactory.cpp:74] No loader registered for tile with content type ‘application/octet-stream’ and magic value ’
LogCesium: Warning: [2021-08-04 18:02:04.636] [warning] [TileContentFactory.cpp:74] No loader registered for tile with content type ‘application/octet-stream’ and magic value ’

4

Thank you for your reply，
error messages

LogCesium: Loading tileset from URL http://127.0.0.1:666/test/layer.json
LogCesium: Loading tileset from URL http://127.0.0.1:666/test/layer.json done
LogCesium: Warning: [2021-08-04 18:02:04.619] [warning] [TileContentFactory.cpp:74] No loader registered for tile with content type ‘application/octet-stream’ and magic value ’
LogCesium: Warning: [2021-08-04 18:02:04.636] [warning] [TileContentFactory.cpp:74] No loader registered for tile with content type ‘application/octet-stream’ and magic value ’

5

The part that says magic value ’ looks truncated (it should actually say what the unknown magic value was). Are you able to share one of these assets, so that it is possible to have a closer look what might be wrong there?

EDIT: Does it work when you try to load this asset from a local file, using the file protocol, as described in Adding Datasets – Cesium ?

If this works, then there might just be something wrong with the local server that is running there. (But again: Without further details, these are just guesses for now…)

6

terrain.rar (1.3 MB)

image
image1304×937 21.1 KB

Here is a small part of what I just packed，And my nginx configuration

7

It should technically be possible to load the data, but I think there are two issues:

  1. It might be that the input data is not compliant to the specification - but I am not sure about this! When I load it locally, it does not look very detailed, and I’m not sure whether this is the result that you’d expect:

    CesiumUnreal local terrain
    CesiumUnreal local terrain720×391 52 KB

    If it is not, then this might be related to the way how the “Tile Availability” is encoded. I’d have to point you to Terrain loading failed in CTB production for now.

  2. I’m not an nginx expert, but I think that the webserver might not configured properly. (I loaded it locally from a file, with a crude workaround for another issue …).
    Specifically: For Quantized Mesh tiles, the tile type is determined based on the Content-Type of the network response. And in order to properly detect this, the Content-Type must be "application/vnd.quantized-mesh" when a quantized mesh tile is requested.
    Maybe you already know where or how to configure this in the nginx config file. Otherwise, I’d ask someone who is more familiar with that topic to chime in here.

(Sorry, this is not a perfectly satisfactory answer, but hopefully helps a bit to investigate that further…)

8

the key point is set Content-Type "application/vnd.quantized-mesh"，maybe need configure the nginx

9

I have the same problem.