-
Notifications
You must be signed in to change notification settings - Fork 956
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
Downlevel max_inter_stage_shader_components
not consistent
#4298
Comments
I can't seem to find this language. I think it's correct that the limits in |
Here: Lines 956 to 959 in f7c8767
As currently documented, yes. This issue is primarily about the fact that either Separately, I think that this simple principle no longer fits the complexity of reality, because "Web only" is an important use case. However, breaking that relationship is a more significant change; perhaps I should have filed a separate issue about it. Let's ignore that question and focus on fixing |
Looking some more into this, I think we should revert the change to A PR would be welcome. |
Description
The default values for
Limits::max_inter_stage_shader_components
are:default
= 60downlevel_defaults
= 60downlevel_webgl2_defaults
= 31The limit to 31 was introduced by 2b985e2 #4248. But this does not make sense, because the documentation says that
downlevel_defaults
is the value for “…almost all backends, including “downlevel” backends such as OpenGL…”. So if the restriction is correct, it should be indownlevel_defaults
too, not only in the WebGL-specific set.Other non-bugfix improvements that could be made:
Platform
wgpu 0.18.0, macOS
The text was updated successfully, but these errors were encountered: