Larian Studios Forums Divinity: Original Sin 2 Divinity - Original Sin 2 - Bugs & Technical Problems Linux support

Since there are a lot of people waiting for Linux native release, maybe it is already possible to play DOS2 as we are waiting. I have tried to run DOS2 on Linux with Wine. Currently, it works fine with few already described problems.

[b]My setup is:[/b]
- Ubuntu 16.04, NVidia 980 GTX. (will fill more info if it's relevant)
- Lutris (https://lutris.net) as the client for Wine
- Wine 2.16-staging 64bit
- Steam

I'm running game on Ultra settings, the game works fine, with some problems (already mentioned), so I'll list them here.

[b]Known problems:[/b]
- buff/debuff icons next to character are not rendered properly, they are black (but mouse over information works)
- when you open book, it's black (but if you have a book with multiple pages and you move the mouse over the black area, in some places UI for changing pages is rendered and that also renders text properly, so you are able to read it)
- performance decreasing (I didn't yet figure out real reasons, but I have noticed few things. After some period of playing, fe. 1 hour or so, decreased performance is noticeable. When I cust some spells that have extensive animation around a character, performance also gets decreased, but for this, I'll try some staging options + game settings.)
- sound noise (I hear some click-click noise, but that's not so relevant)

[b]Solutions[/b]
- performance decreasing (keep Steam client running, enable staging settings and change anti-aliasing to FXAA)

Additional problem is that I'm not able to run game from Steam client. So I use Steam client to update the game, but when I want to run it, I'm using executable directly in "steamapps" folder.

From my point of view, if books and buffs would be rendered properly, DOS2 would be playable on Linux.

If someone also experimenting with Wine please share your experiences. It would be nice to collect problems and possible solutions in order to have DOS2 playable on Linux.

Dear Mtodor, here you are:

On my system the release version - contrary to the latest beta two days before - doesn't work,

My setup is:
- Antergos 64bit
- 4 GB Sapphire Radeon R9 380X Nitro with latest Mesa-drivers (open source)
- Intel i5-2500K CPU @ 3.30GHz × 4
- 16 GB RAM
- Play on Linux as Wine Client
- wine 17 (tried wine 16-staging as well)
- Steam running under POL, installed as described on winehq (report for: Arch Linux x86_64, Aug 25 2017, 2.15-staging, by: writergeek; PLEASE NOTE other games update and run on this Steam installation!)

Installing the game via Steam (for Windows) on a 64bit Wine worked.

Issues:
- couldn't install dotnet35, 40 etc. (neither via POL nor via console and wintricks) in my 64bit-Prefix (error: "Doesn't install on a 64bit-Prefix")
- whilst the latest Beta worked rather flawlessly still on April 13 2017 (!) the release version causes some Directx11 related errors and just crashes.

Workarounds:
1) Steam button actually launches "SupportTool.exe" from .../steamapps/common/Divinity Original Sin 2/bin
which causes a .NET Framework error.
- (well known) workaround: Launching Divinity via the "EoCApp.exe" within the same directory

2) Next: ntlm authentification error
- workaround: installing the "python2-ntlm-auth" packages

3) Finally "BAD WINDOW" error
Tried registry workaround: "MaxVersionGL key to the (DWORD hexadecimal) value 30002", but Divinity just shows its mouse cursor on my desktop and crashes.

Let's hope we find a general solution or proper general work around soon. Thank you very much!
Cecco

EDIT: Just ran it again in windowed mode (set via winecfg), now I 'merely' get this error:

fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported.
Please configure the application to use double buffering (1 back buffer) if possible.

Is there a way to fix this manually via registry entry?

PS: DoS 2's graphics settings can be changed manually by meddling with its config-file

graphicSettings.lsx

in an editor.
(Remember to create a copy, e.g. graphicSettingsOLD.lsx, first!)

It can be found in:

[YOUR_WINEPREFIX]\drive_c\users\[YOUR_USER_NAME]\Documents\Larian Studios\Divinity Original Sin 2

Possible workarounds attempted in my case:

- setting VSync and Triple Buffer Settings to "0" didn't help.
- neither setting everything to "Low" and "0"
- nor adjusting screen size, or anything else I changed

=> nothing works

