Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Divinity Original Sin 2 appid 435150 #413

Open
FreeLikeGNU opened this issue Aug 24, 2018 · 153 comments

Comments

@FreeLikeGNU
Copy link

commented Aug 24, 2018

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

This comment has been minimized.

Copy link

commented Aug 24, 2018

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

This comment has been minimized.

Copy link

commented Aug 25, 2018

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

This comment has been minimized.

Copy link
Author

commented Aug 25, 2018

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

This comment has been minimized.

Copy link
Author

commented Aug 25, 2018

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

This comment has been minimized.

Copy link

commented Aug 25, 2018

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

@FreeLikeGNU

This comment has been minimized.

Copy link
Author

commented Aug 25, 2018

@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

This comment has been minimized.

Copy link

commented Aug 25, 2018

Error logs are indeed a step forward!

@notfood

This comment has been minimized.

Copy link

commented Aug 26, 2018

I get the exact same error.

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

@FreeLikeGNU

This comment has been minimized.

Copy link
Author

commented Aug 28, 2018

@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

This comment has been minimized.

@FreeLikeGNU

This comment has been minimized.

Copy link
Author

commented Aug 28, 2018

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

This comment has been minimized.

Copy link

commented Aug 28, 2018

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

@KGOrphanides

This comment has been minimized.

Copy link

commented Aug 29, 2018

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

@Elisto

This comment has been minimized.

Copy link

commented Aug 30, 2018

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

@notfood

This comment has been minimized.

Copy link

commented Aug 31, 2018

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

@FreeLikeGNU

This comment has been minimized.

Copy link
Author

commented Aug 31, 2018

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

This comment has been minimized.

Copy link

commented Aug 31, 2018

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

This comment has been minimized.

Copy link
Author

commented Sep 1, 2018

@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

This comment has been minimized.

Copy link
Author

commented Sep 1, 2018

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

This comment has been minimized.

Copy link

commented Sep 2, 2018

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

This comment has been minimized.

Copy link

commented Sep 2, 2018

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

@Rotscha

This comment has been minimized.

Copy link

commented Sep 2, 2018

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

This comment has been minimized.

Copy link
Author

commented Sep 3, 2018

@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

This comment has been minimized.

Copy link

commented Sep 3, 2018

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

This comment has been minimized.

Copy link

commented Sep 3, 2018

@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

This comment has been minimized.

Copy link
Author

commented Sep 3, 2018

@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

This comment has been minimized.

Copy link

commented Sep 3, 2018

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

This comment has been minimized.

Copy link

commented Sep 3, 2018

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.

@Bamsey

This comment has been minimized.

Copy link

commented Apr 12, 2019

SaveGame works fine witch parameter PROTON_USE_WINED3D=1 %command% but generates some glitches like black heroes status icon or loading bar.

@Bamsey

This comment has been minimized.

Copy link

commented Apr 15, 2019

The problem is that the VRAM (2GB) is too small. The solution is to reduce the texture quality (medium).

@headlesscyborg

This comment has been minimized.

Copy link

commented Apr 29, 2019

I have the same issue like @Bamsey.
System info: https://gist.github.com/headlesscyborg/9519a667da049ef7885361b4e3674e3b
Video: https://youtu.be/HRMexHPGAmM

Lowering video quality helps but not always. I also have 2GB VRAM.

@HonkingGoose

This comment has been minimized.

Copy link

commented Apr 30, 2019

Seems Xaudio related:

16405.613:002a:003c:trace:module:get_load_order looking for L"C:\\windows\\system32\\XAudio2_7.dll"
16406.007:002a:0036:trace:module:load_dll looking for L"xaudio2_8.dll" in L"Z:\\media\\bams\\DANE\\SteamLibrary\\steamapps\\common\\Divinity Original Sin 2\\bin;C:\\Program Files (x86)\\Steam;C:\\windows\\system32;C:\\windows\\system;C:\\windows;.;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem"
@KGOrphanides

This comment has been minimized.

Copy link

commented May 10, 2019

Quick note: the game stopped working following an update, and failed to run.

I had previously got it running with a variant of @GloriousEggroll's method (see my last post).

I was able to return it to functionality by, in bin, removing my SupportTool.exe symlink and relinking with ln -s EoCApp.exe SupportTool.exe

@clapbr

This comment has been minimized.

Copy link

commented May 11, 2019

Quick note: the game stopped working following an update, and failed to run.

I had previously got it running with a variant of @GloriousEggroll's method (see my last post).

I was able to return it to functionality by, in bin, removing my SupportTool.exe symlink and relinking with ln -s EoCApp.exe SupportTool.exe

That's gonna happen with this workaround by design everytime steam updates the game or verify its checksums.

@jsimmons

This comment has been minimized.

Copy link

commented Jun 8, 2019

You don't actually have to link around the launcher. You can fix it by enabling .net in proton using winetricks using this script https://gitlab.com/quietkerb/steamplayprefix

./sppfx.sh 435150 winetricks -q dotnet472

Afterwards the launcher works normally.

@GloriousEggroll

This comment has been minimized.

Copy link
Contributor

commented Jun 16, 2019

I've noticed with the soft symlink, the first time you launch the game it still blackscreens, all times afterwards it runs fine.

Also dotnet472 sometimes causes issues with the prefix, giving rundll32 error spam, and sometimes does not always complete installation/takes a very long time.

@mysticfall

This comment has been minimized.

Copy link

commented Jun 27, 2019

I noticed that the game freezes frequently after the Steam update to Proton 4.2. It mostly ran without major issues but I'm not entirely certain if the update was actually the cause though.

@norg

This comment has been minimized.

Copy link

commented Jul 2, 2019

You don't actually have to link around the launcher. You can fix it by enabling .net in proton using winetricks using this script https://gitlab.com/quietkerb/steamplayprefix

./sppfx.sh 435150 winetricks -q dotnet472

Afterwards the launcher works normally.

I tried this but didn't help, the script ends with:

dotnet40 install completed, but installed file /home/$USER/.steam/steam/steamapps/compatdata/435150/pfx/dosdevices/c:/windows/Microsoft.NET/Framework/v4.0.30319/ngen.exe not found

and wants to install .net again

@headlesscyborg

This comment has been minimized.

Copy link

commented Jul 7, 2019

Is there any solution or an incoming fix for the FPS drop after saving the game? I'm stuck in the middle of the game, can't play it due to this bug because I save often which means restarting ~30-40 times per hour.
I bought it because people said "runs like native, no port needed" but this really makes me want to go back to full "no tux no bux".

@Bamsey

This comment has been minimized.

Copy link

commented Jul 7, 2019

So, in the middle of the game even lowering the quality of textures to low does not always help. An interesting fact is that playing without using DXVK (only WINED3D) FPS never drops after saving the game. Never. Something's wrong in memory alocated. DXVK author said it wasn't DXVK errors, but by WINED3D works fine. To bad that the wine and dxvk developers don't cooperate.

@headlesscyborg

This comment has been minimized.

Copy link

commented Jul 7, 2019

I can confirm what Bamsey said, this bug doesn't happen with PROTON_USE_WINED3D=1 %command% (WineD3D) but the performance is much worse (20 fps on low instead of 50-60 fps on high/ultra).
It really looks like a DXVK-specific bug, something similar (fps drop to 10-12 after changing graphic settings) happens in other games (for example The Evil Within, Hitman 2). For some reason the only DX11 game where I never saw sudden severe FPS drops on a 2GB VRAM card was Witcher 3.

@TheDaftRick

This comment has been minimized.

Copy link

commented Jul 8, 2019

So, in the middle of the game even lowering the quality of textures to low does not always help. An interesting fact is that playing without using DXVK (only WINED3D) FPS never drops after saving the game. Never. Something's wrong in memory alocated. DXVK author said it wasn't DXVK errors, but by WINED3D works fine. To bad that the wine and dxvk developers don't cooperate.

I don't believe this is a DXVK bug. DXVK just happens to max out your graphics card faster than regular WINED3D.
This FPS issue has been a Linux problem for many years.
ValveSoftware/csgo-osx-linux#185
ValveSoftware/csgo-osx-linux#1206

@mausworks

This comment has been minimized.

Copy link

commented Jul 9, 2019

Also dotnet472 sometimes causes issues with the prefix, giving rundll32 error spam, and sometimes does not always complete installation/takes a very long time.

@GloriousEggroll so. I tried this trick, and now the game won't launch.

