http://bugs.winehq.org/show_bug.cgi?id=12929
--- Comment #31 from Daniel Scharrer dscharrer@gmail.com 2008-06-10 08:31:30 --- (In reply to comment #25)
This is most likely not a wine problem, but rather an ATI driver problem.
Yes, but most likely just isn't good enough to report a bug, now isn't it. After all, you wouldn't be very happy if people started reporting bugs for wine where wine is actually working perfectly, but the application is full or bugs (but may work on some version of windows running on some obscure hardware), right?
(In reply to comment #27)
The 'other linux games work well with my driver' argument doesn't hold.
Neither does the 'wine works with well with other drivers/cards' argument. Not that I think that this is necessarily a wine bug. However, while we (wine+ATI/AMD users) cannot show whether this is a but in wine or in fglrx the 'this must be a fglrx bug, since it only appears under fglrx'/'this must be a wine bug since it is only exposed under wine' situation continues and the status quo remains.
And even if this is shown to be a fglrx bug it would be very helpful to know what fglrx is doing wrong / how wine exposes this bug (like for example what GLSL code was passed to the driver), except just expecting the fglrx developers to dig it up themselves. Not that this is in anyway your responsibility, but it would be a more productive response than jast classifying any D3D problems experienced with ATI/AMD cards as fglrx bugs.
If this seems like a rant, I apologize. That certainly wasn't my intention. After all, the wine project is nothing short of a technological miracle and I for one am very thankful for it.