New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 732826 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 722935



Sign in to add a comment

Investigate RendererSettings::highp_threshold_min

Project Member Reported by staraz@chromium.org, Jun 13 2017

Issue description

It seems highp_theshold_min is only set to non-default value in 
SurfacesInstance. SurfacesInstance is an Android specific class.

Look into what the field does and what the intended values were.
 

Comment 1 by staraz@chromium.org, Jun 13 2017

Description: Show this description
Status: Assigned (was: Started)
Mark it as assigned since I'm not actively working on it.
Assigned? You mean available? Also, remove yourself as owner if you're not working on it. Please hang off the viz layering metabug.
Cc: staraz@chromium.org
Owner: ----
Status: Available (was: Assigned)
Blocking: 722935

Comment 6 by danakj@chromium.org, May 25 2018

Status: WontFix (was: Available)
Looks like this value is used as a "min" as the name says, to clamp the value of highp_threshold in viz's shader.cc. Example:

  int highp_threshold = std::max(*highp_threshold_cache, highp_threshold_min);
  if (x > highp_threshold || y > highp_threshold)
    return TEX_COORD_PRECISION_HIGH;
  return TEX_COORD_PRECISION_MEDIUM;

So it can force the value high, causing us to use MEDIUM precision in more cases than we otherwise would. It looks like we only choose to do that on android, which is fine.

Sign in to add a comment