616864 - Aquarium WebGL demo does not render well with Intel OpenGL renderer

Status: RESOLVED WORKSFORME

(Core :: Graphics: CanvasWebGL, defect)

Description

[Scoobidiver (away)]

Attachment: Several screenshots of Aquarium demo in Minefield and Chrome

Build: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101203 Firefox/4.0b8pre

The fix of bug 603367 does not fix the bad WebGL rendering on 64-bit Windows.

Adapter Description: Mobile Intel(R) 4 Series Express Chipset Family
Vendor ID: 8086
Device ID: 2a42
Adapter RAM: Unknown
Adapter Drivers: igdumd64 igd10umd64 igdumdx32 igd10umd32
Driver Version: 8.15.10.2226
Driver Date: 10-15-2010
Direct2D Enabled: true
DirectWrite Enabled: true
GPU Accelerated Windows: 1/1 Direct3D 10

Comment 1

[JK]

I think the bug platform should be x86 instead of x86_64, considering that there is WOW64 in the user agent -> you are using the x86 (32bit) build.

Comment 2

[Scoobidiver (away)]

> I think the bug platform should be x86 instead of x86_64
I use 64-bit Windows, so x86_64 platform is correct.

Comment 3

[Scoobidiver (away)]

WebGL RendererIntel -- Mobile Intel(R) 4 Series Express Chipset Family -- 2.1.0 - Build 8.15.10.2226

Comment 4

[GMA]

Intel has released new Intel graphics drivers, 8.15.10.2246, older drivers were 2226. Might want to test these and see how it goes.

32bit
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19591&ProdId=3231&lang=eng

64bit
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19593&ProdId=3231&lang=eng

Comment 5

[GMA]

Intel 4 Series chipset users should ignore what I wrote above, the new 2246 drivers only supports HD Graphics(Core i3/i5), which is weird because the 2226 drivers supports both 4 series chipset and HD Graphics. HD Graphics users should install the new drivers since it fixes quite a number of bugs.

Comment 6

[Scoobidiver (away)]

Attachment: Screenshots with DirectX runtime renderer

Comment 7

[Scoobidiver (away)]

I installed DirectX runtime, so that:
WebGL Renderer: TransGaming Inc. -- ANGLE -- OpenGL ES 2.0 (git-devel Jan 10 2011 19:54:16)
And now Firefox and Chrome are competing for the best rendering (see new attachment).
The FPS difference does not change: 12 for Fx, 22 for Chrome.

Comment 8

[Scoobidiver (away)]

With today's build, there is no need to have DirectX runtime installed to use ANGLE:
WebGL Renderer: Google Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.541)

The rendering is excellent and FPS are inverted: 20 in FF 4.0, 14 in Chrome 10.

Comment 9

[Benoit Jacob [:bjacob] (mostly away)]

As I said in bug 594357 comment 22 and 23:

As far as I know, we still don't ship the DirectX
runtime bits, do we?

What today's build, the news is that ANGLE works again (provided that you have
DirectX runtime installed). It hadn't been working in the past 2 days.

Another relevant bit of news is that we now blacklist OpenGL on intel cards on
Windows. So if you can't use ANGLE, then you can't get WebGL at all.

Comment 10

[Scoobidiver (away)]

> As far as I know, we still don't ship the DirectX runtime bits, do we?
This is the only explanation I had for the differences of WebGL renderers between TransGaming (DirectX runtime) and Google.
Chrome has been able to use ANGLE without DirectX runtime installed.

Comment 11

[Benoit Jacob [:bjacob] (mostly away)]

(In reply to comment #10)
> > As far as I know, we still don't ship the DirectX runtime bits, do we?
> This is the only explanation I had for the differences of WebGL renderers

We recently updated our copy of ANGLE to r550 and it seems that they made this change, renaming the vendor from Transgaming to Google.

> between TransGaming (DirectX runtime) and Google.
> Chrome has been able to use ANGLE without DirectX runtime installed.

That just means that they ship those DirectX runtime bits. We're going to do the same very soon. We just had to get a confirmation from our lawyers that we were allowed to.

Comment 12

[Benoit Jacob [:bjacob] (mostly away)]

Shipping the needed DirectX runtime file will be done by bug 630628.

Comment 13

[Benoit Jacob [:bjacob] (mostly away)]

Done; should be working out of the box in tomorrow's nightly build.