Does WINE work well with radeon drivers for D3D games?

[Setlec]

My understanding is that the Intel open source drivers are around GL 1.5 while the ATI open source drivers are "1.3 with nearly all of the 1.4 features". Not sure exactly how that maps into which apps run well on Wine.

I know that this question is stupid and might have been already asked millions of time, why don't you just focus in get openGL3.x support instead of going version 1.0 up to 3.3? R600 do support openLG3.3, right?

[sgcb]

I, for one, compile and install mesa/wine inside a 32 bit chroot. This way it's easier to manage and dependencies stay up-to-date (no more waiting for ia32-libs to catch up on debian)

Also regarding the last bit, most games I've been playing around with will crash if 2 monitors are running and in order to work around this, one must be disabled:
$ xrandr --output DVI-1 --off

Also note, the only game I've tried that is playable at all is CS: Source. Every other game experiences its own set of bugs/crashes. However you may have better luck. My sample size is quite low, consisting of all the GTAs and the 2 Halos out for pc

[whizse]

i test some of my games no directX game work for me on the radeon opensource driver.

it always tells me that i need to install the directX9 sdk but i do have install all dx stuff.

i think openGL3.2 is needed by wine.

Nope. Either the games you're trying to run isn't well supported, or you're Doing Something Wrong?.

[whizse]

Intel support for Wine is spotty at best. I have filed quite a few bugs. Some are specific to the i965 driver (such as Portal being broken) others seems to be specific to Mesa as a whole.

I doubt Wine (and gaming in general) is a priority for the Intel developers at the moment. But given time, I hope things will improve.

[curaga]

Any news on how Intel works now that it supports GL 2.1?

[bridgman]

In theory the higher GL levels will come "for free" once a Gallium3D driver is available. It obviously won't be that easy but it does mean that OGL 2.x support is mostly likely to come after Gallium3D has replaced the current hardware driver layer in Mesa for ATI/AMD parts.

Gallium3D in turn relies on DRI2 and GEM/TTM support, and it's GEM/TTM where most of the "development pressure" is being felt today (since having a solid GEM/TTM implementation is also a pre-requisite for enabling Kernel ModeSetting (KMS) by default.

Getting GEM/TTM into the upstream kernel is really what will gate most of the other bits. Once it is accepted into the kernel that means the upper level drivers (the X driver and Mesa) can rely on having kernel video memory management, which in turn allows developers to focus their efforts on getting DRI2-based drivers (including Gallium3D) ready for shipped in distros.

Fedora is already shipping most of these bits, but that requires it to run ahead of the upstream kernel in a number of areas.

[fermulator]

Any progress on this front Bridgman?

Curious to know when the "needed OGL extensions" required by many games run in WINE would be available in the open source Radeon driver?

[bridgman]

We're trying to find out -- specifically to find a better way for "Wine problems" to get translated into "OpenGL problems" to make it easier for the core OpenGL team to work on them. I suspect that some of the problems will be fglrx-related in that they are caused by changes in the OpenGL functionality, and others will turn out to be wine-related in the sense that they are caused by assumptions made by the wine devs about how our driver stack behaves which are not related to the OpenGL API.

[Extreme Coder]

I don't remember seeing many posts about running Wine on Intel graphics - good *or* bad. My *guess* would be that Wine on Intel open source drivers would be a bit better than on our open source drivers, if only because the driver support has been available for longer, but I don't really know for sure.

My understanding is that the Intel open source drivers are around GL 1.5 while the ATI open source drivers are "1.3 with nearly all of the 1.4 features". Not sure exactly how that maps into which apps run well on Wine.

So the wine issue is not from a problem of fglrx's new 3D stack?

[bridgman]

I see.. but wouldn't that mean that those with Intel cards can't use Wine?

I don't remember seeing many posts about running Wine on Intel graphics - good *or* bad. My *guess* would be that Wine on Intel open source drivers would be a bit better than on our open source drivers, if only because the driver support has been available for longer, but I don't really know for sure.

My understanding is that the Intel open source drivers are around GL 1.5 while the ATI open source drivers are "1.3 with nearly all of the 1.4 features". Not sure exactly how that maps into which apps run well on Wine.