Latest version available.
I only tested Singleplayer gameplay and the Underground DLC as singleplayer.
What does not
Installation of the uplay client requires corefonts. Otherwise there is only a transparent uplay client window.
For some unknown reason the game doesn't launch when being launched by the uplay client directly without an exisiting Steam for windows installation to the same prefix, which does launch the uplay client before. The program file "TheDivision.exe" terminates itself a few seconds after launch. See Bug 45927
The in-game overlay crashes the game when it tries to login to the Ubisoft servers when loading.
My workaround for those of you that own the uplay version of The Division:
1. Make a separate prefix for The Division only. I called mine 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 call your prefix)
3. Install corefonts and the latest dxvk with winetricks
4. Install the uplay client, start it and download and install The Division. If already installed from previous tests point uplay to your existing The Division installation. When finished close the uplay client
5. Install Steam for windows in the same prefix and let it run
6. In the Steam client go to "Games" -> "Add a non-steam game to my library" and choose the uplay client
7. Start the uplay client with steam
8. Disable the in-game overlay in the uplay client and in steam. Otherwise the game might crash when it tries to login on the Ubisoft servers
9. Start The Division from the uplay client
10. Play The Division
When you start Steam from command line and click on "Play The Division" in the uplay client and see the following output:
01b2:fixme:heap:RtlSetHeapInformation 0x6d0000 0 0x22e740 4 stub
and The Division does not start within 30 to 60 seconds after, then it just hangs somewhere.
In this case kill the TheDivision.exe process and start it again with the uplay client.
What was not tested
On its first start the game lagged and stuttered somewhat but that stopped after a couple of minutes of gameplay.
Otherwise I do not see a difference compared to an installation on windows.
- AMD FX 8320
- AMD Radeon RX580
- amdgpu open-source driver
- openSUSE Tumbleweed 20190219 64-bit
- Kernel 4.20.7-1-default
- Mesa 18.3.2 with LLVM 7.0.1
- Plasma 5.15
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||openSUSE Tumbleweed (rolling release)||Mar 04 2019||4.3||No, but has workaround||Yes||Yes||Gold||Freigeist|
|Current||openSUSE Tumbleweed (rolling release)||Feb 26 2019||4.2-staging||No, but has workaround||Yes||Yes||Gold||Freigeist|