http://bugs.winehq.org/show_bug.cgi?id=21515
--- Comment #106 from cruiseoveride cruiseoveride@gmail.com 2010-03-03 17:36:09 --- Graphics driver developers are reluctant (at least in my experience) to use WINE as a testing platform to improve their drivers on the basis that it is too time consuming to distinguish, and isolate faults in the graphics stack when there are too many levels of indirection and hacks required to make 3D Windows application run on Linux.
Considering that there is now out-of-the-box basic 3D acceleration for both Nvidia and ATi cards through open source drivers on all the major Linux distributions coming out this summer, the barrier to entry for gaming on Linux through WINE has significantly come down for the average n00b00n2.
Therefore can someone provide a guide for the average desktop-user on how to distinguish faults between WINE's hackery and/or the open source graphics stack in order to debug, trace and document it appropriately with their respective bug trackers and development channels?