http://bugs.winehq.org/show_bug.cgi?id=25640
--- Comment #9 from Brandon Howard FinalCrisisSX@Hotmail.com 2011-04-23 00:24:11 CDT --- (In reply to comment #8)
(In reply to comment #7)
I did a regression test, and came up with:
a59d0f45c1ab26c4754c9eb5d8c730a5dc997ba1 is the first bad commit
For me, both a59d0f45c1ab26c4754c9eb5d8c730a5dc997ba1 and the commit right before that produce the reported problem. Does the game really start for you normally with the commit before a59d0f45c1ab26c4754c9eb5d8c730a5dc997ba1?
I'm sorry, I'm completely inexperienced with git. "Git log" shows the commit 966d722752b659a12ffa355a1e559f94907cd66d as the one "right before".. is that the one you're talking about? Judging by the description, it doesn't make sense to me that one wouldn't work, but it appears to be the one you are requesting. If that is the correct commit, I just ran "bisect reset 966d722752b659a12ffa355a1e559f94907cd66d" and checked "git log" to see if it was in the right place, and indeed that was at the top.. recompiled, game runs fine. Did the same to go to a59d0f45c1ab26c4754c9eb5d8c730a5dc997ba1, and it's broken again.
....In a nutshell:
Works: 966d722752b659a12ffa355a1e559f94907cd66d $ ./wine --version wine-1.3.4-119-g966d722
Broken: a59d0f45c1ab26c4754c9eb5d8c730a5dc997ba1 $ ./wine --version wine-1.3.4-120-ga59d0f4
Judging by the 119 and 120, I don't think I did anything dumb. If I did however, let me know.