https://bugs.winehq.org/show_bug.cgi?id=41929
--- Comment #9 from leozinho29_eu@hotmail.com --- I wonder how relevant this error message is:
002d:fixme:d3d:texture2d_blt_fbo Unsupported filter mode WINED3D_TEXF_ANISOTROPIC (0x3).
By checking the apitrace I recorded on Windows 10 of Cat Girl Without Salad, there are two different situations where D3DERR_INVALIDCALL was the result. They happen 308 times during the record and seem to be the only errors in the entire apitrace. They are:
367 @0 IDirect3DDevice9::StretchRect(this = 0x4894520, pSourceSurface = 0x48765c0, pSourceRect = &{left = 0, top = 0, right = 1920, bottom = 1080}, pDestSurface = 0x48767c0, pDestRect = &{left = 0, top = 0, right = 1920, bottom = 1080}, Filter = D3DTEXF_POINT) = D3DERR_INVALIDCALL
Which I don't really understand what went wrong. Maybe the destination rectangle is too large? The screen is 1366x768.
407 @0 IDirect3DDevice9::StretchRect(this = 0x4894520, pSourceSurface = 0x48767c0, pSourceRect = &{left = 0, top = 0, right = 1920, bottom = 1080}, pDestSurface = 0x10be720, pDestRect = &{left = 0, top = 0, right = 1296, bottom = 729}, Filter = D3DTEXF_ANISOTROPIC) = D3DERR_INVALIDCALL
Here what caused the D3DERR_INVALIDCALL result is the invalid Filter.
I wonder if the message Wine outputs should be outputted so often or even if it should be outputted at all. On Windows it is an invalid call, but it "fails silently". Isn't Wine working as intended? So, no need for fixme on this particular case?
I compared one of the screens between llvmpipe, i965 (with the patched Wine) and Windows 10 Intel driver. The comparison was made using ImageMagick's compare, the differences are the red elements of the image and its results are below:
i965 and llvmpipe: https://i.imgur.com/5yKw2fO.png Windows 10 and llvmpipe: https://i.imgur.com/ESWYYOt.png i965 and Windows 10: https://i.imgur.com/5vdf0Sw.png
Please note it was not easy to get images with exact same proportions (Windows 10 fullscreen is 1360x768 while Wine fullscreen is 1366x768 for this game), so there is that weird elements at the top right of the screen, but the Humble Original logo is at the exact same proportion and the images are not compressed or scaled to achieve this. To get llvmpipe screenshot I used Xephyr and to get i965 screenshot I created a virtual desktop for Wine by setting it with winecfg.
i965 and Windows 10 Intel driver have nearly the exact same result, while llvmpipe result is different. So it seems Windows 10 Intel driver fall back to the same method i965 does. Maybe now it's just OpenGL vs. DirectX decimals rounding?
Maybe someone with Nvidia or AMD GPUs should check if with their drivers the result for that operations is D3D_OK, but with Intel GPU it is D3DERR_INVALIDCALL.