Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 348237 TEXTURE_MAX_ANISOTROPY init value is wrong on Linux AMD
Starred by 3 users Project Member Reported by zmo@chromium.org, Mar 1 2014 Back to list
Status: Fixed
Owner:
Closed: Apr 2014
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment
It should be 1, but instead, it returns 0.

So cause the failure in https://www.khronos.org/registry/webgl/conformance-suites/1.0.2/conformance/extensions/ext-texture-filter-anisotropic.html

A few ways to workaround this to pass 1.0.2

1) Disable this extention on Linux AMD - this is allowed behavior - until AMD fixes this driver issue

2) If the extension is enabled in webgl, when creating a texture, init the TEXTURE_MAX_ANISOTROPY value to 1 - this could be very heavy

3) Assuming the initial default behavior is actually the same as TEXTURE_MAX_ANISOTROPY == 1 (although it returns a 0), we only need to mask the returned value to 1 if it's never explicitly set.  This is the best way in my opinion, but we need to verify the default behavior is as if TEXTURE_MAX_ANISOTROPY == 1.

What do you think?
 
Comment 1 by zmo@chromium.org, Mar 1 2014
This is the last remaining issue for 1.0.2 webgl conformance issue, so I'd like to resolve it quickly.  Please share your opinion.
Comment 2 by zmo@chromium.org, Mar 4 2014
Owner: zmo@chromium.org
Status: Started
Comment 3 by kbr@chromium.org, Mar 4 2014
Cc: shannonwoods@chromium.org vmi...@chromium.org
First, any logic change should be guarded under a driver bug workaround so that only the affected machines are penalized.

I would personally prefer (2) if it works, to avoid special-casing more queries in the command buffer.

Project Member Comment 4 by bugdroid1@chromium.org, Mar 5 2014
Comment 5 by zmo@chromium.org, Apr 21 2014
Status: Fixed
Sign in to add a comment