I wrote a small article (http://eengine.org/en/winehq-how-one-can-help/) about Wine and described there two ideas. The first one is about how in my opinion comminuty could help debugging rendering issues. And the next one about new approach to test D3D-related things (for regression testing, for example). The goal of this post is to ask feedback for QA guys if they think that this could work or not, but my feeling is that it can significantly reduce amount of work needed to resolve rendering issues (at least I hope so). Any kind of feedback is highly appreciated. Best regards, Anton
Haven't quite read the article, but I noticed that you wrote this:> a solid open source project created to add Windows OS capabilities into your Linux.Wine is not *quite* that. The only OS capability that it adds are being able to run Windows programs. Everything else, like driver support (and pretty much everything not in userland), is handled by the OS Wine is running in.
The capture tool that you have posted seems very interesting, I never knew something like that existed. It is certainly very useful for capturing and reproducing areas of a game that has problems. If the tool has proven to work well, perhaps in can be linked in a few of the WineHQ articles about submitting bugs.
I suppose that the tool runs stable enough for Windows and I have tried personally a lot of games on it. I have tried several game frames in Wine as well and some of them (not all) do not work for some reason (but works in Windows). I have tried 1.3.3 branch and possibly they will work with stable branch. As for your comment about "capabilities"/"capability" I am agree with you and I am not against of changing this sentence in the article. Thanks for your feedback.
btw, in case if you have questions related to that tool feel free to ask since i know it very well..