Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve performance for large cities #23

Open
kfarr opened this issue Jun 25, 2017 · 0 comments
Open

Improve performance for large cities #23

kfarr opened this issue Jun 25, 2017 · 0 comments

Comments

@kfarr
Copy link
Owner

kfarr commented Jun 25, 2017

Cities with ~100+ objects seem to be slow in VR mode in FF nightly / Vive. There can be a noticeable delay when looking around or moving controllers which is nauseating and annoying. Here are some notes on optimization from a-frame slack conversation:

  • enable a-frame stats - done, and noticed a few things. the control-bar component creates a new draw call for each object previewed, but this is not removed. so over time in a scene when objects are browsed this slows down the scene little by little.
  • city builder users obj files. at the moment, each obj uses a separate mtl and png, but after some quick analysis those are usually identical (or very similar) and it's possible to load one mtl and use that same mtl reference for separate obj files. this may result in significant performance improvements and is probably the first place to try.
  • research instancing of identical objects - https://github.com/takahirox/aframe-instancing/
  • using "pool" is probably not going to offer significant performance improvement for this use case per slack conversation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant