http://bugs.winehq.org/show_bug.cgi?id=7584
------- Additional Comments From a.hurst@shef.ac.uk 2007-05-03 13:12 ------- Ok, the interesting bit is in a function called SetExecuteBufferDefaults in d3d_render.cpp
You can follow it in the trace right up until it calls SetExecuteBuffer, where out of nowhere, a call to EndScene turns up.
The return value from EndScene changes the behaviour from here on, despite the fact that in the entire AvP code the EndScene return value is never used, except to print a message using LOGDXERR.
Weird.
Were it not for the fact that _nowhere_ in the AvP code is EndScene called without a BeginScene first, i'd be suspecting a problem with handling of the so-called "RasterThread"