Last night I've changed few things:
- enabled all staging settings for wine
- kept Steam client running (before I didn't run it at all during gameplay)
- changed in settings anti aliasing to FXAA

I played for 2-3 hours and I didn't notice any performace drop.
I'm not sure what really helped, but it could be useful hint for others.

It looks as if there were presently a problem with AMD graphics drivers and the related Mesa libraries, whilst a Nvidia gpu seems to cause no trouble.

So I'll have to try again with each Mesa update and new version of wine - and report back here (and on winehq).

After some more fiddling I suppose my problem may have to do with the running version of OpenGL since I am initially getting this error:

"winediag:wined3d_adapter_init GL_ARB_compatibility not supported, requesting context with GL version 3.2."

Hence, what does your console turn out when you enter?

glxinfo | grep OpenGL

On my system it's

@Cecco - did you check this post: [url=https://forum.winehq.org/viewtopic.php?f=2&t=29362]https://forum.winehq.org/viewtopic.php?f=2&t=29362[/url]

Much obliged for your commitment!
Yes, I know that thread.

- Already tried the

export MESA_GL_VERSION_OVERRIDE=4.5

console-trick.
Result: version override to "=3.2" and "=4.5" works, yet the GL-version error persists.
Shall keep on experimenting and posting if I come across further workarounds and hopefully solutions.

@Cecco here is my output of:
glxinfo | grep OpenGL

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 980/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 375.66
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.0 NVIDIA 375.66
OpenGL shading language version string: 4.50 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 375.66
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Thank you.
Now I suppose even more that my issue is related to my AMD gpu and its drivers.

*

By the way:
According to this thread on the compatibility of save games from beta versions there should be a 'rollback' option to pre-release versions in the Steam library

""
In your Steam library, right-click on the game and select "properties". The "betas" tab is at the top right of the pane that pops up.
""

Yet although I had a beta running before release on the very Steam install within the very Wine-prefix I when following these instructions just get told that I hadn't participated in any beta - which might as well bug of Steam incapable of accessing all online data under Wine... dunno.

There is a new release of Wine, wine 2.17-staging. I have tested it and I didn't notice any improvements (issue with books and icons still persists). Additionally, I have noticed that ability icons get black when you click on them in order to cust spell, so to say, when they are activated (it could be that same issue exists on 2.16-staging, but I didn't notice it yet).

No matter what I try, it doesn't run. Something about missing shaders in the console.

My glxinfo

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 970/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 384.69
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.0 NVIDIA 384.69
OpenGL shading language version string: 4.50 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.69
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Game used to run perfectly under the Beta except for the blank books which was neglegible.

Now it outright crashes and writes a minidump. https://paste.laravel.io/4a494764-0ebc-499f-8df6-9dd43a6ac891

I tried installing xact, dotnet40, nothing works.

I'm using latest wine-staging on ArchLinux with nvidia card. mtodor there must be something special in your configuration.

Please save me from dual booting, Windows is a complete headache. I'd rather being unable to read books than booting Windows.

Overnight I made a fresh download via a re-installed Steam in a clean new prefix under Wine 2.17-staging

=> same errors, nothing works.

Since NotFood's system is affected as well, I fear the problem is not AMD-specific as I had thought.


@mtodor: Being unfamiliar with Lutris (which by the way lists a garbage-rating for the DoS 2 beta, from Nov. 2016), did you use any script or settings from a database (as e.g. in PlayOnLinux) when you installed Steam under Linux and thus changed settings and added libraries we are not aware of yet?

EDIT: Just got a bit familiar with Lutris, which I downloaded, and then launched Steam (for Windows) and DoS2 through (NB: I made no new install, just browsed into my existing Steam folders) that Client and its stock wine 2.15 settings => DoS2 doesn't work.

@mtodor: Could you maybe divulge your Lutris "Runner Options"? Or is there an installer script (either for Steam or DoS2) one can only see/download after one has registered there?

Thank you in advance!
Cecco

I'll put short guide here what I did, because I had help from some guy on #playonlinux irc channel and he helped me a lot with setup, so I'm not sure do I remember everything correctly.

1. I updated winetricks - https://github.com/Winetricks/winetricks (I think this step is not relevant, since Lutris uses it's own version)
2. Installed latest version of Lutris for my distribution - in this case 0.4.13
3. In Lutris - I have downloaded staging-2.16 (it's kinda strange way to do it: in Lutris application menu click -> Lutris -> Manage runners -> find Wine (not Wine Steam) -> click Manage versions -> there you have list with checkboxes - it behaves strange there, because checkboxes are not relevant, you just have to click once on it and wait -> and download will start.

--> now we have all pre-requirements - and it's time to create wine prefix.

4. Open Lutris -> click "+", to create new game
4.1. Game info Tab
4.1.1. Name - write some name for Game (Steam, SteamDOS2, whatever.)
4.1.2. Runner - select to be Wine (not Steam, not Wine Steam, just Wine) - It's written: Wine (Runs Windows games)
4.2. Game options Tab
4.2.1. Executable - select any dummy file that can't be executed, like txt, pdf, whatever (it's important for some steps later)
4.2.2. Wine prefix - set directory name, has to be full path, fe.: /home/mtodor/lutris-steam64
4.2.3. Prefix architecture - 64-bit (this is important, I don't think so, that DOS2 works on 32-bit platform)
4.3. Runner options Tab
4.3.1. Wine version - staging-2.16-x86_64
-> everything else default
4.x click Save to finish creation of Lutris Game (if game doesn't appear, close Lutris and open)

5. Run created Lutris Game - it should fail (since not executable file is used), but correct wine prefix folder should be created
5.1. (optional) double check if version of wine prefix is correct: go in wine prefix directory (fe.: /home/mtodor/lutris-steam64), and "less system.reg", you should see: #arch=win64

6. Right click on game icon in Lutris and select Winetricks
7. Select - Install an application -> click OK, then click Cancel on next dialog
8. then you should get new dialog with option - Install a Windows DLL or component, select that and click OK
9. on next dialog select dotnet40 -> click OK (that will finish with some error, what you can ignore)

10. again, Right click on game icon in Lutris and select Winetricks
11. Select - Install an application -> click OK
12. on next dialog find Steam and select it, click OK to install, it will finish installation

13. Right click on game icon in Lutris and select Configure
14. go to Game options tab and set Steam as Executable - fe. /home/mtodor/lutris-steam64/drive_c/Program Files (x86)/Steam/Steam.exe
15. In Arguments add: -no-cef-sandbox (that should help Steam to work properly in wine)

Next step is to run Lutris Game, that should open Steam and you should install DOS2.
If you already have installation, you can just start installation in new Steam (so that it start downloading) and then turn Steam off, copy manually "steamapps" from previous installation to new "steamapps" location.

After installation is finished start Steam and start DOS2 from Steam -> it should install some dependencies and fail, after that you can do following.
1. Right click on game icon in Lutris and select - Run EXE inside wine prefix
2. Navigate to "EoCApp.exe" - fe. /home/mtodor/lutris-steam64/drive_c/Program Files (x86)/Steam/steamapps/common/Divinity Original Sin 2/bin/EoCApp.exe
3. And execute it, game should run!

If that doesn't work, you can try following:
- install latest version of Mono that wine prefix (download from http://www.mono-project.com/download/#download-win 64-bit version) and same as I have explained before, select "Run EXE inside wine prefix" and run that installable
- install additional libraries over winetricks - fe. d3dx10, d3dx10_43, d3dx11_43, directx9, vcrun2015

=> problem is that I have tried a lot of things before I tried to run DOS2 directly, that's why I'm not sure, are some parts relevant or not.

I hope so I didn't miss anything and that this guide will be helpful for you.
Good luck!

P.S. for some reason I can't edit first post.

@mtodor:

Wow! That's detailed! Kudos!
Shall try that out as soon as I have the time and report back!
Cheers!
Cecco

@mtodor
Alright, just followed your instructions, found out a few new things en route, yet didn't get it running, alas.

Here's what I did:

1) updating winetricks
- skipped, as you suggested

2) installed Lutris 0.4.13
3) downloaded wine staging-2.16 via Lutris > Manage Runners > Manage Versions

4) repeated everything step by step exactly as you told (from 4.1 to 4.3.1/4.x)

