Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

Kangz
Copy link
Contributor

@Kangz Kangz commented Feb 1, 2019

We agreed that anisotropic filtering would be an extension so this
parameters shouldn't be defined in the descriptor for core WebGPU.

We agreed that anisotropic filtering would be an extension so this
parameters shouldn't be defined in the descriptor for core WebGPU.
@kvark
Copy link
Contributor

kvark commented Feb 1, 2019

@Kangz could you link to the minutes/discussion/investigation on where we agreed to this, please?
Thinking about this now, it's only optional in Vulkan, where just 4% of the devices (ARM, mostly) don't support it. Given how old the tech is, and how wide-spread the use of anisotropic sampling is in games, it would be a good candidate for us to expose unconditionally.

@Kangz
Copy link
Contributor Author

Kangz commented Feb 4, 2019

Mmmmh it seems recent-ish versions of Samsung's ARM driver don't support it, including the 9S and 8S. Supporting it unconditionally would prevent WebGPU from running on these devices. We (Google) should probably ask ARM about it.

@grorg
Copy link
Contributor

grorg commented Mar 25, 2019

Discussed at 25 March teleconference

@kdashg kdashg merged commit 1f7faed into gpuweb:master Mar 25, 2019
@Kangz Kangz deleted the remove-anisotropy branch April 23, 2019 12:57
ben-clayton pushed a commit to ben-clayton/gpuweb that referenced this pull request Sep 6, 2022
(originally gpuweb#202 against glsl-dependent)

The test originally checked for the validation error on the wrong device.

Co-authored-by: Austin Eng <[email protected]>
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

Successfully merging this pull request may close these issues.

4 participants