http://bugs.winehq.org/show_bug.cgi?id=8371
------- Additional Comments From tom@dbservice.com 2007-20-05 12:12 ------- Most likely something in direct3d changed between .32 and .36 that broke yukon. If yukon creates the file and the file contains _any_ frames, than it means yukon hooked into the libraries successfully and is indeed capturing frames. If the image is flipped upside down, it means yukon is being invoked while the framebuffer contains and flipped frame or is being invoked while the framebuffer isn't yet fully drawn.
Can you git-bisect to find where exactly it stops working?