@sguimmara @autra @erilem it does but for example being able to get webgl array buffers from renderers instead of the final image could be also interesting!

@autra what makes it interesting compared to chrome performance tab is:
- it includes async macro/micro tasks (settimeout, promises...) when tracking time
- it gives a clear reading of how often each method is called and how much time is spent in it
- it shows the frame times in real time

@autra @erilem would love to find the time and talk about this a bit more... Renderers are part of the OL API so it should definitely be possible to extend them. The biggest problem might be that an assumption for 2D is done in many places (e.g. shaders). Also maybe it just doesn't make sense to rely on another library for something so critical, as it would mean heavily dependant on it.

@erilem @autra it does haha, and it sure has a lot of potential! I wonder if it could use more than just the sources from OL and somehow plug itself into the renderers to benefit even more from the work done there

@autra I'd like to go back to doing 3D but I'm currently quite busy with good old 2D vector tiles in OL 😓 but yes, very interesting project, I4ll keep it in mind!

@autra sweet! 👍

@autra thanks, improssive work! I'm really curious on how meshes from WFS are adjusted to the elevation model 🧐 are they positioned vertically according to their center and then extruded downwards and upwards?

@autra Yes, I had a look and integration with OL is great IMO. Well done! How far are you guys in terms of rendering actual shapes instead of images for vector data?

@ls sounds good!