http://bugs.winehq.org/show_bug.cgi?id=12964
--- Comment #123 from dk developer@gaminglounge.com --- @JHaleIT - I'm just as surprised as you that it works but I have no idea why it would. Anything I can think of is just speculation. I would assume that the official AMD supported Linux driver (I was using the last stable release) would be good (meaning thoroughly tested).
I mean - what are the odds that this bug occurs on both the official NVidia and AMD drivers? It could be something with the Linux Kernal but then how are the open source drivers working? Even if the open source drivers aren't working properly (and are somehow able to skip whatever is causing this issue) THAT bug in itself is probably valuable because it really narrows down where we should look at in the Wine code. So again - it seems like it's back to Wine.
I found myself wondering that if this problem exists in the kernal/drivers shouldn't we be seeing other issues from other games that are using the d3d8 apis?
@Brian - back around comment 62 I was using a different computer with a Nvidia card. Disabling the sound resulted in a more specific error related to direct3d. I *think* that around that time (Wine 1.3-ish) Wine was undergoing a sound architecture revamp. Sound cut out on a couple of non-related games that I had tried to play and I was told to wait for Ubuntu to catch up.
I'm still not sure what caused it but the errors did seem more meaningful with the sound off.
I did have sound enabled with the open source drivers so it looks like that problem has been fixed (or maybe the AMD chipset I'm using isn't as affected?)