Will GL_EXT_depth_bounds_test be promoted to core now that both AMD and NVidia support it?
Will GL_EXT_depth_bounds_test be promoted to core now that both AMD and NVidia support it?
The OpenGL 4.3 core spec removed the GL_ALPHA format for glReadPixels (chapter 18.2.1, page 458). The other single-component formats GL_RED, GL_GREEN and GL_BLUE are supported, but GL_ALPHA is only supported in the compatibility profile. In 4.2 core all 4 individual components could be read with glReadPixels.
Is there a reason why the alpha channel is treated special here ?
It also needs to be used by a lot of people. If very few people actually use a feature, then it usually has very little testing or IHV support. Anything "not on the common paths" is very likely to blow up or not provide any benefits, just due to the exponential branching complexity of oh-so-many features. Ideally, any proposed feature would have some kind of "preliminary consensus" that it can indeed be a benefit, and would indeed match a lot of people's expected case uses.
The nonsensical description of DrawElements was eventually fixed in 4.3 spec, nice! However, it would be good if the
description of the "indices" parameters would reflect the according meaning on the ref pages as well (of it being an offset,
not any sort of pointer C-type).
This is mostly incorrect. Features are (or should be) tested before they are released regardless of popularity of each feature, and the way to achieve that is to write tests or use an existing test suite which can assess the quality of an OpenGL implementation. There is the official OpenGL conformance test suite developed by Khronos that driver developers should use first. There is also Piglit, the unofficial open source OpenGL test suite, which is pretty huge and it's getting bigger every day with 89 contributors so far. Finally, driver developers should write their own tests for features they implement (I know major vendors do that, though the specification coverage of their tests might vary a lot, considering AMD passed about 75 % of Piglit tests last time I checked, which is not very good, and NVIDIA even less than that).
(usually just hobbyist) OpenGL driver developer
You seem very conflicted about what you're saying.This is mostly incorrect. Features are (or should be) tested before they are released regardless of popularity of each feature, and the way to achieve that is to write tests or use an existing test suite which can assess the quality of an OpenGL implementation.
On the one hand, you're saying that the post is wrong to say that only some features are being tested. Yet you cite low Piglit scores and the obvious lack of comprehensive testing by driver developers. So clearly some features are not being properly tested. So you agree with Brandon's point: that staying on commonly tread ground is the most effective way to avoid driver bugs.
The post you're responding to is not talking about what "should be"; the post is talking about what is currently. And you seem to agree with his explanation of the current state of things.
So what is "mostly incorrect" about what he's saying?
If there is a desktop OpenGL conformance test, I haven't heard of it. The old conformance test for desktop GL was never updated; it never even checked conformance to 2.0. So it's worthless for anything more recent. OpenGL ES 2.0 and 3.0 have conformance tests, but not desktop GL.There is the official OpenGL conformance test suite developed by Khronos that driver developers should use first.
Khronos said that they were interested in making one, but they haven't announced anything beyond interest.
Last edited by Khronos_webmaster; 07-22-2013 at 05:56 AM.