We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sonic Engine text used to be crisp on reasonably performant devices
Sonic Engine's giant texture has regressed to being blurry again
See https://scratch.mit.edu/projects/74711180/
Mac OSX Chrome
The text was updated successfully, but these errors were encountered:
It looks like this has been happening since #393.
Instead of backing off if a texture fails to render, the maximum texture size can be queried directly via gl.getParameter(gl.MAX_TEXTURE_SIZE).
gl.getParameter(gl.MAX_TEXTURE_SIZE)
There's still the question of what happens if you allocate too many large textures and run out of VRAM-- as far as I can tell, different browsers and possibly even different hardware may do different things.
Sorry, something went wrong.
Try running this on your test hardware: texture-allocation-test.zip
On my machine (Linux, NVIDIA GTX 780 Ti), both Firefox and Chromium happily eat up all my RAM creating textures beyond what can fit into VRAM at once.
I'd be interested to know if the same happens for the Chromebook mentioned in #393, or if it causes the WebGL context to be lost.
No branches or pull requests
Expected Behavior
Sonic Engine text used to be crisp on reasonably performant devices
Actual Behavior
Sonic Engine's giant texture has regressed to being blurry again
Steps to Reproduce
See https://scratch.mit.edu/projects/74711180/
Operating System and Browser
Mac OSX Chrome
The text was updated successfully, but these errors were encountered: