low framerate on oculus quest about 3dstreet HOT 6 CLOSED

stats, default camera placement, http://localhost:8080/#https://streetmix.net/kfarr/3

from 3dstreet.

models worth optimizing:

• ground component adds ~6k triangles per each, could easily be brought to 1 with a simple plane and texture
• fence is 80k triangles and 300+ draw calls, huge optimization potential here
• "block" of buildings is 155k tris and 367 calls, also large optimization potential

not worth optimizing:

• tracks ~3k tris and 24 calls, moderate optimization potential and known as a model that needs improvement anyway
• car / bus / train are ~5.5k, ~3k and ~2k tris respectively; for their quality level this isn't too bad; perhaps instancing can be used to reduce calls for duplicated objects?

from 3dstreet.

Ground component before/after triangle count as part of 5e4d8ca:

• For http://localhost:8080/#https://streetmix.net/kfarr/34 - before: 291934; after 283998 (reduction by 7936 triangles)
• For http://localhost:8080/?#https://streetmix.net/kfarr/36 - before 364028; after 348156 (reduction by 15872 triangles)

from 3dstreet.

Attempted to reduce draw calls using A-Frame merge geometry component, but can't get it to work for this use case. It doesn't appear to work for gltf models (and/or when entities added dynamically).

Final short term attempts will be to fix the fence and buildings

from 3dstreet.

Tried using gltfpack and it definitely reduced draw calls but resulted in larger file size. Still experimenting:
#4

Also tried reducing complexity of the 3d scene which definitely helped. That's also a work in progress.

Next, need to test how using gltf-part affects draw calls.

Also in order to use gltf-part with draco needs fixing:
supermedium/superframe#260

from 3dstreet.

This ticket is too broad so closing as-is. There are other tickets that represent further work on this topic in this milestone:

• https://github.com/kfarr/streetmix3d/milestone/1

from 3dstreet.