31
General / We really need help to fix the Cesium tiled format output
« on: January 20, 2022, 06:25:25 PM »
There is definitively something wrong with the cesium tiled output.
There have been several messages on the forum about that so i'm not the only one having issues.
Could please have a look, this i a very important feature to be able to use our very large models.
Here is a tiled model generated by metashape:
Using cesiumjs with inspector tools:
https://www.gigascope.net/vr/tilesfrommetashape/
Using my aframe vr viewer:
https://www.gigascope.net/vr/tilesfrommetashapeaframe/
link to download the tiles:
(https://data2.gigascope.net/3d/tilesfrommetashape/street0.zip)
And the tiled model from cesium when i upload the obj to cesium:
Using cesiumjs with inspector tools:
https://www.gigascope.net/vr/tilesfromcesium/
Using my aframe vr viewer:
https://www.gigascope.net/vr/tilesfromcesiumaframe/
As you can see something is broken in the metashape output, you can use the inspector to see that the Bounding and Content volumes are wrong.

some of the previous topics about that issue:
https://www.agisoft.com/forum/index.php?topic=12730.msg61211#msg61211
https://www.agisoft.com/forum/index.php?topic=13121.msg58197#msg58197
https://www.agisoft.com/forum/index.php?topic=11978.msg53691#msg53691
There have been several messages on the forum about that so i'm not the only one having issues.
Could please have a look, this i a very important feature to be able to use our very large models.

Here is a tiled model generated by metashape:
Using cesiumjs with inspector tools:
https://www.gigascope.net/vr/tilesfrommetashape/
Using my aframe vr viewer:
https://www.gigascope.net/vr/tilesfrommetashapeaframe/
link to download the tiles:
(https://data2.gigascope.net/3d/tilesfrommetashape/street0.zip)
And the tiled model from cesium when i upload the obj to cesium:
Using cesiumjs with inspector tools:
https://www.gigascope.net/vr/tilesfromcesium/
Using my aframe vr viewer:
https://www.gigascope.net/vr/tilesfromcesiumaframe/
As you can see something is broken in the metashape output, you can use the inspector to see that the Bounding and Content volumes are wrong.


some of the previous topics about that issue:
https://www.agisoft.com/forum/index.php?topic=12730.msg61211#msg61211
https://www.agisoft.com/forum/index.php?topic=13121.msg58197#msg58197
https://www.agisoft.com/forum/index.php?topic=11978.msg53691#msg53691