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

Performance issues with WebQuake build 54 (1.09) #32

Open
JustH3LL opened this issue Oct 5, 2017 · 5 comments
Open

Performance issues with WebQuake build 54 (1.09) #32

JustH3LL opened this issue Oct 5, 2017 · 5 comments

Comments

@JustH3LL
Copy link

JustH3LL commented Oct 5, 2017

So I decided to Mirror WebQuake on http://h3ll.x10host.com/WebQuake/

I couldn't help but notice that the version on Quaddicted seems to be way better optimized than the latest on here, I tested on a Chromebook to confirm this (huge random performance drops on the latest version on here even with a performance-increasing autoexec)

I'm sure this is due to optimization, and I'm willing to fix this myself if I had a pointer on where to start on this

My target is Chromebooks due their wide usage in schools

@Triang3l
Copy link
Owner

Probably caused by the dynamic vertex buffer rewrite. Dynamic vertex buffers are extremely messy and unpredictable in OpenGL, especially on mobile GPUs, I don't really know how to make the performance nice with them, considering WebGL doesn't even provide things like glMapBufferRange :(

@LiamKarlMitchell
Copy link

Could a shader do the job to change the vertex geometry if it's just moving points around? Or is it more involved?

@Triang3l
Copy link
Owner

Particles still need at least to be spawned and destroyed on the CPU, so they will be resubmitted in some form anyway, changing position to base position, velocity and time won't help. That's how dynamic VBOs are probably supposed to be modified in OpenGL ES, but also it's very broken in GL implementations.

@SpiritQuaddicted
Copy link

Quaddicted was finally updated too :p

I guess this issue can be closed as things simply changed and it sounds like it is going to stay that way.

@Triang3l
Copy link
Owner

OpenGL ES 2 sucks in general.

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

4 participants