https://bugs.winehq.org/show_bug.cgi?id=38326
--- Comment #9 from swswine@gmail.com --- At the same time I have 3Dmark03 (and 3DMark06 also) working with stock wine version (tested 1.7.53), without any patches. WineHQ database also suggests the same: https://appdb.winehq.org/objectManager.php?sClass=application&iId=3120
I am pretty sure so far that indexed vertex blending is not used there. I can hardly imagine how the changes made by the patch can trigger the fix for your problem. Most likely there is some other difference. Did you make both builds of wine (with and without the patch) yourselves the same way and installed 3DMark the same way to clean wineprefix? If you are comparing some stock wine build with your build with the patch than the difference might rather come from build environment. Or (the most common reason) can you have different wineprefix setup between the tests?
If you give some details on your test configuration (see below), it may give some chance to guess what can be the reason:
1. wine versions with and without patch (version number and build source: your own, or some prebuilt versions) 2. wineprefix: are you using the same wineprefix for both tests and switch wine versions, or different? Did you start from clean wine prefix in both cases? Do you have any direct3d tuning keys in registry (HKEY_CURRENT_USER/Software/Wine/Direct3d)? 3. Your OS and version 4. Your GPU hardware & driver info (glxinfo | grep OpenGL, or optirun glxinfo | grep OpenGL if using discrete video card with bumblebee)