-
Notifications
You must be signed in to change notification settings - Fork 83
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
BTW: I get much better fps with webpack-dev than budo. #96
Comments
That’s really odd - the bundler should have no impact on framerate or shader rendering performance. I’ve never seen or heard of this issue. Do you have a test case I can try? |
My thoughts exactly. Makes no sense. Maybe some prod/dev env variable is being set somewhere? Don't have a test case I can share now, but it's basically just about 10k points being animated with regl and mix() in the shader. I push points off screen to hide them. I mainly want people who are getting a weirdly low fps in budo to try out webpack. |
I switched from webpack to budo recently and didn't perceive this. Until someone can reproduce it, should we close this? |
@MaxBittker Sounds good to me. Only thing I can imagine is that some dev/debug/env flag difference would trigger something, but nothing jumps out. I'm definitely interested in debugging/tracking down if it can be reproduced, but without a reproducible case, it's unfortunately just a wild good chase. |
For webpack, I did move my shaders into separate files since glslify-loader doesn't seem to like using the inline glsl(``) style.
fps with budo is ~20-25, webpack is around 60.
The text was updated successfully, but these errors were encountered: