http://bugs.winehq.org/show_bug.cgi?id=21515
--- Comment #102 from P.Panon ppanon@shaw.ca 2010-03-03 13:30:28 --- Looks like the patch has been accepted so it should be in 1.1.40. That means we can probably close this bug since any remaining rendering/display issues appear to be due to Mesa driver GL API support level & bugs.
On the other hand, someone else might want to file a bug on the vidmem issue discussed in comments #79 -> #84 so that it get looks at further. That value appears to be set correctly in Wine's internal data structures by ..._guess_card() but not used/reported by whatever Direct3D API call 3DMark2001SE is using. That probably significantly affects performance since the application likely wouldn't attempt to load textures and 3D data into video memory as a result, causing them to be loaded more slowly from main memory instead.
I was thinking that maybe the issue is that the D3D API used is supposed to return dynamic values instead of static maximums. Perhaps those functions haven't been implemented yet. If so, then hopefully those functions will have FIXME/WARN entries and someone can rerun a trace after 1.1.40 comes out and look for FIXME output that would indicate what those functions might be.