#wine-staging

slackner, ping?

brunojesus: yep?

slackner, hello my friend. any news in that WSASend bug?

brunojesus: could you test with the updated completion notification patchset?

sure, can you point the patch?

why don't you think it's an application bug? it would make things easier XD

brunojesus: https://github.com/wine-compholio/wine-staging/... - patch 1 should be sufficient, this is the patch which (most likely) caused the issue

brunojesus: well, as i already pointed out, the existance of this function triggers a different code path, and you weren't able to reproduce without it ;)

slackner, vanilla + first patch is enough then?

brunojesus: yep

or whole patchset?

ok

slackner, 30 tests no crash. I'm reverting the patch to test again

slackner, I'm convinced already.

the patch is good, it is a staging bug that is now fixed with the new set

brunojesus: kk, thx for testing

Have you started to build staging 2.1 yet?

If not, silencing dx11 set blend state would be nice

Yoshimo: no, it has not been released yet. nevertheless, whats the purpose of silencing one fixme when there are most likely a lot more in the d3d11 area? ;)

Yoshimo: not sure if you are aware, but you can start wine with WINEDEBUG=-all to avoid unnecessary performance impact

if you print it once it keeps the logs clean to check for other things. You do a "repeat once" for a few other fixmes already

Yoshimo: well, is this fixme the only one which spams in the console output?

i will verify that

fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not implemented.

fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not implemented.

the rest is ok

https://bugs.winehq.org/show_bug.cgi?id=42017 basically

i wonder when mesa-senpai will notice me/my bug report