Open Bug 1343705 Opened 7 years ago Updated 2 years ago

WebGL: drawArraysInstancedANGLE with gl.POINTS not working

Categories

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

54 Branch
defect

Tracking

()

UNCONFIRMED
Webcompat Priority P3

People

(Reporter: bugzilla, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

When calling drawArraysInstancedANGLE with gl.POINTS, only one instance seems to be rendered. It works correctly with LINES or TRIANGLES, while it also works with POINTS on Chrome and IE.

`ext.drawArraysInstancedANGLE(gl.POINTS, 0, numVertices, numCubes);`

I first thought it might be a threejs bug, so I tried to adapt a more raw example (given in http://stackoverflow.com/a/38805264/1550314) to use gl.POINTS:

Bug demo: http://ocbnet.ch/bugreport/firefox/webgl-instanced-points/

Tested against nightly 54.0a1 (2017-03-01) (64-bit) and stable 51.0.1 (32-Bit).



Actual results:

Only one instance is rendered


Expected results:

All instances should be rendered
Can you post a screenshot of what you're seeing? And also a copy of the Graphics section in your about:support?

I seem to be getting the same results between Chrome and Firefox on my machine.
Flags: needinfo?(bugzilla)
Attached image webgl-points.png
This is what I am seeing on Firefox.
Whiteboard: [gfx-noted]
Attached image ff-bug-webgl-points.png
Sorry for not reporting back earlier. Interstingly the demo seems to work on my laptop, which has an nvidia graphics chip beside the onboard intel one. My desktop is using an AMD Radeon 7800 gfx card. These are my about:support settings:

Allgemeine Merkmale
Compositing	Basic
Asynchrones Wischen und Zoomen	Mausrad-Eingabe aktiviert; Berührungs-Eingabe aktiviert
WebGL-Renderer	Google Inc. -- ANGLE (AMD Radeon HD 7800 Series Direct3D9Ex vs_3_0 ps_3_0)
WebGL2-Renderer	WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps.
H264-Dekodierung durch Hardware	No; Hardware video decoding disabled or blacklisted
Audio-Back-End	wasapi
DirectWrite	true (10.0.14393.351)
GPU 1
Aktiv	Ja
Beschreibung	AMD Radeon HD 7800 Series
Herstellerkennung	0x1002
Gerätekennung	0x6818
Treiber-Version	21.19.137.514
Treiber-Datum	11-21-2016
Treiber	aticfx64 aticfx64 aticfx64 amdxc64 aticfx32 aticfx32 aticfx32 amdxc32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Subsys-ID	00000000
RAM	2048
Weitere Informationen
AzureCanvasAccelerated	0
AzureCanvasBackend	skia
AzureContentBackend	skia
AzureFallbackCanvasBackend	cairo
Entscheidungsprotokoll
HW_COMPOSITING	
disabled by user: Disabled by pref
D3D11_COMPOSITING	
unavailable by default: Hardware compositing is disabled
D3D9_COMPOSITING	
unavailable by default: Hardware compositing is disabled
DIRECT2D	
unavailable by default: Direct2D requires Direct3D 11 compositing
D3D11_HW_ANGLE	
unavailable by default: D3D11 compositing is disabled
disabled by env: D3D11 compositing is disabled
FWIW: I've also disabled all custom settings related to webgl in about:config now, but I still get the same result as shown in the screenshot I've posted.

This is also affecting the WebGL globe animation at https://metal.equinix.com/ (the "cities" on the globe aren't being rendered).

Webcompat Priority: --- → ?
Webcompat Priority: ? → P3
Severity: normal → S3

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(bugzilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: