[Bug 49942] Games on Battle.net refuse to launch using either wine-5.18 or wine-staging-5.18

[WineHQ Bugzilla]

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

Sveinar Søpler <cybermax at dexter.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cybermax at dexter.no

--- Comment #3 from Sveinar Søpler <cybermax at dexter.no> ---
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.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.