-
Notifications
You must be signed in to change notification settings - Fork 52
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
listen() halts UI if used on many controllers #35
Comments
Oh thanks for the catch. Yes, dat.GUI consolidates all the listen loops, lil-gui makes a new loop for each controller. Is this hosted anywhere by chance? I'm curious how many controllers it takes to make this happen. I'll look into consolidating the loops in a future release. |
not hosted. I had ~100 controllers. do you plan to solve it?
|
Yes, I'd like to. I'll need to reproduce it first to have something to test against. dat.gui's NPM warnings aren't related to this library. Unless you're seeing warnings when installing lil-gui you should be fine. |
Should be able to do a lot more listening if you update to 0.16.1 Let me know how that works! |
No sir. Sorry, still way too slow. Down to 5 fps (!). And yes, I'm using 0.16.1 |
I'm able to run this page https://dev.lil-gui.georgealways.com/examples/listen-stress/?100 at 50fps on a 2014 MBP (after checking animateAll). Unless you're able to upload your work I can't really help any further. |
I've tried
lil-GUI
to replacedat.GUI
, followingthreejs
.I've noticed it kill my framerate. this happens because I use the
listen()
on each field.Note that in
dat.GUI
it doesn't happen.For now I'm returning to
dat
. keep me updated.The text was updated successfully, but these errors were encountered: