Divinity Original Sin 2 appid 435150

[FreeLikeGNU]

D:OS2 will not start after installation (SupportTool.exe). Some users report that using the EoCApp.exe and WINE dll override xaudio2_7 allows the game to run, but for me, I get only as far as a black screen and the game cursor with those modifications.

OS: Ubuntu 18.04 bionic
Kernel: x86_64 Linux 4.15.0-32-generic
Resolution: 1920x1080
DE: XFCE
WM: Xfwm4
CPU: Intel Core i5-3470 @ 4x 6.3GHz
GPU: GeForce GTX 1070 driver 396.54
RAM: 2030MiB / 15989MiB

[KGOrphanides]

I'm not having any joy with installation, either. No useful error message at command line, but installation appears to fail during or just after Microsoft DotNet framework.

EoCApp.exe can be made to run using standard Wine 3.0.2, but blackscreens.

Distro: Ubuntu Mate18.04
Kernel: 4.15.0-32-generic
Resolution: 1920x1080
CPU: AMD Ryzen 1600 six-core
GPU: 4GB AMD Radeon 6990 (Caymen), Padoka driver (see https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa)
RAM: 16GB

[nstgc]

It certainly seems to me as if the issue is .Net. In CrossOver I had been able to run it perfectly by simply specifying the executable (and skipping Steam).

[FreeLikeGNU]

I renamed EoCApp.exe to SupportTool.exe for it to load with proton. I used proton_winedbg_run (modified to override xaudio2_7) with the following results (black screen, game cursor):

./proton_winedbg_run2
wine: Call from 0x7b43c45c to unimplemented function mscoree.dll.CorIsLatestSvc, aborting
wine: Unimplemented function mscoree.dll.CorIsLatestSvc called at address 0x760023:0x7b43c45c (thread 0015), starting debugger...
WineDbg starting on pid 0035
0x000000007bc8f905 DbgBreakPoint+0x1 in ntdll: ret	
Wine-dbg>next
start_process () at /home/proton/proton/wine/dlls/kernel32/process.c:1067
1067	    return entry( peb );
Wine-dbg>next
Thread ID=0041 not in our list of threads -> can't rename
Thread ID=0042 not in our list of threads -> can't rename
Thread ID=0043 not in our list of threads -> can't rename
Thread ID=0044 not in our list of threads -> can't rename

https://paste.ubuntu.com/p/XhcsthMtwd/

[FreeLikeGNU]

Tried again with some overrides and taskset -c 1 (as suggested by this workaround: https://bugs.winehq.org/show_bug.cgi?id=29215)

please see this gist:
https://gist.github.com/FreeLikeGNU/efb26bebb40fc13a3fb78f2c0b0c78f5

[nstgc]

@FreeLikeGNU Did it work? I'm assuming it failed, but could you clarify?

[FreeLikeGNU]

@nstgc It failed with the same result of black screen and game cursor, but I got more information from the debug output, so maybe a step closer?

[nstgc]

Error logs are indeed a step forward!

[notfood]

I get the exact same error.

Some people have had success by just renaming the app. Most likely a video driver issue.

[FreeLikeGNU]

@notfood and anyone else getting this, it may help to post your system information from Steam's Help menu:

https://steamcommunity.com/sharedfiles/filedetails/?id=390278662

[nstgc]

https://gist.github.com/nstgc/02457d7920931a3f8d69cc7b9fa41a2c

[notfood]

https://gist.github.com/notfood/4937609d291bf79316eb60cc818fde17#file-steam-system-information-txt

[FreeLikeGNU]

Hmm could it be lack of hyperthreading or something about realtek audio chips that DOS2 on WINE does not like? I've tried testing in Mint, Manjaro and Xubuntu (with xaudio2_7 and renamed exe's) with the same results. On the same hardware running Xubuntu and Manjaro I can run Witcher 3 and Skyrim SE just fine.

[notfood]

I don't see a way to enable it. I can play Witcher 3 and Skyrim.

