4 ms·
The Next Generation OpenGL Initiative isn't about an API cleanup, rewrite, tooling, benchmarking, or profiling. Those are all areas that could use improvement,
by modeless 12y ago
The Next Generation OpenGL Initiative isn't about an API cleanup, rewrite, tooling, benchmarking, or profiling. Those are all areas that could use improvement, but a standards body is not the place to do those things. Trying to do those things in a standards body is a recipe for logjams and delayed and bloated standards. "Longs Peak" is a prime example actually.
This initiative is about one major thing: reducing overhead. It's a response to Mantle/DX12 and their low CPU overhead rendering capabilities. OpenGL risks being left behind performance-wise because drivers are too complex. Because the API hasn't evolved as fast as the capabilities of modern hardware changed, drivers today do too much automatic work "behind the scenes". Things like memory allocation, texture swizzling, parameter validation, and shader recompilation often happen implicitly, outside of the control of the application. This adds unexpected CPU overhead which varies per driver.
Mantle/DX12 change the semantics of the API to match what modern hardware actually does. Applications have more control, drivers do much less implicit automatic work and CPU overhead is greatly reduced. That's what the "Next Generation OpenGL Initiative" is hopefully going to do for OpenGL.
- baq 12y agoagreed; simply reminding that apple's metal is very likely also a factor.
- criley2 12y agoIs metal that much of a factor to OpenGL? It's competition, but for a much much smaller piece of open gl's pie. OpenGL code will run on billions of mobile devices, but metal will only run on iOS which is an ever-shrinking share of total smartphone sales each year. Anyone who picks metal over opengl is picking iOS only--period. Any crossplatform game that doesn't want to write the entire game multiple times (once for apple, once for crossplatform, or heck onece for every platform) will simply not pick metal or any OS-dependent API.
- potatolicious 12y agoThe competition isn't going to happen at the end-developer level. Few game developers are actually going to be touching Metal directly. The competition is going to exist in middleware. Unreal, Unity, etc, will have Metal-optimized implementations on iOS, because they're still a big market. The real threat to OpenGL is if the Metal implementation on these engines is so substantially more powerful than the OpenGL implementation, and results in better-looking games or games running on cheaper/slower hardware.
- pjmlp 12y agoEver heard of rendering engines? AAA studios do it all the time.
- huxley 12y agoApple is encouraging Metal adoption through game engines like Unreal Engine 4, Frostbite and Unity (among others) to make it less demanding for developers. http://www.polygon.com/2014/6/2/5773128/metal-ios-gaming-wwdc http://www.polygon.com/2014/6/2/5773128/metal-ios-gaming-wwd...
- flohofwoe 12y agoThe inefficiency of PC 3D APIs compared to game consoles is an ongoing discussion since at least 2007. So far all low-level APIs have been designed for one specific GPU, or at least a specific architecture (like Mantle on AMDs GCN). Apple's move was unexpected, but much easier then trying to implement a low-level API which runs equally well on a wide range of GPU architectures. DX12 and 'GLNG' will be the first to really tackle that. But I have faith since there's enough 'prior art' in the form of game console 3D APIs, Mantle and Metal.
- exDM69 12y ago> but a standards body is not the place to do those things. Whose job it would be then? There is AMD's Mantle and Apple's Metal as well as Google's somewhat related RenderScript. As long as they're going to remain a single vendor API, they will be adapted as an universal new API. But hopefully the work by these vendors (all of which are Khronos members) will serve as a basis for a future standard API. Longs peak was a failure and the API was very complicated. It was definitely a failure due to design by commitee. But in the end, there has to be an industry consortium to standardize on a new API. When we're talking about an API that is closely tied to the hardware it runs on (which is a lot more expensive to develop than APIs and software), there's no other option than to get all the big players around the same table. Right now, Khronos is the most likely candidate since all the key players are members in that group. At some point there has to be a new API. OpenGL isn't just an API with some warts in it, it's getting more and more in the way of new development.
- modeless 12y agoFocusing on reducing driver overhead is the right way forward. If driver overhead is minimized, so that OpenGL is as thin a layer as possible over the real hardware, then changing the API becomes trivial: you can just wrap OpenGL and expose any API you want on top. Then, if someone writes a popular API wrapper, Khronos can take that API and standardize it as the next version of OpenGL, no design-by-committee required.
- fzltrp 12y ago> Then, if someone writes a popular API wrapper, Khronos can take that API and standardize it as the next version of OpenGL, no design-by-committee required. If that wrapper actually supports all the features evenly, and doesn't favor a particular implementation. Is that possible outside a design by committee?
- exDM69 12y agoI think your idea is completely crazy. Feel free to disagree. I think the only realistic way forward without breaking backwards compatibility is to build a new low overhead close to the metal API and implement OpenGL on top of that (e.g. adding a new MESA backend). Doing a new API on top of OpenGL first is quite impossible. But I wouldn't mind breaking backwards compatibility either. I think D3D does the right thing here and every major version is incompatible with the previous version. Porting to the next version isn't too difficult (mostly a search and replace job) but it's still not source or binary compatible. I think this is the major reason why D3D is a cleaner API. > If driver overhead is minimized, so that OpenGL is as thin a layer as possible over the real hardware, then changing the API becomes trivial: you can just wrap OpenGL and expose any API you want on top. Given the convoluted mess that OpenGL drivers are (I work on one), it is very unlikely that such things will happen. We can't reduce driver overhead by adding new stuff. Some parts we can help (see the "Approaching Zero Driver Overhead" talks) but there's still an inherent overhead from all the state validation and other complexities. Also, wrapping OpenGL into anything nicer isn't really possible. Otherwise there would be lots of neat 3D APIs implemented on top of OpenGL and you could choose whichever you like. But it's impossible to work around the idiosyncrasies of OpenGL. And writing wrappers is fundamentally incompatible with low overhead anyway. > Then, if someone writes a popular API wrapper, Khronos can take that API and standardize it as the next version of OpenGL That "someone" would need to be a major established player and the API must be something that actually catches on. It must be complete and functional. Khronos isn't just going to fork a random dude's GitHub project and go from there. There are practical reasons but let's not forget the legal issues either. This scenario isn't just gonna happen.