Gallium3D's Direct3D 9 Support Is Coming Along Well

[eydee]

Also to standart wine. Standart wine with nvidia is much faster than nine in CPU bound usages.

This assumes that every nvidia card is faster than any AMD card. That's just not true.

[gigaplex]

The "fix" would be for more wine users to pay for it or develop patches themselves.

The patches have already been developed. The Wine developers just don't want to accept them.

[geearf]

Also to standart wine. Standart wine with nvidia is much faster than nine in CPU bound usages.

I see, thanks!

Nine cannot do miracles. It can be improved to have even lower cpu usage, but the gallium driver is also a limiting factor on this point.

That is unfortunate, miracles are cool!


But to Stefen's point, if Gallium drivers had the same speed/overhead as nvidia blobs, nine would still add a bonus performance boost, wouldn't it? If so, why can't it be a good idea to fix issues on both sides of the fences? (or at least one till the other gets its fixes)

[SXX⁣]

Because this is a key piece of what Wine is used for, to default and rely on a set of software that is both out of their control programming wise and also out of their control as to what version an individual user might have is a little worrying.

Wine is project that constantly break something with every single release while fixing other things and this is normal considering what it's doing. So people not going to blame Wine if they'll able to break it by any way as most of people who use it a lot have many versions installed via PlayOnLinux.

If the version the user needs is in Mesa 11.2 (to pick a future release) but the user only has mesa 11.0 then all they are going to see is wine not working and thus blame wine.

Nine patchset not going to break anything for anyone. It's have to be manually activated to use and it's also fallback to WineD3D if Nine not installed properly.

[SXX⁣]

. In a highly cpu limited scenario, Win still beats Gallium Nine by a lot.

Not that many of games are CPU-bound currently as they're mainly made for consoles with crappy CPUs.

To be fair it's a lot more interesting how Nine is perform against Windows. Sadly nobody made any proper benchmarking in that area yet.

[pal666]

Their own implementation works decent over everything, GalliumD3D9 only works on Nouveau and Radeon. That cuts out all of us that run things of Intel GPU's or catalyst or want the full power of our Nvidia cards.

it does not cut you. it keeps old shit working. but not including it cuts out all radeon and nouveau users(because old shit is slow and buggy). and there is a gallium driver for intel

[haplo602]

Staging implies it is being prepared for eventually being added into mainline, and AFAIU, this code has been rejected by upstream by design with them saying they will never accept it mainline because it's not something the proprietary drivers work with.

Not that i'm complaining - if they can stick it into staging, that'd be great.

They are doing special handling around NVIDIA for years, so driver compatibility should not be an excuse.

[stefandoesinger]

They are doing special handling around NVIDIA for years, so driver compatibility should not be an excuse.

http://xkcd.com/285/

Can you point me to the code where we are doing special handling?

There are 3 pieces of vendor specific code in wine:

• dlls/wined3d/ati_fragment_shader.c: A fixed function fragment pipeline implementation based on GL_ATI_fragment_shader, ATI's version of Shader Model 1 shaders. Used on r200 cards.
• dlls/wined3d/nvidia_texture_shader.c: The Nvidia counterpart for Geforce 3/4 cards.
• dlls/wined3d/arb_program_shader.c: Has shader model 3 support via GL_NV_*_program. Disabled by default. Used to be ~10% faster than GLSL. Nvidia appears to have fixed their GLSL implementation, ARB's advantage is mostly gone. Can be used on AMD GPUs too, but has only Shader Model 2 support.

Nothing in there that explains the factor of 3 performance difference that also affect Linux native games between equal Nvidia and AMD GPUs on Linux, or the factor of 3 performance difference between AMD on Linux and AMD on Windows.

[pinguinpc]

http://xkcd.com/285/

Can you point me to the code where we are doing special handling?

There are 3 pieces of vendor specific code in wine:

• dlls/wined3d/ati_fragment_shader.c: A fixed function fragment pipeline implementation based on GL_ATI_fragment_shader, ATI's version of Shader Model 1 shaders. Used on r200 cards.
  
• dlls/wined3d/nvidia_texture_shader.c: The Nvidia counterpart for Geforce 3/4 cards.
  
• dlls/wined3d/arb_program_shader.c: Has shader model 3 support via GL_NV_*_program. Disabled by default. Used to be ~10% faster than GLSL.
  
  Nvidia appears to have fixed their GLSL implementation, ARB's advantage is mostly gone. Can be used on AMD GPUs too, but has only Shader Model 2 support.

Nothing in there that explains the factor of 3 performance difference that also affect Linux native games between equal Nvidia and AMD GPUs on Linux, or the factor of 3 performance difference between AMD on Linux and AMD on Windows.

First thanks for your work

Do you know if wine 1.8 release candidate phase begins in somewhere in 2015????

[gens]

The problem is that wine developers don't see wine users as "actual customers".

Until that gets fixed we're just gonna have to live with differing opinions I guess.

wine devs are about doing things properly
if every patch that fixes every small thing some "customer" wants would get put in, wine would become un-debuggable after a while