Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding "discard" after "break" in WebGL (ANGLE) shader causes wrong image to be rendered #29

Open
0152la opened this issue Nov 28, 2016 · 3 comments

Comments

@0152la
Copy link
Collaborator

0152la commented Nov 28, 2016

[Shaders, screenshots, error log, reproduction steps, etc.] [ZIP]

Recipient:

recipient image

Variant:

variant image

Similar to #6. Confirmed to appear when run with GetImageAngle and not to appear when run with get_image.

@0152la
Copy link
Collaborator Author

0152la commented Nov 29, 2016

AMD Report Form ("n/a" means not filled):

Graphics Card Model:
Radeon R9 Fury X

Graphics Card Part Number:
n/a

AMD Radeon Software Driver Version:
AMD Radeon Software Crimson Edition 16.9.2

Driver History:
Do Not Know

Operating System:
Windows 10 64-bit

Type of Issue:
Other

Crossfire Configuration:
No

Using Mantle:
No

Other Games/Applications:
Google Chrome

Describe the Issue and Steps to replicate:
We use a custom written WebGL launcher and Chrome (self-contained HTML available for download at [1]; paste the shader code in the top box and hit "Execute"). When rendering the shader via WebGL, the incorrect image is being produced (variant.png), compared to the original, correct image (original.png). The difference between the two shaders is an added "discard" statement after a "break" statement. We observed that this does not occur when using normal OpenGL, but it does occur when using a custom-built ANGLE-based launcher (available for download at [2]).

More information and a list of all used files is available at [3].

[1] http://htmlpreview.github.io/?https://github.com/mc-imperial/shader-compiler-bugs/blob/master/utils/webgl/webgl_viewer.html
[2] https://github.com/paulthomson/GetImageAngle
[3] https://github.com/mc-imperial/shader-compiler-bugs/issues/29

CPU Details:
Intel(R) Xeon(R) CPU E5-1630 v3 @ 3.70GHz, 3701 Mhz, 4 Core(s), 8 Logical Processor(s)

Display Devices and Connections used:
Dell S2009W on HDMI

Motherboard or System Make & Model:
n/a

Motherboard BIOS version:
n/a

System Memory Type & Amount:
32GB

Power Supply Wattage:
n/a

@0152la
Copy link
Collaborator Author

0152la commented Jun 22, 2017

Issue persists with Radeon version 17.6.2.

@afd
Copy link
Member

afd commented Jun 22, 2017

Do we think this is an AMD issue or an ANGLE issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants