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

Re: [Public WebGL] GL_OES_element_index_uint

On Thu, Feb 10, 2011 at 3:57 PM, Jonathan Feldstein <jfeldstein@rim.com> wrote:
> Hi Ken,
> Thanks for the quick reply. I guess I'm a touch confused. Doesn't the whole extension concept imply that not everyone needs to implement them? Case and point you just mentioned that this extension is supported by Google but not Apple on the iPhone and iPad platforms for OpenGL ES 2.0.

While that is true, there's a strong desire in the WebGL working group
to avoid fragmenting the developer landscape by adding official
extensions (such as those adopted from the OES namespace) that are
unsupported on a large class of hardware.

A vendor would be more than welcome to add an extension to their WebGL
implementation (RIM_element_index_uint?) and try to garner support for
other vendors to implement it as well.


> All the best,
> - Jonathan Feldstein
> -----Original Message-----
> From: Kenneth Russell [mailto:kbr@google.com]
> Sent: Thursday, February 10, 2011 6:36 PM
> To: Jonathan Feldstein
> Cc: public_webgl@khronos.org
> Subject: Re: [Public WebGL] GL_OES_element_index_uint
> On Thu, Feb 10, 2011 at 2:52 PM, Jonathan Feldstein <jfeldstein@rim.com> wrote:
>> After playing around with WebGL one thing that I noticed was that the
>> specification seems to be missing the ability to create 32-bit index
>> buffers. OpenGL ES 2.0 has the ability to enable this with the:
>> GL_OES_element_index_uint extension.
>> 65536 possible index values doesn't really seem like enough values for
>> today's games. People will be forced to split their index values into
>> multiple arrays of data. Would it be possible to add this extension, or is
>> there a good reason that it is currently absent?
> I don't think the WebGL working group has discussed this extension.
> However, after doing some searching, it looks like while Android
> hardware has widespread support for it, it isn't supported on any
> current iOS hardware, iPhone or iPad. We want WebGL content to run
> identically across desktop and mobile hardware, so in my opinion the
> lack of support on iOS makes adding it to the WebGL extension registry
> a non-starter.
> -Ken
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl