openframeworks / openframeworks/openFrameworks
iOS ESRenderer initialisation issue for old devices
@danoli3 is already working on this.
Since Nov 24, 2014.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Would be a crashing bug, however it is only affecting a handful of devices that may not even exist in use anymore ;)
After stepping through the renderers for the new window changes coming in for 0.9 with @julapy we discovered that, if a device failed to load OpenGLES 2.0 (programmable renderer), it would then try and load OpenGLES 1.1 (not programmable renderer), however openFrameworks window would still be set to programmable and may not work and would then need a way of communicating it has only loaded OpenGLES 1.1 and then reload the window appropriately (something that can come after new window changes).
Hard one to test as almost all iOS devices support OpenGLES 2.0. (which leads me to my other issue: ##)
Only ones I could find listed by Apple to only support OpenGLES 1.1 are iPhone, iPhone 3, iPod Touch 2,3. Even the iPad 1.0 has ES2.
However when it comes to a OpenGLES 3.0 feature, this may become a larger issue. (Although 3.0 is programmable, so not so severe, however oF won't know currently if it has really loaded say OpenGLES 3.0 or OpenGLES 2.0, those messages are just not sent).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.