All capability detection should be based on opengl extensions. In most cases
when there's no opengl extension which can provide the functionality we can't
support it. Recently I have improved our capability reporting quite a bit. Some
of the caps from the page you pointed to are now reported but
On Saturday 19 August 2006 15:06, EA Durbin wrote:
> Can we tie the gpu detection in to supporting fake/real alpha blending?
>
> http://bugs.winehq.org/attachment.cgi?id=2936&action=view
>
> http://bugs.winehq.org/show_bug.cgi?id=4050
No it's must be implemented using usuals GL caps queries :)
Ra
Can we tie the gpu detection in to supporting fake/real alpha blending?
http://bugs.winehq.org/attachment.cgi?id=2936&action=view
http://bugs.winehq.org/show_bug.cgi?id=4050
On 8/18/06, Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
Hi,
Hello,
This patch tackles the problem in a different way. The idea is not to return
the exact videocard but a close match (a card supporting more or less the same
opengl features or with similar performance). Based on test us
On 19.08.2006 00:09, Roderick Colenbrander wrote:
> +} else if(WINE_D3D8_CAPABLE(gl_info)) {
> +if (strstr(gl_info->gl_renderer, "GeForce4 Ti") ||
> strstr(gl_info->gl_renderer, "Quadro4"))
> +gl_info->gl_card = CARD_NVIDIA_GEFORCE4_TI4200; /*
> Gef
On 8/18/06, Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
Hi,
In case of Direct3D each device exports the pci device/vendor ids of the
videocard. Lots of programs use these ids to get an idea about the capabilities
of the card, enable/disable features based on the detected card or sometimes
