1122912 - Bad rendering of WebGL demo with D3D11 ANGLE enabled

Status: RESOLVED WORKSFORME

(Core :: Graphics: CanvasWebGL, defect, P3)

Description

[Loic]

STR:
1) Open this demo http://5013.es/toys/to_the_beat_js/
NB: source code is here https://github.com/sole/to_the_beat
2) Click on "START"
3) After ~15 sec, you should see light blue ellipses in the background like "worm holes".


Result:
With D3D11 ANGLE enabled, it's malformed and bad rendered.
It's fine with webgl.angle.try-d3d11=false.

Comment 1

[Loic]

Maybe a dupe of bug 1109718.

Comment 2

[Loic]

Attachment: screenshot-FF35.jpg

Comment 3

[Loic]

Attachment: screenshot-FF38.jpg

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Does the problem happening in Chrome with D3D11 on?

Comment 5

[Lawrence Mandel [:lmandel] (use needinfo)]

Can you confirm that this issue is present in Aurora 37 and not in Beta 36?

Comment 6

[Loic]

Yes, I confirm it. In general, I test each version before reporting a bug (to find a possible regression/fix). :)

Comment 7

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Loic from comment #6)
> Yes, I confirm it. In general, I test each version before reporting a bug
> (to find a possible regression/fix). :)

Great. Thank you. I have updated the tracking and status flags for 37.

Comment 8

[Jeff Muizelaar [:jrmuizel]]

Do you see the same problem in Chrome when using D3D11 ANGLE?

Comment 9

[Jeff Muizelaar [:jrmuizel]]

I am able to reproduce a difference between ANGLE D3D11 and D3D9 but it's not obvious to me which one is correct. FWIW, Our D3D11 rendering seems to match Chrome's D3D11 rendering. Perhaps there's some precision issue?

Comment 10

[Jeff Muizelaar [:jrmuizel]]

A reduced test case would help a lot here.

Comment 11

[Loic]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #8)
> Do you see the same problem in Chrome when using D3D11 ANGLE?

I don't have Chrome to test.

Comment 12

[Jeff Muizelaar [:jrmuizel]]

(In reply to Loic from comment #11)
> (In reply to Jeff Muizelaar [:jrmuizel] from comment #8)
> > Do you see the same problem in Chrome when using D3D11 ANGLE?
> 
> I don't have Chrome to test.

Is it possible for you to get Chrome?

Comment 13

[Lawrence Mandel [:lmandel] (use needinfo)]

This bug hasn't had any progress in ~3 weeks. My understanding is that this is not expected to impact a large amount of Web content. As such, I'm dropping tracking and will let the gfx team prioritize with their other work.

Comment 14

[Kelsey Gilbert [:jgilbert]]

I think this is fixed, probably by an ANGLE update.

Please reopen if it's still broken for you.

Comment 15

[Loic]

Attachment: screenshot-FF46.jpg

It's not fixed with the latest Nightly and D3D11 ANGLE enabled.
The blue "spirals" in the background are still malformed.

Comment 16

[Kelsey Gilbert [:jgilbert]]

(In reply to Loic from comment #15)
> Created attachment 8705763 [details]
> screenshot-FF46.jpg
> 
> It's not fixed with the latest Nightly and D3D11 ANGLE enabled.
> The blue "spirals" in the background are still malformed.

It works for me. Please post your about:support.

This machine is Win10 on NVidia.

Comment 17

[Loic]

Attachment: about_support.txt

(In reply to Jeff Gilbert [:jgilbert] from comment #16)
> (In reply to Loic from comment #15)
> > Created attachment 8705763 [details]
> > screenshot-FF46.jpg
> > 
> > It's not fixed with the latest Nightly and D3D11 ANGLE enabled.
> > The blue "spirals" in the background are still malformed.
> 
> It works for me. Please post your about:support.

Attached.

Comment 18

[u279076]

Does this still reproduce?

Comment 19

[Loic]

(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #18)
> Does this still reproduce?

Yes, still broken like in my 1st comment #0 (tested with the latest Nightly).

Comment 20

[u279076]

Can you please post an updated about:support and mark your old one as obsolete?

Comment 21

[Loic]

Attachment: about_support.txt

Comment 22

[u279076]

I suspect this:
> WebGL2 Renderer WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: WEBGL_NATIVE_GL_OLD_INTEL * Exhausted GL driver options.

Can you make sure both your GPUs are running the latest driver?

Comment 23

[Milan Sreckovic [:milan] (needinfo for best results)]

That error is for WebGL2 - the error in the original description is WebGL, so probably not related.

Comment 24

[Loic]

I can't update Intel drivers anymore because Intel has stopped support for HD Graphics 3000, they have not even provided drivers for Windows 10 support (last ones are from May 2015 which are mine).

Comment 25

[Mayank Bansal]

HD Graphics 3000 are old drivers. I am closing this.
@Loic: Please reopen if you can still reproduce this bug.