5) Running dummy fails, as planned
5.1) doubled checked prefix structure/content – looks alright

6-9) Lutris' winetricks: dotnet 40 – check

10-12) Lutris' wintricks: steam – check

13-15) Steam.exe as executable + -no-cef-sandbox as argument – check - check

Next:

- Running Steam through that Lutris, starting to install DoS2, interrupting, moving my latest Steam download into my /steamapps-folder within the Lutris-prefix – check

OF NOTE: Steam looks better (fewer font and display bugs) and seems smoother than my last POL-installation, which also runs with the -no-cef-sandbox argument.

IMPORTANT: Also copy your appmanifest-files from the old /steamapps-main folder into the new one.
Otherwise Steam won‘t recognise the existing game files and folders and just download everything again – which would take about 5h on my computer.

- Then I had the pasted files checked via the the DoS2 > rightclick > properties tab in Steam.

- Starting DoS2 through Steam => some downloading (.NET framework… 3/5) and failing (as expected)

EDIT: One should add vcrun2015 via Lutris'winetricks first, for then the .NET-downloading can be completed with 5/5 and doesn't get stuck at 3/5.

- 1st try to run DoS2: Run EXE inside prefix with "EoCApp.exe" => failed, just mouse cursor and crash

adding libraries via Lutris'winetricks:
all d3dx-versions + directx9 are already there, so I just added vcrun2015