After a while, wine console pops up a window which says:

The .NET Runtime Optimization Service is started and paused.
Microsoft (R) CLR Native Image Generator - Version 2.0.50727.3053
Copyright (c) Microsoft Corporation. All rights reserved

And then repeats it ad infinium.
Running xprops on said window reveals that it's indeed a wine console.

WM_CLASS(STRING) = "wineconsole.exe", "Wine"

But I've never seen it before.

Also, the installation is no longer progressing taking a very long time, but it's now just 1 step, instead of 4:

DeepinScreenshot_Steam_20190709231404

While taking the time to write this (maybe ~20 mins since launch), the installation actually ended (I'm not sure what made it end though). Then I got this message:

DeepinScreenshot_discord_20190709231607

I might have made a royal mistake somewhere. I'll investigate and see what I can find.

Any help is appreciated though. 😄


So I ran ./sppfx.sh 435150 winetricks dotnet472 again, but this time without the -q flag. Then I clicked myself through all the wizards (it will install .NET Framework 4.5 and onwards).

The last .NET Framework 4.7.2 install failed. So I closed the wizard, launched the game, and then voilá — insta-launch 🤷‍♀

@Endiverge

This comment has been minimized.

Copy link

commented Jul 10, 2019

You don't actually have to link around the launcher. You can fix it by enabling .net in proton using winetricks using this script https://gitlab.com/quietkerb/steamplayprefix

./sppfx.sh 435150 winetricks -q dotnet472

Afterwards the launcher works normally.

I tried this but didn't help, the script ends with:

dotnet40 install completed, but installed file /home/$USER/.steam/steam/steamapps/compatdata/435150/pfx/dosdevices/c:/windows/Microsoft.NET/Framework/v4.0.30319/ngen.exe not found

and wants to install .net again

In my own experimentation, I ran into this problem with recent versions of winetricks, but it worked with the winetricks package from the Ubuntu 19.04 repo.

@ThatGhost54

This comment has been minimized.

Copy link

commented Jul 15, 2019

@Endiverge I'm new to Linux in general (had to pick it up for a class and decided to experiment with Manjaro on this side) and I'm wondering what the move would be for someone not running Ubuntu if you know. Trying to run sppfx 435150 winetricks -q dotnet472 (and without the -q) both result in:

wine cmd.exe /c echo '%ProgramFiles%' returned empty string, error message ""

even though it ran the first time but game the dotnet40 install completed, but installed... message the first time.

@Endiverge

This comment has been minimized.

Copy link

commented Jul 15, 2019

@ThatGhost54 The version on Ubuntu 19.04 doesn't look different from version 20181203 on the winetricks github in any way that should matter. If you download an archive of the source, the winetricks script itself is the winetricks file in the src folder.
Put that file in your working directory, and preface your sppfx commands with WINETRICKS_COMMAND="./winetricks"

@ThatGhost54

This comment has been minimized.

Copy link

commented Jul 15, 2019

@Endiverge Thank you. It came up with: error: dotnet472 conflicts with dotnet40, which is already installed. You can run './winetricks --force dotnet472' to ignore this check and attempt installation
I ran it with --force instead of -q and it had me restart after installing some .net stuff. I did and now Divinity says running on steam when I hit play, but nothing actually shows up. I run ps in the terminal and there is no Divinity running. It stays running in my library and I've launched other games as well (sometimes this would happen in windows after exiting a game and launching another one would normally fix it) I'm when I try to run the winetricks command again becuase I feel like maybe I shouldn't have restarted to quickly, I get the same error as before, would it be worth it to just delete the game and any .net files and start from scratch again?

EDIT: I decided to put up a report on ProtonDB but I found out my graphics driver was the free one instead of the non-free one. I remember that I didnt use the non-free one because when installing Manjaro selecting that driver would keep the whole sytem from booting properly. Installed the Nvidia driver and I have entered the menu of the game! Going to play around for a few hours and see if any issues arise.

@foresto

This comment has been minimized.

Copy link

commented Aug 15, 2019

Based on this comment, it looks like we could tell Steam to stop re-running its .Net install script by creating the right registry key under HKEY_LOCAL_MACHINE/Software/Wow6432Node/Valve/Steam/Apps/CommonRedist/.NET. Is there some way to find out exactly which registry key is missing?

@foresto

This comment has been minimized.

Copy link

commented Aug 16, 2019

Sharing workarounds:

The rename+symlink trick worked for me, but I wanted to avoid depending on that, mainly so I wouldn't have to do it again whenever the game gets an update. So:

I used winetricks version 20181203 to install dotnet472. I did not use the --force or -q options. It ran several .NET installers with increasing version numbers. Whenever they prompted me to reboot now or later, I chose now, knowing that Wine would not actually reboot my computer.

At two points during the process, I noticed one CPU core stuck at 100% while no progress appeared in the terminal window. I let the first one run for an hour, decided it was stuck, and killed the responsible process: pkill ngen.exe. When it happened again later, I checked the process' full command line, which turned out to be something like "ngen.exe uninstall System" followed by some additional options. Manually running "ngen display System" revealed that no assembly by that name was installed, so I figured it was safe to kill ngen once again. After this, the .NET installation continued and eventually finished.

I then removed my symlinks and reverted the directory and file names from the earlier workaround, started Steam, and launched the game. Steam still insisted on repeating the first time setup (Installing Microsoft .NET Framework), but the Larian Launcher appeared after that, and I was able to start the game from there. Progress!

Strangely, Steam sometimes thinks the game is still running long after I have quit, preventing Steam from exiting cleanly. The game process has actually exited, but this process stays around keeping the Wine instance alive: mscorsvw.exe -StartupEvent c4 -InterruptEvent b4 -NGENProcess b8 -Pipe c0 -Comment NGen Worker Process Looks like another ngen-related hang.

All this was with Proton 4.11-2.

A few questions remain in my mind:

  • Do any newer versions of winetricks work for installing dotnet472?
  • What is ngen.exe trying to do, and why does it never finish?
  • Is mscorsvw.exe trying to do the same thing? Is there some way to prevent it from sticking around in the background after I finish playing the game?
  • Did manually killing those ngen processes leave something in a broken state that will bite me later?
  • Why does the Larian Launcher max out my CPU even when it's basically a glorified menu with nothing much to do except wait for me to make a choice? Does it do this on Windows? Could it be activating a .NET background service that tries to do the same work that ngen was attempting?
  • The first time I started the game from the launcher, a black window appeared with nothing visible except an "I agree" button and a "no thanks" button. What was it trying to ask me?
  • How can we convince Steam not to run its first time setup every time we launch the game? Solution found. See my next comment.
@foresto

This comment has been minimized.

Copy link

commented Aug 26, 2019

Solution for Steam "Installing Microsoft .NET Framework" every time it launches the game, despite the framework already being installed: A single value is missing from the registry.

Here's a .reg file that will create the missing value when imported using regedit:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\Software\Wow6432Node\Valve\Steam\Apps\CommonRedist\.NET\3.5]
"3.5 SP1"=dword:00000001

Here's a command line that will do the same, assuming your WINEPREFIX environment variable and wine executable are set correctly:

wine reg add "HKLM\Software\Wow6432Node\Valve\Steam\Apps\CommonRedist\.NET\3.5" /v "3.5 SP1" /t REG_DWORD /d 1 /f
@GloriousEggroll

This comment has been minimized.

Copy link
Contributor

commented Aug 27, 2019

My proton build runs 'protonfixes' which auto applies the symlink rename trick if it's detected that it hasnt been done when the game is run. no user intervention required and no mucking with files if there's an update.

@zeeshan595

This comment has been minimized.

Copy link

commented Sep 1, 2019

@GloriousEggroll Tried it with your proton version and works perfectly for me. Plus all of the mods are working as well. Nice one!

@Bamsey

This comment has been minimized.

Copy link

commented Sep 24, 2019

After the last update (4.11-6) , game not start.

LOG:
[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.

File name: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
134308.524:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\windows\system32\winebus.sys" : builtin
134308.524:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\windows\system32\setupapi.dll" : builtin
pid 14972 != 14971, skipping destruction (fork without exec?)

@foresto

This comment has been minimized.

Copy link

commented Sep 24, 2019

@Bamsey, I'm also using Proton 4.11-6, and not experiencing that problem. Did you use the symlink/rename trick when you installed? I did not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.