http://bugs.winehq.org/show_bug.cgi?id=19848
--- Comment #32 from Henri Verbeet hverbeet@gmail.com 2009-08-27 17:19:45 --- (In reply to comment #31)
Are you no longer seeing the crash from http://bugs2.winehq.org/attachment.cgi?id=23265 ? That part is probably the same as bug 18636.
I haven't applied any patch for source games.
http://bugs2.winehq.org/attachment.cgi?id=23265 isn't a crash. It's the output of wine as it shows the corrupted menu in attachment http://bugs2.winehq.org/attachment.cgi?id=23266 That backtrace is probably from an irrelevant crash on exit.
I have, on the other hand applied http://bugs2.winehq.org/attachment.cgi?id=23268 from bug 18799. The Crysis patch is the one that fixes http://bugs2.winehq.org/attachment.cgi?id=23267
This probably sounds confusing :/
No, that makes sense. Bug 18636 isn't really specific to source engine games, it sometimes happens when a D3D device is use after its associated window is destroyed, usually on exit. I initially thought you had that crash while running the game, in addition to the broken menu.
The broken menu is most likely related to the shader error mentioned above. On that subject, 2 seems rather low as a limit on the amount of temporary registers, so there's a chance this is just a bug in the driver's GLSL compiler.