https://bugs.winehq.org/show_bug.cgi?id=53697
--- Comment #73 from Yulian Kuncheff yulian@kuncheff.com --- (In reply to jhu543369 from comment #72)
esync/fsync disabled was for removing a variable from the testing during the issues with 8009/8012. Some people, including myself, have noticed that Battle.net won't start first time or will start and be unresponsive at the login screen. Sometimes wineserver will core dump, other times not. This is related to having esync and/or fsync enabled for Battle.net (kernel and wine version did not seem to matter). It does not affect any of the games. If it is an issue, point to the game directly and only use battle.net for updates. If your battle.net always starts 100% I would love to know your config so I can try it here.
I mean, mine has always started 100% using Bottles, turning off the runtimes, and using FSYNC since you can't have ESync and FSync on at the same time in bottles. I also then on FSR on ultra quality. I think the rest of the settings are on defaults. Using latest versions of WineGE and everything else.