You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenGL ES 3 is a large extension to ES 2, offering a large number of new features. Eventually we should have support for it.
I propose we do so by having a new package that contains the extra enum values and functions, which can be used in conjunction with the existing gl package.
This is a very low priority item as ES 3 is not currently usable on Android. 72% of devices only support ES 2, so all software today must first target ES 2 and only use ES 3 as an optional extension.
I think those statistics are more android in general and not representative of "people who game on android". I wouldn't be surprised if > 50% of android users never ran a GL based app.
Are you suggesting having a package with "new to gles3" funcs/enums only? I would vote against that. The new and old are too intertwined. New enums that only work with old funcs. New funcs that work with new and old enums.
Also GL Extensions are currently being ignored.
All of my gles2.0 android devices have extensions that make them much more usable.
A device that is not capable enough to run all of gles3.0 may still run parts of it as extensions.
So old, new and random extensions intertwined. It is moderately chaotic.
OpenGL ES 3 is a large extension to ES 2, offering a large number of new features. Eventually we should have support for it.
I propose we do so by having a new package that contains the extra enum values and functions, which can be used in conjunction with the existing gl package.
This is a very low priority item as ES 3 is not currently usable on Android. 72% of devices only support ES 2, so all software today must first target ES 2 and only use ES 3 as an optional extension.
http://developer.android.com/about/dashboards/index.html#OpenGL
The text was updated successfully, but these errors were encountered: