-
Notifications
You must be signed in to change notification settings - Fork 962
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
Check for webgl2 validation errors and catch issues #3296
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3296 +/- ##
==========================================
- Coverage 65.63% 65.63% -0.01%
==========================================
Files 82 82
Lines 39479 39488 +9
==========================================
+ Hits 25914 25918 +4
- Misses 13565 13570 +5
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
b10f9d3
to
a4d64d2
Compare
Hey, nice work 🤙 I also spent a bit of time experimenting with catching the WebGL errors... Just an idea... |
@haraldreingruber Normally I would be totally game for expanded error messages - but in this particular case it can be a bit misleading. Because there are potentially so many errors registered during execution, combined with how horrid the GL error scheme is, adding more information when we don't really know much could leave people going down the wrong path. GL errors will already come through through the console, so we'll get some level of error messages. |
@cwfitzgerald makes totally sense. Thanks for the explanation. |
1490424
to
efa651b
Compare
Checklist
cargo clippy
.RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown
if applicable.Connections
Helps with #3282
Description
Testing
Explain how this change is tested.