[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AW: [Public WebGL] Context Creation Error Event

Hi Ashley,
That's not the problem here. We will do this anyway. As we expected a better performances from WebGL than from 2D Canvas we would like to make sure that as many players as possible will use WebGL instead of 2D canvas. If their browser have no WebGL support at all this is easy as we just can recommend to install one that have support.
My problem are these 15% that have a browser with WebGL but have other problems. The spec is not clear if this status message is just a technical one or something that is understandable enough for a common user to fix these problems without additional support. Don't get me wrong I am happy that the new draft contains a feedback method that give us more details. I am just trying to figure out what we can do with this feedback. 

Von: ash@scirra.com [ash@scirra.com] im Auftrag von Ashley Gullen [ashley@scirra.com]
Gesendet: Montag, 9. Januar 2012 17:38
An: Kornmann, Ralf
Cc: public_webgl@khronos.org
Betreff: Re: [Public WebGL] Context Creation Error Event

Hi Ralf,

If getContext() returns null when requesting a WebGL context, you can just call getContext("2d") and you get the 2D canvas you can fall back to.


On 8 January 2012 23:31, Kornmann, Ralf <rkornmann@ea.com> wrote:
as our new web game is somewhat graphics intensive we see some performances problems with browser that have no hardware acceleration for 2D canvas operations. Therefore we though to add another WebGL based render engine to the game. To get some numbers about how many of our players can use WebGL we add a short test in our current beta version of the game.
We were able to create a WebGL context for ~62% of this tests. We had ~22% tests with no WebGL support at all (mostly IE). While this is good enough to give a WebGL path a try I am somewhat unsure how we can handle the missing 15%. For these tests the browser reports general WebGL support but we were unable to create the context.
The new draft contains a new error event with a status message. But the draft is not very specific how usable this message would be. Will it be something that can be understand from the user (in the local language) or should we expect something more technical that requires additional support from our side?
Bonus question: Is there already an implementation of this error event in any browser?