Re: WineD3D: glBlend* fixes

2006-09-27 Thread H. Verbeet
On 27/09/06, Chris Robinson [EMAIL PROTECTED] wrote: In the case of WineD3D, it should have an OGL version - D3D version map. So if, say, OGL 2.0 is functionaly equivilant to D3D 9, then it'd report D3D 9 right off the bat for OGL 2.0 drivers; if added extensions can make it functionally

Re: WineD3D: glBlend* fixes

2006-09-27 Thread Chris Robinson
On Wednesday 27 September 2006 00:51, you wrote: Also, I've yet to see a driver that doesn't report the extension while supporting the functionality in the core. Isn't that the problem you're running into that spawned this discussion? With certain drivers not reporting an extension for

Re: WineD3D: glBlend* fixes

2006-09-27 Thread H. Verbeet
On 27/09/06, Chris Robinson [EMAIL PROTECTED] wrote: On Wednesday 27 September 2006 00:51, you wrote: Also, I've yet to see a driver that doesn't report the extension while supporting the functionality in the core. Isn't that the problem you're running into that spawned this discussion? With

Re: WineD3D: glBlend* fixes

2006-09-27 Thread Roland Scheidegger
Roderick Colenbrander wrote: On windows the opengl32.dll exports glBlendColor by default and as opengl32.dll is opengl 1.1 I thought that it was a core function. So you say that it is backed by GL_ARB_imaging. The problem is that basicly only Nvidia advertises it and the other drivers don't.

Re: WineD3D: glBlend* fixes

2006-09-26 Thread Roderick Colenbrander
Hi, Roderick, Mesa calls the extension GL_EXT_blend_minmax, and so does the spec. I don't know what exactly uses the min_max form. Is this a typo? Apart from the blend_minmax typo, it appears to be me this patch has some other problems. This patch changes the detection extension

Re: WineD3D: glBlend* fixes

2006-09-26 Thread Roderick Colenbrander
The problem is that a version check is not reliable. For instance in case of a remote X session the version number for instance in case of the nvidia drivers can be 2.0 while most extensions aren't supported. For reasons like this we can't use version checks and should only detect extensions.

Re: WineD3D: glBlend* fixes

2006-09-26 Thread Chris Robinson
On Tuesday 26 September 2006 03:21, Roderick Colenbrander wrote: Vendors should still advertise GL_ARB_imaging for backwards compatibility if they do support 1.4 or higher but ATI and friends don't :( Compliant implementations are not required to advertise an extension if they report a

Re: WineD3D: glBlend* fixes

2006-09-26 Thread Chris Robinson
On Tuesday 26 September 2006 08:47, you wrote: The problem is that a version check is not reliable. For instance in case of a remote X session the version number for instance in case of the nvidia drivers can be 2.0 while most extensions aren't supported. For reasons like this we can't use

WineD3D: glBlend* fixes

2006-09-25 Thread Roland Scheidegger
Roderick, Mesa calls the extension GL_EXT_blend_minmax, and so does the spec. I don't know what exactly uses the min_max form. Is this a typo? Apart from the blend_minmax typo, it appears to be me this patch has some other problems. This patch changes the detection extension detection for

Re: WineD3D: glBlend* fixes

2006-09-21 Thread Jesse Allen
On 9/21/06, Roderick Colenbrander [EMAIL PROTECTED] wrote: Hi, This patch changes the detection extension detection for glBlendColor/glBlendEquation. The function glBlendColor is part of OpenGL 1.1 and is supported on all OpenGL implementations. Officially it is part of the GL_ARB_imaging