[KGOrphanides]

It's not very likely to be a Realtek audio issue - I'm using an external USB audio device and appear to be having the same difficulties.

In my case, at least, my bet is firmly on some combination of (maybe) DotNet and (very likely) driver issues with my powerful-but-ancient Radeon 6990.

Steam info, and I've switched to the stock radeon driver to provide more representative results while submitting Proton test results: https://gist.github.com/KGOrphanides/c0fe99f0d9824a8ab434907637c07400

[sinnate]

https://gist.github.com/Elisto/b27246d9bfa63f4fbd110616cec1cb2d
same problem here black screen + mouse

[notfood]

D:OS2 updated to "Definite Edition" and can't run anymore.

[FreeLikeGNU]

The "bin" folder now contains the frontend. The steam/steamapps/common/Divinity Original Sin 2/ folder now contains "Classic" and "DefEd" folders each with their own set of executable. No luck getting the frontend working so far.

[Sethox]

I got the game to work without any add/winetricks/installation and even skipping the script installation from steam.

Since D:OS2 and D:OS2 Difinitive Edition is DRM free I can run the game without steam, thanks to this I could troubleshoot a little further.

I managed to set up a seperate WINEPREFIX for my own and use Wine 3.7 on it, the game just did not want to start, the black screen, I figure I had to install XACT. Out of curiosity I tried Wine-Staging 14 (cleaning my WINEPREFIX fully) I made it work without installing XACT, just like that, no problem playing the game. Even using Wine 3.14 had the same affect, no problems no extra installations. The problem was, it was without the steam-environment, as I can play the game it feels naked on the multiplayer side, I still want the steam version run like the steam version (how it's supposed to run).

So what I take from this is that I have wait until Valve update Proton to a newer Wine-base version.

Note: I used Lutris for this troubleshooting (Easier to force kill the WINEPREFIX when needed). I also may have LSI (Linux Steam Integration) on but it does not have any affect on this "experiment".

OS: Solus x86_64
Kernel: 4.17.17-87.current
Shell: bash 4.4.19
Resolution: 1920x1080
DE: Budgie
CPU: Intel i7-2600K (8) @ 3.800GHz
GPU: AMD ATI Radeon R9 290
Total Memory: 20040MiB

[FreeLikeGNU]

@Sethox maybe I'm getting a bit off topic here but here is output of my fresh wineprefix of wine-staging 3.14 with DXVK .70 (no xact) with Witcher3 (runs great) and D:OS2 DE (blackscreen). I really dont know what to make of this or the fact that DOS2 runs for some of us but not others. Maybe there is some other system configuration that is blocking this!?

https://gist.github.com/FreeLikeGNU/5d438df7aa8a6b8c851f768e4839722c

[FreeLikeGNU]

after testing a few machines using the same Xubuntu 18.04.1 nvidia 396.54, wine staging 3.14 and DXVK .70 I get:
Intel(R) Core(TM) i5-3470 CPU, GTX1070 - fail
Intel(R) Core(TM) i5-4590 CPU, GTX 680 - fail
Intel(R) Core(TM) i7-3630QM CPU, GTX 670MX - runs great
Intel(R) Core(TM) i7-2679QM CPU, GTX670 - runs great

all tested machines run The Witcher 3 in that same prefix fine (except for the minor known texture streaming issue)

[ksterker]

Have not been able to run D:OS2; been trying since it came out. Now I tried with Proton, but results in black screen just like with regular wine (or wine + DXVK).

Ubuntu 18.04
CPU: Intel(R) Core(TM) i5-4460 @ 3.20GHz (family: 0x6, model: 0x3c, stepping: 0x3)
GPU: GeForce GTX 950 driver 396.54
RAM: 8GB

Been running games like Witcher 3 or Kingdom Come: Deliverance just fine.

[lieff]

@FreeLikeGNU May be game tries to detect graphics settings on first run? What if copy generated settings from working system to non-working?

[Rotscha]

I'm one of those who never got the game to run with wine. Just like @FreeLikeGNU, the game would would segfault (and create a minidump) and than hang with the black screen.

So I debugged the game a while back, and I'm very sure, that the problem isn't gpu related at all.

What I found out:
On game start, during the initialization of the game's audio engine (Audiokinetic Wwise), a new thread is created. When this thread is executed first, it makes a call to some subroutine within the engine. However, unlike on Windows, on Wine the pointer to that subroutine contains an invalid memory address. The call to that address causes the thread to segfault. I assume the game hangs at this point because other threads are waiting for the thread forever to release locked semaphores.

As the crash happens before xaudio2_7.dll is even loaded, installing xact doesn't help in this case.

Sadly, I couldn't find a solution or workaround to get it running. I can only assume it's somewhat related to .NET, which Wwise is based on. Maybe in invalid vtable or something like that.

[FreeLikeGNU]

@Rotscha any idea why it might work on some machines and not others, like perhaps the audio chipset or driver?

EDIT: I disabled my onboard audio via bios, no effect.

[notfood]

Could it be that the people running it have simple 2.1 audio and D:OS2 is trying to do something fancy for 5.1/7.1 users?

[Sethox]

@notfood That is a possibility I did not think myself. Since it's about audio..

My test did involve a headphone so it's basically "2.1". For those that does not work for, what audio setup do you have?

[FreeLikeGNU]

@lieff that was my line of thinking when I used an external drive with xubuntu and the game installed in a known working configuration. This is a portable system I can use to test on lots of hardware quickly with game configuration saved. I built the installation with the non-working hardware tested again on that and then tested with working hardware (and those ran the game). I then ran the game on the non-working hardware again to verify (and hope maybe something changed the games configuration file to work) but results remained the same.

[ksterker]

I'm using a simple stereo setup, nothing fancy at all, hooked to line out of the mainboard. Can't get much simpler than that, but no dice.

[Sethox]

Reading things around and looking at the spreadsheet (https://docs.google.com/spreadsheets/d/1DcZZQ4HL_Ol969UbXJmFG8TzOHNnHoj8Q1f8DIFe8-8/htmlview?sle=true#gid=0)

I notice that some people compile their own proton version direct from source, that seems to work for most of the people. I cannot get it to work with steam's own version (beta or the other), only if I make my own WINEPREFIX with newer mainline wine version.

Edit: I just validated the game folder, and bam more than 30 files "failed to validate", so disregard my message.

[mantvius]

It seems Proton 8.0-1 breaks compatibility of the game as the launcher works but game doesn't start. I switched to Proton 7.0-6 and the game works out of the box now.

The same for me.

[KatyushaScarlet]

It seems Proton 8.0-1 breaks compatibility of the game as the launcher works but game doesn't start. I switched to Proton 7.0-6 and the game works out of the box now.

Same issue here, but the game is not working with Proton 7.0-6 on my Steam Deck.
It shows an alert box that says "Failed to create dir"
Here's my log: https://gist.github.com/KatyushaScarlet/03768a9a4055a16e92d630e9b1ba66b4

[kisak-valve]

Divinity: Original Sin 2

Issue transferred from #6883.
@VeilSilence posted on 2023-06-27T16:22:01:

Compatibility Report

Divinity:Original Sin 2 Definitive Edition.
Steam AppID of the game:435150

System Information

• GPU: Nvidia RTX 3090
• Driver/LLVM version: nvidia-open-dkms 535.54.03-3
• Kernel version: 6.3.9-zen1-1-zen
• Link to full system information report as Gist:
• Proton version:Proton 8.0.2, Proton Experimental, Proton 7.0.6

I confirm:

• [✓] that I haven't found an existing compatibility report for this game.
• [✓] that I have checked whether there are updates for my system available.

Symptoms

Greetings.
When i'm chosing in Divinity Launcher start "Definitive Edition" game crash after ~60% loading on start. If i chose "Classic" version however, game works properly.
Tried different proton version ( see proton version ) without any luck.

Reproduction

1:Launch the game
2:Choose in Launcher "Definitive Edition"
3:Crash of loading

steam-435150.log

[kisak-valve]

DOS 2 definitive edition doesn't start on steam deck

Issue transferred from #6997.
@sumilinux posted on 2023-08-06T13:37:09:

Compatibility Report

• Name of the game with compatibility issues: Divinity Original Sin 2 Definitive edition
• Steam AppID of the game: 435150

System Information

• GPU:
• Video driver version:
• Kernel version:
• Link to full system information report as Gist:
• Proton version: experimental/ 8.0-3

I confirm:

• [ ✓] that I haven't found an existing compatibility report for this game.
• [ ✓] that I have checked whether there are updates for my system available.

Symptoms

Game crashes on startup. I see a black screen and then the game exists.
Tried with different proton version like experimental,8.0-3 7.0-6. Crashes in both regular and desktop mode

Reproduction

[sumilinux]

After doing a reset of steam deck, the game is starting up with proton latest version without any other tweaks from user.

[friedc]

This game shows graphical artifacts when installed on a NTFS partition!

This problem does not happen on an ext4 partition.

[techmouse]

Replying to #413 (comment)

I feel like I'm missing a subtle joke but I'll just say this anyways in case you don't know.

Don't use NTFS. It's a proprietary closed source file system made and maintained by microsoft. "Broken on Linux" is not a bug. It's intentional. "Working perfectly on Linux" would be the bug.

Should a day ever come where the NTFS Linux drivers ever start working perfectly, microsoft will update NTFS again, to "fix" that Linux bug.

Anyways, sorry if I missed a joke.

[friedc]

Replying to #413 (comment)

No, this was definitely not meant as a joke even if it was funny to some. I just documented an issue that cost me a lot of time to debug. To explain my setup a bit more: I followed the wiki and put

UUID=BADF00D00BADF00D /media/gamedisk lowntfs-3g uid=1000,gid=1000,rw,user,exec,umask=000,allow_other,ignore_case,nofail 0 0

in my /etc/fstab. Without lowntfs-3g recent steam wouldn't even recognize the directory.

My use case for NTFS is that I want to be able to use big game directories from Windows without needing additional space and download time. It is interesting to me if something is a game bug or a proton bug. (Or even a mesa or Linux bug - those do happen.)

[techmouse]

My use case for NTFS is that I want to be able to use big game directories from Windows without needing additional space and download time.

Yeah I know. It's a very common pitfall. We all fall for it.

I hear there's an ext driver for windows, but I've never used it so I can't recommend it. I mean would you really want M$ to have control over your Linux drives anyways?

The best choice really is just to get another hard drive. Unless you want to go full time Linux. Sucks, but this is corporate sandbagging for ya. One tries to provide choices, the other tries to reduce them.

[ShalokShalom]

I hear there's an ext driver for windows, but I've never used it so I can't recommend it. I mean would you really want M$ to have control over your Linux drives anyways?

There are a couple ones, and you can set them to read only.
Another option is OpenZFS, that is supported by both.

Don't use NTFS. It's a proprietary closed source file system made and maintained by microsoft. "Broken on Linux" is not a bug. It's intentional. "Working perfectly on Linux" would be the bug.

Linux 5.15 onwards should have proper NTFS support in the new driver from Paragon.
https://docs.kernel.org/filesystems/ntfs3.html

[ShalokShalom]

Proton Experimental, 8, 7 and 6:

I click on "Play" and the game tries to launch, but ultimately fails and restores the text on the button back to "Play"

The game doesnt launch, no error message at all.

I am on NixOS.
My system
PROTON_LOG=1 %command% does not produce a log in my HOME directory.

Can I provide anything else?

[kisak-valve]

DOS2 sound broken

Issue transferred from #7409.
@sumilinux posted on 2024-01-14T21:19:33:

Compatibility Report

• Name of the game with compatibility issues: DOS2
• Steam AppID of the game:435150

System Information

• Steamdeck
• Kernel version:
• Link to full system information report as Gist:
• Proton version: 8.04 or experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Ever since the upgrade to latest proton, the sound for the game is not working.
Tried the following:

1. Restart deck
2. Downgrade and use older proton versions
3. Verify integrity of the game files
4. Reinstall the game.

None of the above restores the sound for the game.

Reproduction

[Lightsockie]

Started getting crashes today-ish, seems to be some change that was pushed in the Experimental Branch that caused it. Switched to using 8.0-5 and it loaded up again just fine. (My client defaults to using the Proton Experimental branch.)

Guessing it's something in the Proton 9.0 (Beta11) from 3days ago that is causing this.

Specifically I was getting a crash during the "Instantiate Level" step of the Script Extender mod (v59), during first game launch loading. Couldn't find anything in neither the script extender nor the game's logs to figure out why, but saw a comment in the steam discussions about how a recent proton change was giving them CTD, and switching a version back fixed it (so am confirming that). Also seen comments about how GeForce is causing problems right now, but I'm AMD (so anti-confirming that).

(Game has run perfectly fine besides this point, no issues at all even with mods. Just want to have this documented somewhere besides a throw-away steam discussions thread, so it's more easily found)

[kisak-valve]

Hello @Lightsockie, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

[Lightsockie]

Okay so I rewrote my launch commands to skip the launcher (SupportTool.exe) and launch the game directly (the --skip-launcher still launches the launcher). Doing this brought the log file size from about ~60Mb to ~1Mb (forced third-party launchers are such a cancer). For posterity, here's that quick lil hack:
echo "PROTON_LOG=1 WINEDLLOVERRIDES=\"DXGI.dll=n,b\" PROTON_NO_ESYNC=1 %command%" | sed 's\bin/SupportTool\DefEd/bin/EoCApp\' | sh

Here's the logs, tho looking in I dunno if there's a clear smoking gun. Attaching both 8 and 9, for comparison sake.
v8.0-5: https://files.catbox.moe/wz0xdq.log
v9.0 (Beta): https://files.catbox.moe/as445n.log
The crash itself seemed to happen around 1372853.534

Me:

CPU Brand: AMD Ryzen 9 7950X 16-Core Processor
"Artix Linux" (64 bit)
Kernel Version: 6.8.0-rc2-273-tkg-bore
Steam Runtime Version: steam-runtime_0.20231127.68515
X Server Release: 12101011
Driver: AMD AMD Radeon RX 7900 XT (radeonsi, navi31, LLVM 16.0.6, DRM 3.57, 6.8.0-rc2-273-tkg-bore)
Driver Version: 4.6 (Compatibility Profile) Mesa 24.0.1-arch1.1

[alasky17]

@Lightsockie We are trying to look into this, but I'm not familiar with the script extender specifically. I found https://github.com/Norbyte/ositools/releases but I don't see a v59 - it looks like the most recent is v3. Is this the one you are using or are you using a different one? Any extra tips on how to set this up so that we can attempt to reproduce locally would be greatly appreciated :)

[Lightsockie]

@alasky17 Yep that's the right one. I'm not sure why it says v5 there, it'll say v59 in-game. (tbh the whole thing is a little jank, even among these sorts-of frameworks imo.) I followed what that link ya posted, no caveats or gotchas -- should hopefully just be as easy as dropping that DXGI.dll (the only thing in that archive) where it says to, and setting the "native,builtin" override in wine for that DLL (which the launch options does easily enough).

The framework itself is horrendously documented, though, so if you want to get any useful info out of it I'll save ya the headhunt I wasted an afternoon on. If you create ./Divinity Original Sin 2/DefEd/bin/OsirisExtenderSettings.json and toss the following into it, you'll get it's console and logging enabled.

{
    "CreateConsole": true,
    "EnableLogging": true,
    "LogRuntime": true,
    "LogCompile": true,
    "LogFailedCompile": true,
    "DeveloperMode": true 
} 

Is the regression only happening for the case with the script extender? I just tried disabling it, but it still seems to be crashing without it. But tbf my environment isn't pristine, "Verifying Game Integrity" now to try and give a better test case without it.

EDIT:
Oh, I should've looked back before I posted. The Verify finished, but still getting the crash at about the same spot: https://files.catbox.moe/bzhjwk.png. With the script extender enabled, it'll call this "Instantiate Level".

EDIT2:
Oh, also I have these workshop mods enabled. I'm not sure how "loaded" these mods even are before the main menu (where you'd select which to use), but I'd think they wouldn't be relevant at the point we're CTDing at? Still, in the interest of giving ya all I know:
https://steamcommunity.com/sharedfiles/filedetails/?id=1506776884
https://steamcommunity.com/sharedfiles/filedetails/?id=1499447796
https://steamcommunity.com/sharedfiles/filedetails/?id=1503849808
https://steamcommunity.com/sharedfiles/filedetails/?id=1506230499
https://steamcommunity.com/sharedfiles/filedetails/?id=2943080327

[AJuujarvi]

@Lightsockie This should be working now with Proton Experimental on the Bleeding Edge Branch. Let me know if you have any additional problems. It was in fact unrelated to the mod, the issue was happening with the mod uninstalled.

[siborg]

for a while now the game stopped running past launcher. It fails every time with the below error:

I have tried multiple proton versions, recreating compat directory from scratch but the results are the same.

Setup:

CPU Brand: AMD Ryzen 9 5900X 12-Core Processor
RAM: 64219 Mb
Driver: NVIDIA Corporation Quadro RTX 5000/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 550.76

Arch Linux" (64 bit)
Kernel Version: 6.8.9

X Server Vendor: The X.Org Foundation
X Server Release: 12101013
X Window Manager: KWin

[Blisto91]

@siborg Hi there. Attach a Proton log if you can.
Running the game with PROTON_LOG=1 %command% in its launch options in Steam should make a file called steam-435150.log appear in your users home folder

[siborg]

@siborg Hi there. Attach a Proton log if you can. Running the game with PROTON_LOG=1 %command% in its launch options in Steam should make a file called steam-435150.log appear in your users home folder

Please see the attached.

steam-435150.log

[ell1e]

Crashes on latest proton experimental, doesn't crash (but gets stuck on black screen) when run outside of Steam with wine with taskset -c 0. Seems to be fundamental proton multithreading bug maybe? There are mentions in various places online that other users see such a multithreading bug with specifically this game and wine or proton too.

Sadly I can't run it with taskset -c 0 inside Steam due to it being seemingly impossible to figure out. taskset -c 0 %command% doesn't work, my guess is because it only applies to the launcher not to the game once that one is launched.

Edit: update: it almost always crashes no matter what, seems like the differences I saw were just random.

[ell1e]

I tried PROTON_LOG=1 %command% but it looks a little like it just covers the launcher and not the actual game. Is there a way to make it log for the game, too?

[Blisto91]

It should include everything launched through the play button in one big log. The starting point is just the launcher.

[ell1e]

steam-435150.log
I see! Then here's the crash log, or the quit log I guess (dmesg doesn't log a segfault but it's disappearing after 1 second of black fullscreen with game mouse cursor, so something isn't working right). I tried multiple older proton versions and proton experimental, none work. Fallout 4 runs fine on this machine with high settings, so it shouldn't be a general hardware issue.

Here's how it looks like:

bug-proton-divinity-original-sin-2-crash.webm

Update: this has been fixed now with a Proton update.

[ell1e]

None of Proton Experimental, Proton 9, Proton 8, Proton 7 work, by now I tested them all and it always looks like this. Is this the CPU detection issues? But it seemed from the previous comments like that was supposed to be fixed.

Update: this has been fixed now with a Proton update.