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

Issue 773449 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

ANGLE sampler object on integer texture produces black frag when mesh is small

Reported by shreks...@gmail.com, Oct 10 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Download the attached texture_integer_sampler_test.html file
2. Launch a local http server and access this html file in the browser.

What is the expected behavior?
Two textures should be zooming in the canvas.
Launch chrome via `chrome.exe --use-gl=desktop` (forcing use opengl) can produce the correct result.
Same thing happens in firefox so pretty sure it should be related to ANGLE

What went wrong?
Both textures are integer textures.
The one on the right is using a sampler object. It is only producing correct fragments when the scale is larger than a certain point.

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version:
 
texture_integer_sampler_test.html
10.4 KB View Download

Comment 1 by alph@chromium.org, Oct 10 2017

Components: -Platform>DevTools Internals>GPU>ANGLE
Labels: Needs-Triage-M61
Cc: sc00335...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
Unable to reproduce this issue on reported version 61.0.3163.100 and on latest canary 63.0.3236.0 using Windows 10 with steps mentioned below.

1.Downloaded attached sample file.
2.Launched HTTP Server using python -m SimpleHTTPServer
3.Launched chrome using chrome.exe --use-gl=desktop and navigated to localhost:8000/Downloads/texture_integer_sampler_test.html
4.Black screen with Left: uint texture, Right: uint texture + sampler object is seen. Attaching screencast for reference.

@Reporter: Could you please let us know what is the expected. It would be helpful if you attach a screenshot of expected behaviour for further triaging.

Thanks!
issue 773449.mp4
873 KB View Download

Comment 4 by shreks...@gmail.com, Oct 11 2017

My bad. It's because of cross origin image getting denied.
I've uploaded a new zip file which include the image. the html will now load the image from local. So it should work correctly now.
I also uploaded two gif: one showing result when ANGLE is enabled, and one with it disabled.
Reproduce step stays the same: 
1.Downloaded attached .zip file, go to the folder.
2.Launched HTTP Server using python -m SimpleHTTPServer
3a.Launched chrome normally and navigated to localhost:8000/path/to/folder/texture_integer_sampler_test.html. 
The texture on the right will only be visible when it is larger than a certain size. (try resize the viewport if you cannot see it appears as it scales up)
3b.Launched chrome using chrome.exe --use-gl=desktop and navigated to localhost:8000/path/to/folder/texture_integer_sampler_test.html. Both texture should be visible all the time.
texture_integer_sampler_test.zip
240 KB Download
angle_wrong_result.gif
1.1 MB View Download
opengl_expected_result.gif
1.2 MB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 11 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: geoffl...@chromium.org jmad...@chromium.org
Components: Blink>WebGL
Owner: jmad...@chromium.org
Status: Available (was: Unconfirmed)
I can confirm the ANGLE GL back-end does not display the issue while the D3D11 back-end does. Can affect WebGL 2 conformance. Assigning to myself but leaving as available in case someone else wants to steal it from me.

Comment 7 by kbr@chromium.org, Oct 11 2017

Possibly related to mipmapping of integer textures? This isn't supported in ES 3.0, but maybe is in D3D11 and we're forgetting to turn that off?

Status: Assigned (was: Available)

Sign in to add a comment