https://bugs.winehq.org/show_bug.cgi?id=49942
--- Comment #4 from nvaert1986 nvaert1986@hotmail.com --- (In reply to Sveinar Søpler from comment #3)
Since you mentiones "ebuilds", does that indicate Gentoo? If so.. Are you compiling wine --with-mingw ? (Loads of PE dll work has been done as of late, that may break some games if NOT compiled with mingw-w64)
In the case of you actually using mingw-w64, wine-staging-5.0 is somewhat "old", so upgrading the wineprefix -> wine-staging-5.18++ might break stuff.
I think i had some problems needing me to redo my prefix when coming from wine-staging-4.x -> wine-staging-5.x due to some leftover crud on my wineprefix i run battle.net games from.
I am not sure what you mean by "clean install", but if that only means reinstalling the game from the Battle.net app itself, it probably will not do much if it is "old prefix crud" messing stuff up.
Battle.net works fairly well re-using your old game install if you just create a new wineprefix and moving the game folders over to the new wineprefix, and let the Battle.net client search for games.
With re-installing battle.net I mean removing my wine prefix using rm -rf .wine in my /home/username directory (which is the default prefix). There I completely re-installed everything twice. The installation of Battle.net and starting Battle.net works fine, but starting any of the games does not. Whenever I switch back to wine-staging.5.0 and start any of the games, they work flawlessly using the prefix created with wine-staging-5.18.
I'm using Gentoo indeed. I'm not compiling with mingw or mingw-w64. I'm using GCC 9.3.0 using -O2 and --march=znver1 those ore the only flags set.
I just started a compilation to double confirm if mingw is being called, but when watching the compilation, mingw is not being called at all.
The only difference as of recent is unwind support, which I disabled, which is set through a USE flag, but which I don't need.