Linked by Thom Holwerda on Thu 26th Apr 2012 18:23 UTC, submitted by Radio
Permalink for comment 515824
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2009-02-19
No, it isn't, at least not entirely. Part of the reason that OGL support is so bad on Windows is because OpenGL isn't Windows' primary 3D API; hardware developers treat OpenGL as a second-class citizen on Windows because it is a second-class citizen on Windows.
Also, part of the reason that OpenGL is so inconsistent between drivers is because Khronos doesn't (and can't) have the same kind of driver verification regime for OpenGL that Microsoft uses for D3D. Actually, NVIDIA (amusingly) is infamous for shipping known-broken OpenGL drivers on Windows.
The problem isn't the range of hardware targeted; the problem is that GL3 and GL4 state-trackers are not available for GL3 and GL4 hardware on Linux. I'm dual-booting my lap-top: in Windows 7, I get a GL4 context, while in Linux, I get a GL2.1 context. The open-source driver stack makes GL3+ contexts available to pretty much nobody at the moment. We're only just beginning to see GL3 state trackers actually get sent out to users by distributors. Mesa currently includes GL3 state trackers that work on some Intel hardware, and nowhere else; God knows how long it will be before GL3 is available for most of ATI's or NVIDIA's hardware, and say nothing of GL4.
Understand, I am a Linux user, and I'm not trying to really come down on the Mesa team or Linux kernel team. I think the major problem is just a lack of resources; graphics hardware is moving pretty fast right now, as is the OpenGL standard, and they just don't have the resources or the vendor support to keep up. But that doesn't change the reality of the situation; you're not going to get a decent port of a DX11 graphical system on GL2.
Edited 2012-04-26 21:52 UTC