http://bugs.winehq.org/show_bug.cgi?id=12923
--- Comment #11 from Roderick Colenbrander thunderbird2k@gmx.net 2008-05-10 02:41:02 --- The way I wrote the code is that we try to find a pixel format which exactly matches our requirements. The pixel format table is sorted by the display drivers and there is no real pattern in it and it is different for each driver. Further down to the end of the list there tend to be 'extended' pixel formats. Those formats have the same basic properties as the ones at the top of the list but different extended features like multisampling and others.
Due to the sorting of the list we store the first format which reaches the end of the loop (because that format matches out basis requirements). We then continue to look for a format for which depth also matches exactly. If that one is found we break else we use the format which first met our requirements.
It would be useful to see what the requirements specified to WineD3D_ChoosePixelFormat are (what parameters are passed to it). Likely depth/stencil isn't requested. If that is the case we need to know why it wasn't requested.