- 2nd try to run DoS2: Again Run EXE inside prefix with "EoCApp.exe" => failed, just mouse cursor and crash

- 3rd try: Second launch of DoS2 via Steam in order to complete the .NET-Downloading (as in EDIT above), then once more Run EXE inside prefix with "EoCApp.exe" => failed, just mouse cursor and crash

Switching to Wine 2.17-staging (as additional Runner-version)

- 4th try: just mouse cursor and crash

Installed, as you proposed, mono for Windows 64bit; downloading and running as EXE in prefix.

- 5th try: just mouse cursor and crash

*

Well, at least I get to know a new Wine-Client, learn a few things and am part of a great supportive Linux community

@mtodor

PS: As you wrote that you "tried a lot of things before" running DOS2 through EoCApp.exe, are there any Windows-dlls ticked off on your Lutris-winetricks-list apart from these here? Or have any wine-settings, wine-cfg boxes checked/unchecked that could further my issue?

- d3dx10_43 down to d3dx9 (each one checked)

- directx9

- vcrun2015

- xact
- xinput

(installing dotnet40 doesn't somehow result in it being checked on the list)

@Cecco

When it comes to libs installed, I have:
- from d3dx10, untill d3dx9_43 everything checked
- directx9
- vcrun2015
- xact
- xinput
- dotnet40 - is not checked, because you get error on install, that's why it's not checked.
=> so more or less same as you

What you can try is to run Lutris from console and then you will be able to see errors, maybe that can help a bit.

Additionally, in properties for DOS2 in Steam (right click -> Properties) - I have disabled both options on General tab.

In Wine configuration (right click on Lutris Game -> wine configuration), I have Windows 7 as Windows Version.
On Graphics Tab - first 3 options checked. Staging options -> all checked. (but games runs when all are unchecked too).

-= Some exp with playing =-
I have played already 18 hours. Books are problem, some of them are relevant for quests, but you can just open them and close, and quest log will get updated, also recipe books -> just open them and recipe will be added. Some books can be viewed, so I check every book if readable or not -> after that I'm selling them.
Skill books work properly. Performance is also fine.

I have basically the same setup as @NotFood, get the same result. Tried everything, the game just crashes and writes a MiniDump.

The native port can't come soon enough...

@mtodor
Again I am very, very grateful for your assistance!

Here is what I further did and what came out:

- Matching my Lutris-wine-settings (staging-tab, graphics-tab) with yours => mouse cursor, crash

- running Lutris in the console produced this error:
"err:winediag:wined3d_adapter_init GL_ARB_compatibility not supported, requesting context with GL version 3.2."

(manually overwriting the GL version with
export MESA_GL_VERSION_OVERRIDE=3.2 doesn't help)

- Since (without override)
glxinfo | grep "OpenGL version"
produced
OpenGL version string: 3.0 Mesa 12.1.4

** THE FOLLOWING ISSUE JUST CONCERNS ARCH/ANTERGOS:

Hence I realized that something must have gone wrong when updating via console (and Pamac) on Antergos, since today's Mesa for Arch/Antergos should be Mesa 17.2.1.

There is - as I found out in the Arch forum - actually an updating issue affecting Arch/Antergos-installs from an 'old' ISO ('old' meaning before February 2017, which is my install)
being caused by 'unknown' signatures from one "Anatol Pomozov" and keeping updating from completion.

If any other Arch-user has this problem as well: The solution can be found here in the Arch Forum. (AT YOUR OWN RISK!)

When updating afterwards I ran into a ca-certificates-utils error, which is solved as described here. (AT YOUR OWN RISK!)

And while running "sudo pamac -Su" I had to apply the "Anatol Pomozov" key-ring upgrade once more.

** END OF ARCH/ANTERGOS-ONLY PROBLEM

- Now:

glxinfo | grep "OpenGL version"

shows:

"OpenGL ES 3.1 Mesa 17.2.1"

=> BUT DOS2 won't start and the selfsame problem persists with the very

"err:winediag:wined3d_adapter_init GL_ARB_compatibility not supported, requesting context with GL version 3.2."

when running Lutris from console and then EoCApp.exe in the prefix.
(Neither does "export MESA_GL_VERSION_OVERRIDE=3.2" do the trick, nor manipulating the Registry as expounded in the Wineforum-Post, we mentioned above. )

*

@mtodor
PS: Don't worry about the black books in DOS2 since we are writing the great Divinity-and-Linux-Saga here