http://bugs.winehq.org/show_bug.cgi?id=29236
--- Comment #4 from Henri Verbeet hverbeet@gmail.com 2011-12-07 08:50:51 CST --- (In reply to comment #2)
I'm using an Nvidia 540M card running via VirtualGL to Sandy Bridge graphics (I'm using ironhide). So has anything changed that might have confused VirtualGL?
I think that could be significant. I don't have that kind of hardware, so not a lot of experience with VirtualGL, but if I understand correctly it redirects some X11 / GL calls to a different GPU.
The main difference between before and after that commit is that we now initialize GL and create the corresponding window earlier for ddraw. That means that in some cases we may now have two GL contexts active at the same time while previously we didn't. That shouldn't be a problem by itself, but I suppose if something messed up X or GL synchronization you could get that kind of BadDrawable errors. I suppose it would be useful if anyone could reproduce this without VirtualGL, since we could rule that out as a factor then.