2 ms·
I suspect the most intractable OpenGL ES issues on mobile have nothing to do with that state machine though. For example, some drivers have oddball hardware lim
by makomk 11y ago
I suspect the most intractable OpenGL ES issues on mobile have nothing to do with that state machine though. For example, some drivers have oddball hardware limitations on the complexity of shader they'll execute and silently miscompile or drop shaders if they exceed the limits. That's not going to go away with Vulkan.
- Jasper_ 11y agoThe most intractable OpenGL ES issues on mobile have to do with the large amount of state kept, requiring long pipeline flushes, complex application-level batching, driver batching, and other things. Normally, drivers try to batch up a lot of work, but being really subtle about things (calling glGet, for instance), you can accidentally cause a blocking flush of your entire state. Making applications fast involves trying to defer and hack around this state machine as much as possible, while maintaining correct behavior. As such, you end up with tons of subtle, hard-to-find interaction bugs. I've debugged and fixed some of these in a certain mobile OpenGL driver we're deploying on our platform we licensed from the vendor. This is independent from other tricky bits of OpenGL ES, like the shader compiler front-end choking on perfectly valid GLSL, because there's no compliance tests for any of it.