分页: 1 / 1

shader-f16 not supported by browser

发表于 : 2024年 9月 18日 01:36
yylly
Chromium v120 and up is meant to have shader-f16 by default, but it won't be listed in features here: https://webgpureport.org/

See: https://github.com/mlc-ai/web-llm/issue ... 1877115608

I need this feature for use with @mlc-ai/web-llm, please include it in an update. Thank you.

Re: shader-f16 not supported by browser

发表于 : 2024年 9月 18日 13:00
catsxp
Same kernel m129 in Chrome and CatsXP
The test results are consistent

Re: shader-f16 not supported by browser

发表于 : 2024年 9月 18日 13:58
yylly
catsxp 写了: 2024年 9月 18日 13:00 Same kernel m129 in Chrome and CatsXP
The test results are consistent
When you go to this site, does it show shader-f16 in the "features" section? (Bottom of the middle column.)

Re: shader-f16 not supported by browser

发表于 : 2024年 9月 18日 17:17
catsxp
M120+ confirmed default support?

Re: shader-f16 not supported by browser

发表于 : 2024年 9月 19日 02:01
yylly

Re: shader-f16 not supported by browser

发表于 : 2024年 9月 19日 12:03
catsxp

代码: 全选

// List of WebGPU feature names, delimited by ,
// The FeatureParam may be overridden via Finch config, or via the command line
// For example:
//   --enable-field-trial-config \
//   --force-fieldtrial-params=WebGPU.Enabled:UnsafeFeatures/timestamp-query%2Cshader-f16
// Note that the comma should be URL-encoded.
This is the only relevant comment that can be found in the source code
Attempt to add startup parameters:

--enable-field-trial-config \
--force-fieldtrial-params=WebGPU.Enabled:UnsafeFeatures/timestamp-query%2Cshader-f16

The test results show that it is not yet open
Are you sure the test results of this page are valid under win? (Mac testing?)

catsxp://gpu/

代码: 全选

[Adapter Supported Features]
----------------------------
*   depth-clip-control
*   depth32float-stencil8
*   timestamp-query
*   texture-compression-bc
*   indirect-first-instance
*   shader-f16
*   rg11b10ufloat-renderable
*   bgra8unorm-storage
*   float32filterable
*   subgroups
*   subgroups-f16
*   dawn-internal-usages
*   dawn-multi-planar-formats
*   dawn-native
*   implicit-device-synchronization
*   surface-capabilities
*   unorm16texture-formats
*   snorm16texture-formats
*   multi-planar-render-targets
*   adapter-properties-memory-heaps
*   adapter-properties-d3d
*   format-capabilities
*   norm16texture-formats
*   shared-texture-memory-dxgi-shared-handle
*   shared-fence-dxgi-shared-handle
is ok!

Re: shader-f16 not supported by browser

发表于 : 2024年 9月 21日 20:24
yylly
My apologies, it turned out to be a hardware issue, apparently my card doesn't support shader-f16. Very sorry.