Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Brian Hill
It's possible to do a rough auto-detect. General rule of thumb : ARB_FRAGMENT_PROGRAM = ~1.4 ARB_SHADER_LANGUAGE_100/GLSL = >= 2.0 This does not, however, take into account vendor specific shader extensions. H. Verbeet wrote: On 04/02/06, Vitaliy Margolen <[EMAIL PROTECTED]> wrote: +

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Brian Hill
GL_ext_blend_func_separate was something else I was working on for EVE Online. I branched off two CVS directories on my hard drive and that accidentally got copied over. H. Verbeet wrote: On 04/02/06, Brian Hill <[EMAIL PROTECTED]> wrote: I'd appreciate if people could test this patch a

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread H. Verbeet
On 04/02/06, Vitaliy Margolen <[EMAIL PROTECTED]> wrote: > > + default : > > + WARN("Invalid Pixel Shader version > > %d",wined3d_settings.ps_mode); > > + break; > Default should be NONE. > > > + if (!strcmp(buffer,"default")) > > +

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Brian Hill
* The copyrights are still in my copy of the altered file. I have no idea why CVS removed them. I'll look into why it did that. Same goes with the formatting. * Will change from WARN to FIXME. * Detecting the amount of texture memory is implementation specific and so we'd have to do differen

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Evil
Brian Hill wrote: > * User-selectable texture memory reporting. The current CVS version > is hardcoded to report 64 megabytes of graphics card texture memory. > I changed the hardcoded variable to be set by a registry setting... Woo hoo! I like this one! -J

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Segin
Vitaliy Margolen wrote: Saturday, February 4, 2006, 3:33:50 PM, Brian Hill wrote: * User-selectable texture memory reporting. The current CVS version is hardcoded to report 64 megabytes of graphics card texture memory. I We still need to make an attempt to detect it. Ov

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread H. Verbeet
On 04/02/06, Brian Hill <[EMAIL PROTECTED]> wrote: > I'd appreciate if people could test this patch and see if it breaks any > games. It compiles and runs fine on my system but I'd like to know > regardless. Sometimes I have a tendency to make silly mistakes in coding :P I had a quick look at the

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Joseph Garvin
Vitaliy Margolen wrote: * User-selectable texture memory reporting. The current CVS version is hardcoded to report 64 megabytes of graphics card texture memory. I We still need to make an attempt to detect it. Overriding it this way doesn't really make it more universal. From what I see

Re: wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Vitaliy Margolen
Saturday, February 4, 2006, 3:33:50 PM, Brian Hill wrote: > Attached is a patch file of the changes I have made to wined3d and it's > config options. > Summary of the changes : > * User-selectable pixel shader version. Default is 1.4. 2.0 is > selectable and if your card has GLSL support it sho

wined3d PS 2.0/TexMem/Config Window Patch

2006-02-04 Thread Brian Hill
Attached is a patch file of the changes I have made to wined3d and it's config options. Summary of the changes : * Cleaned up graphics tab on winecfg to make room for more DirectX related options. In an ideal world, options would be automagically detected but due to the amount of difference