Performance regressions about zeo

[avaer]

Seems fine now.

[avaer]

This could have been because of multiplayer.

• Investigate that

[avaer]

Slow code paths from the profile:

• rend _updateKeyboardAnchors BoxTarget generation
• update keyboard anchors when menu is opened
• world _updateNpmAnchors BoxTarget generation
• update npm anchors when menu is opened
• Excessive ShadowMap renders: camera, and once per eye; it could just as well be only one
• No need to use solidMaterial/MultiMaterials for tag meshes

[avaer]

☝️ Getting rid of the shadow map hits the frame target.

[avaer]

Looks like too many drawcalls for tags rendering. Should use a single geometry + texture atlas. Indeed, getting rid of all tag meshes from the scene makes all the difference.

• use a texture atlas for tag meshes
• make number of textures a per-ui setting
• merge tag mesh geometries, and return a proxy plane mesh object used to recompute geometry vertices
• implement page garbage collection in uiManager
• port mail engine to new biolumi API on rebase
• anchor tracking for tag meshes does not work
• regressed menu/keyboard positions
• npm mesh tag selection is one off

[avaer]

Reopening because some checkboxes remain.

[avaer]

Reportedly performance leaves something to be desired:

Surface book, 6th Gen Intel Core i7, 1TB SSD, 16GB RAM, Nvidia 940M