[Bug 45927] Tom Clancy' s TheDivision.exe terminates itself a few seconds after launch

[wine-bugs at winehq.org]

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

--- Comment #36 from Freigeist <m4ng4n at gmx.de> ---
First things first.

Revisiting.

wine 4.3 and wine 4.3-staging

Using the uplay client I can confirm that with both wine versions the error is
gone. It is now possible for me to run the The Division without the workaround
in comment 29 with the uplay client directly.

For others to test: This is the way that worked for me

1. Make a new separate prefix for The Division only. I called it
wine-division-64

2. From now on do every step below pointing wine to this prefix with
WINEPREFIX=$HOME/.wine-division-64 (or whatever you called your prefix)

3. Install corefonts and the latest dxvk with winetricks

4. Install the uplay client, start it from the commandline and point it to your
existing The Division installation, otherwise download and install The
Division.

5. Disable the in-game overlay in the uplay client. Otherwise the game might
crash when it tries to login to the Ubisoft servers

6. Start The Division with the uplay client

7. When you start the uplay client from command line and clicked on "Play The
Division" and see the following output on the command line and the command line
output stops there:

01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub

and The Division does not start within 30 to 60 seconds after you clicked on
start, then it just hangs somewhere.
In this case kill the TheDivision.exe process and start it again with the
uplay client.

On wine 4.3 this happened to me 3 or 4 times before The Division finally
started.

8. Now give it a try on your machines

-- 
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.