3d tiles renderer js migration bootstrap

[jailln]

Description

Starts the migration towards using 3dtilesRendererJS for 3D tiles. I created the 3d-tiles-migration branch in which we can merge our work related to this migration. This is a first implementation with some TODOs left in the code

Already implemented:

• [x] Create a new 3D tiles layer using 3dtilesrendererjs and deprecate C3DTilesLayer
• [x] Draco and KTX2 support
• [x] Cesium ion support
• [x] Google 3D tiles support
• [x] Gltf 1.0 support
• [x] CESIUM_RTC GLTF 1.0 extension support
• [x] itowns PointsMaterial support (ongoing)

Some TODOs left in the code (don't hesite to give your opinion), commits are still messy and still some stuff to do to be iso with the C3DTilesLayer implementation (see below).

Motivation and Context

2225

Notes on the implementation

• Used the name ThreeDTilesLayer, WDYT?
• Even if 3dtilesRendererJS TilesRenderer is conceptually not at the same level than an itowns Layer, I decided to instance one TilesRenderer per ThreeDTilesLayer. Also I kept the C3DTilesIonSource and C3DTilesGoogleSource for C3DTilesLayer to keep working but also to keep itowns Source / Layer instanciation logic in the API (even if these sources are not really useful anymore now that we use 3dtilesRendererJS because all the logic related to querying cesium ion an google sources are handled by 3dtilesRendererJS).
• I implemented a wrapper around threejs GLTFLoader and LegacyGLTFLoader that loads gltf regardless of their version (1.0 or 2.0) and that shares the same interface than three GLTFLoader to allow loading gltf 1.0 files with 3dtilesrendererjs (named iGLTFLoader for "itownsGltfLoader"). This class is exported so users that need to load gltf 1.0 or 2.0 files in their applications can benefit from it.
• I implemented CESIUM_RTC gltf 1.0 extension support in the LegacyGLTFLoader
• Regarding draco and ktx2, I decided to keep the static enableDracoLoader and enableKTX2Loader that sets the draco and ktx2 path in itowns internal instance of iGLTFLoader.

Don't hesitate to give your opinion on these choices :)

First tests

I started running some tests, it seems that:

• Google 3D tiles display is lightning fast
• 3dtiles_25d.html example seems slower
• Point clouds:
  • slower
  • there seems to be a SSE issue (some visible tiles are not loaded)
  • the batch table is not loaded

I will take some time today to do some more performance tests and try to assess where these drawbacks may come from.

Remaining TODO

Still a lot to do, see this list :)

[jailln]

@Desplandis I rebased my branch and updated 3d-tiles-renderer-js to 0.3.33 (last version).

Except from the remaining points listed here, I'm not really satisfied of the modifications I made to the PointVS shader (there should be a better way than having a #if inside the if/else conditions for the PNTS_MODE) and the classification mode does not work in the 3dtiles_pointcloud.html yet, I need to check why. I still wanted to push my rebase so you can review before I come back at it next thursday :slightly_smiling_face:

Note that because of this that has not been released yet you need to make this correction in the 3d-tiles-renderer-js source files in itowns node_modules/ for it to work (or simply downgrade to 0.3.32 should work too)

[mgermerie]

The PR on 3DTilesRendererJS you mentioned has been merged and in their latest 0.3.34 release. I bumped the version and pushed it on your branch so the manual correction is no longer necessary.