search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.88k stars 1.04k forks source link

Elite Dangerous (359320) #150

Open KewaiiGamer opened 6 years ago

KewaiiGamer commented 6 years ago

I've just tried starting Elite Dangerous and it seems to not even display the game at all. It just starts and 1 second later it shuts down

I don't know how would I debug it so I would be glad if someone could instruct me on how to enable verbose for Proton Games

OS: Ubuntu 18.04 CPU: AMD Ryzen 5 1600X GPU: Nvidia GeForce 1050 Ti 3GB Driver Version: Nvidia Driver 396

redmcg commented 5 years ago

@kaiarne Did you ever get your Thrustmaster Hotas X working correctly? Another user has the same device and has raised an issue. I've made some suggestions there - but your issue sounds a bit like the one users were having with their Logitech Extreme 3D Pro. So you might also want to try the steps that seems to work for that.

fls2018 commented 5 years ago

@kaiarne Did you ever get your Thrustmaster Hotas X working correctly? Another user has the same device and has raised an issue. I've made some suggestions there - but your issue sounds a bit like the one users were having with their Logitech Extreme 3D Pro. So you might also want to try the steps that seems to work for that.

I have a Hotas X and it works fine, although I needed to delete the .binds in the control schemes folder (to avoid conflicts) and start with remapping from a blank preset.

redmcg commented 5 years ago

Proton 3.16-8 Beta ED has been released. It merges the changes made in Proton 3.16-8 Beta and includes a fix so vcrun2015 is no longer required.

I thought I would update that all patches used in this build are now in wine-devel 4.4 (except for the hack to allow vcrun2015 to install - but that is no longer required). So for those looking forward to an official Proton release with ED support, then any version based on 4.4 or later will only need dotnet40 installed.

fls2018 commented 5 years ago

Thanks to recent wine fixes as of Proton 4.2 the game is working with just a .Net install, strangely I didn't even need to change the wine path to wine64 so I assume that's fixed.

I don't know what tweaks it's missing from RedMcG's custom version but on my end it runs pretty well.

The unofficial Proton-TKG also works well (but needs the wine path changing to fix CRC error).

redmcg commented 5 years ago

Yes! That's very good news. I've updated the wiki with instructions on how to get ED going with 4.2 (using winetricks).

I found that manually installing vcrun2015 is still required. The patch that makes vcrun2015 unnecessary was only added to 4.4.

I too was surprised that wine64 wasn't required - but I found that it's because Proton now launches a steam.exe which makes a CreateProcessW call to launch the game. CreateProcessW was fixed with this patch (which fortunately only just made it in to 4.2).

Thulium-Drake commented 5 years ago

Hi folks,

It doesn't seem to fix all issues, when I try running it (even with the 3.16 patched version you made @redmcg). Let me start with my system as snipped from Steam:

Operating System Version:
    Debian GNU/Linux 9.8 (stretch) (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.19.0-0.bpo.2-amd64
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11902000
    X Window Manager:  Xfwm4
    Steam Runtime Version:  jenkins-steam-runtime-beta-release_0.20190320.2
Video Card:
    Driver:  NVIDIA Corporation GeForce GT 1030/PCIe/SSE2
    Driver Version:  4.6.0 NVIDIA 390.87
    OpenGL Version: 4.6

I have installed steam with the package from the repo and I'm running the following stuff from backports:

When I try running the game, nothing happens. When I run the following commands in my terminal:

WINEPREFIX=/games/steam/steamapps//compatdata/359320/pfx
WINEPREFIX=$WINEPREFIX /games/steam/steamapps/common/Proton\ 4.2/dist/bin/wine64 /games/steam/steamapps/common/Elite\ Dangerous/EDLaunch.exe /novr /steam

I get the following output:

wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
000b:err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
0021:err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory
0021:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\WineBus": c0000142
0014:err:service:process_send_command service protocol error - failed to write pipe!
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 1114
wine: configuration in '/games/steam/steamapps//compatdata/359320/pfx' has been updated.
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections" in state 2
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"sectionGroup" in state 6
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"section" in state 6
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"enforceFIPSPolicy" in state 4
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"userSettings" in state 2
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"CobraBay.Properties.Settings" in state 6
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>

Do you have any clue what is missing from my setup?

Thanks!

sizeofbool commented 5 years ago

I have installed steam with the package from the repo and I'm running the following stuff from backports:

* kernel (4.19)

* nvidia-driver (390)

Minimal requirements for Proton with dxvk is nvidia-driver 415 or later. https://github.com/doitsujin/dxvk/wiki/Driver-support You can try and run it with 410 which is available in stretch-backports suite. ED runs on my Debian stretch system with GTX1060 6G and nvidia-driver version 410.104

When I try running the game, nothing happens. When I run the following commands in my terminal:

WINEPREFIX=/games/steam/steamapps//compatdata/359320/pfx
WINEPREFIX=$WINEPREFIX /games/steam/steamapps/common/Proton\ 4.2/dist/bin/wine64 /games/steam/steamapps/common/Elite\ Dangerous/EDLaunch.exe /novr /steam

After you've selected compatibility tool in properties of the game and set it to "Proton 3.16-8 Beta ED", restart steam client and run ED from Steam Client as any normal game. You should get at least to a launcher and will be able to sign-in into ED account and launch the game.

Thulium-Drake commented 5 years ago

@sizeofbool You sir, are a hero! Thanks for the tip, I've got it running on my system! Thanks! :-)

Another step closer to putting Windows in the ditch where it belongs... ;-)

shadywack commented 5 years ago

I've run into one problem, and I'm assuming I did something wrong. I can't find the Elite player journal anywhere. I looked in the compatdata/359320/pfx directory for Steam and I can find the "Saved Games" directory, but where there should be "Frontier Developments/Elite Dangerous/" the Saved Games directory is empty. It doesn't appear that E:D is even saving a captain's log anywhere, as when I plot a course in the Galmap and exit the game, I have to replot the whole course as opposed to just accessing galmap and having it replot automatically.

redmcg commented 5 years ago

I think this was just asked and answered over on the Frontier Forums: https://forums.frontier.co.uk/threads/how-to-install-ed-on-linux-using-wine-experimental-not-officially-supported.366894/post-7715541

shadywack commented 5 years ago

I think this was just asked and answered over on the Frontier Forums: https://forums.frontier.co.uk/threads/how-to-install-ed-on-linux-using-wine-experimental-not-officially-supported.366894/post-7715541

Thank you for pointing that out!

If anyone else is googling for this, the solution in the forum post is to create the "drive_c/users/steamuser/Saved Games/Frontier Developments/Elite Dangerous" folder in your prefix folder.

EdwinHoksberg commented 5 years ago

Hi guys, thanks for this thread. It helped me setting up the game to the point where the launcher appears, but then it seems to bug out. If I launch the game in the terminal, the launcher is a weird black and white box(see screenshot below), and the terminal is just a endless loop(I waited for at least 10 minutes) of the same messages:

Log snippet

``` 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7858, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7880, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d78a8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d78d0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d78f8, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7920, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7948, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7970, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7998, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d79c0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d79e8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7a10, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7a38, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7a60, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7a88, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7ab0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7ad8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7b00, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7b28, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7b50, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7b78, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7ba0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7bc8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7bf0, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7c18, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7c40, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7c68, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7c90, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7cb8, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7ce0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7d08, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7d30, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7d58, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7d80, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7da8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7dd0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7df8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7e20, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7e48, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7e70, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7e98, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7ec0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7ee8, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7f10, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7f38, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7f60, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7f88, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7fb0, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d7fd8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8000, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8028, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8050, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8078, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d80a0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d80c8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d80f0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8118, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8140, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8168, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8190, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d81b8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d81e0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d8208, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5a30, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5a58, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5a80, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5aa8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5ad0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5af8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5b20, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5b48, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5b70, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5b98, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5bc0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5be8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5c10, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5c38, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5c60, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5c88, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5cb0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5cd8, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5d00, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f7e0,0x00000000), stub! 0037:fixme:win:EnumDisplayDevicesW ((null),1,0x2418f7e0,0x00000000), stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5d28, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5d50, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5d78, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5da0, (nil)) stub! 0037:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x551d5dc8, (nil)) stub! 0037:fixme:win:EnumDisplayDevicesW ((null),0,0x2418f560,0x00000000), stub! ```

It seems like it's stuck because I have multiple monitors, but when I turn off a monitor the same error occurs. Can anyone help me with this problem?

This is the command I run to start ED:

WINEPREFIX=~/.steam/steam/steamapps/compatdata/359320/pfx wine64 ~/.steam/steam/steamapps/common/Elite\ Dangerous/EDLaunch.exe /steam /novr

Operating System Version:
    Debian GNU/Linux buster/sid (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.19.0-4-amd64
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12004000
    X Window Manager:  i3
    Steam Runtime Version:  jenkins-steam-runtime-beta-release_0.20190320.2

Video Card:
    Driver:  X.Org AMD Radeon R9 200 Series (HAWAII, DRM 3.27.0, 4.19.0-4-amd64, LLVM 7.0.1)
    Driver Version:  4.5 (Compatibility Profile) Mesa 18.3.4
    OpenGL Version: 4.5

2019-04-04_20:58:36

redmcg commented 5 years ago

Running ED via:

WINEPREFIX=~/.steam/steam/steamapps/compatdata/359320/pfx wine64 ~/.steam/steam/steamapps/common/Elite\ Dangerous/EDLaunch.exe /steam /novr

will launch it via the wine version you have installed (not via Proton). To launch via Proton, just press 'Play' on your steam client.

Can you please verify the versions of wine and winetricks you have installed by running:

wine64 --version
winetricks --version

Also check out the DXVK driver recommendations and run vulkaninfo and make sure it doesn't return any errors.

I'm not using AMD or multi-monitor - but hopefully someone using one or both can comment on their experience.

EdwinHoksberg commented 5 years ago

@redmcg Thank you for your response. I must've done something wrong because I didn't change anything but it's working perfectly now :)

ebbit1q commented 5 years ago

I've been trying to get this to work for a while now. So far I'm stuck on launching the game itself, after logging into the launcher.

I've tried both using proton 4.2 and 3.16-8 Beta ED. I've also tried multiple nvidia driver versions to no avail.

After clicking play in the elite dangerous launcher the game will open a black window, then promptly close and open the crash reporter (picture) image

I am running Ubuntu 18.04.2 with: Kernel: 4.15.0-47-generic CPU: AMD Ryzen 7 1700X GPU: NVIDIA GeForce GTX 1080 Graphics driver: nvidia 410.104 (also tried 418) Wine: 4.0 stable (also tried 4.5 staging) Winetricks: 20190310-next

I have followed the instructions on redmcg wine's wiki: https://github.com/redmcg/wine/wiki I have tried both the 4.2 instructions and the custom build. I have tried some of the proton flags like no esync as well.

Have a debug log: [log] (44 MB, been having issues getting a paste site to just take it)

redmcg commented 5 years ago

@ebbit1q The usual cause of an early crash in the client is Vulkan related. Looking in your logs - I don't see DXVK initialising - so I'd say this is your problem.

You can quickly test Vulkan is working by running vulkaninfo. If you see an error like VK_ERROR_INITIALIZATION_FAILED - then Vulkan isn't working.

To use nvidia 4.10 you need X.Org X Server version 1.20.1 or higher. With 18.04.2 - this means upgrading the X HWE via: sudo apt install linux-generic-hwe-18.04 xserver-xorg-hwe-18.04

You can find more info here: https://github.com/redmcg/wine/wiki/NVidia#ubuntu

I couldn't find a stacktrace to find the exact cause - so if this isn't it - then you might want to provide the MiniDump. In you logs I can see one was created here: "C:\\users\\steamuser\\Local Settings\\Application Data\\Temp\\Frontier Developments\\EliteDangerous\\CrashDumps\\20190414_193942_MiniDump.dmp.detailed"

ebbit1q commented 5 years ago

vulkaninfo returns a whole bunch of output but no errors. I can run other games with vulkan just fine.

I followed your advice and I am now running X Server version 1.20.1 instead of 1.19, but I still have the exact same issue.

Now when digging through these minidumps myself I noticed it complaining about something:

>>>>>>>> Can't find input device mapping. Device details:
>>>>>>>>     Device name: ckb1: CORSAIR M65 RGB ELITE Gaming Mouse vKB

Simply unplugging my corsair mouse and using an old one instead allowed me to start the game and everything just fine! Even the vr version seems to be in working order.

I'm not sure if this is an issue with ckb next or with the mouse itself. Plugging the mouse back in causes the game to hang, requiring me to kill it manually. I might try if uninstalling ckb next fixes the issue. (update: it doesn't hang when I try to replug it now)

Thanks for the advice, if you want I can still give you the crashdump to see why the mouse would cause this.

redmcg commented 5 years ago

Great to hear you got it going. I must admit - I didn't predict that to be the problem.

Re: crashdump - without access to the map file(s) produced by the build, I can only get a real high level view from the mini-dump. So I suspect we wouldn't learn any more than we already know (although I'm happy to take a quick look if you do put it up somewhere).

redmcg commented 5 years ago

@madewokherd Thanks for your work on wine-mono. It's good to see it now in Proton.

I'm wondering what the plan is for WPF? I see it's being made open source with .NET Core - but they're only targeting the Windows platform. Is the plan to port this (when it's finally compiling) to wine-mono? I assume the mono project won't pick it up (given it targets just the Windows platform).

madewokherd commented 5 years ago

Yes, we're expecting to be able to port it. More information here: https://bugs.winehq.org/show_bug.cgi?id=24501#c16

redmcg commented 5 years ago

Excellent - thanks for the link

kisak-valve commented 5 years ago

Elite Dangerous on Vega 56 has shader problems

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2701. @Byter09 posted on 2019-05-17T14:32:29:

Compatibility Report

System Information

I confirm:

steam-359320.log

Symptoms

Reproduction

Create a new prefix with:

export WINEPREFIX=~/SteamLibrary/steamapps/compatdata/359320/pfx
rm -rf $WINEPREFIX
winetricks -q dotnet40 vcrun2015 win7 dxvk

The reason for this can be found here: https://github.com/redmcg/wine/wiki#the-official-build-of-proton-42-runs-ed

After that start Elite Dangerous with VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" PROTON_NO_ESYNC=1 %command% The VK_ICD part is supposedly workaround to use radv instead of amdvlk as reported here to prevent exactly the problem I'm facing. It does not matter though, even without any modified launch options the same problem occurs.

I believe, that the VK_ICD_FILENAMES variable is not being passed to the Elite Dangerous process itself from the launcher. I already used it in X4: Foundations and that worked great.

kisak-valve commented 5 years ago

Hello @Byter09, amd_icd64.json doesn't sounds like a mesa/radv icd. I think you're explicitly asking for amdvlk which as you've noted has a driver issue. I'd expect radv's icd to be something like radeon_icd.i686.json or radeon_icd.x86_64.json.

The video driver issue should also be mentioned to the video driver vendor if it hasn't been already.

Byter09 commented 5 years ago

@kisak-valve Oh I'm sorry I posted this as a new issue. Also, I used amd_icd64.json in X4: Foundations which worked fine. I'll try radeon_icd.x86_64.json. I'll edit this comment after testing.

EDIT: YES. It worked. Thank you SO much. I have no idea though why the amd file worked in X4... weird.

Also, why are no issues allowed for the same game if the title of this issue is not even close to what I'm experiencing? Whatever the case, see you in the void commanders!

HadetTheUndying commented 5 years ago

I can confirm this issue only exists when using the amdvlk driver, if you use radv the game renders and performs as intended.

FurretUber commented 5 years ago

With Proton 4.2-5, Elite Dangerous is working on Intel HD Graphics 520! :tada:

The first game loading is still very dramatic, taking very long to load: took 2 hours the first time ever, without the shader pre-caching, with the pre-cache it takes around 20 minutes only. The window saying the application crashed appears, but ignoring that window makes the shader loading finish. After it finishes, the game must be closed because of the crash window. Opening it again the game works.

As DXVK tries to allocate large amounts of video memory (up to 4,3 GB) the game may crash due to heavy swapping on my system after playing for some time. As my system has only 8 GB of memory, I set a DXVK configuration file with the following:

dxgi.maxDeviceMemory = 1536
dxgi.maxSharedMemory = 128
d3d11.maxFeatureLevel = 11_1

Fortunately Elite Dangeours respects that values (unlike most other games) and while the amount of allocated memory is 2,8 GB, the amount used is 1,9 GB. There are some notorious graphical glitches using that configuration file close to large stations, as if the textures disappeared for a brief moment. I would say this bug is somehow affecting Elite Dangerous too.

Another notorious graphical bug is that the photos of the characters don't finish loading and are always pixelated. Not a terrible bug, but it exists.

image

Oliver-1xok commented 5 years ago

First it worked very well for me. I followed these instructions:

https://github.com/redmcg/wine/wiki

That worked like I said. I could play Elite with good performance. But since today I only get the following error message when I try to start Elite: " Server Unavailable - Failed to Synchronise Time with Server". Complete message window:

TimeServerError

Nothing helps. Not even a complete reinstallation. I found this: https://appuals.com/fix-elite-dangerous-failed-to-synchronize-time-with-server/ But the proposed solutions do not help either.

Does anyone have that problem too?

My System:

``` Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz CPU Family: 0x6 CPU Model: 0x5e CPU Stepping: 0x3 CPU Type: 0x0 Speed: 4200 Mhz 8 logical processors 4 physical processors HyperThreading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 18.04.2 LTS (64 bit) Kernel Name: Linux Kernel Version: 4.18.0-25-generic X Server Vendor: The X.Org Foundation X Server Release: 11906000 X Window Manager: Xfwm4 Steam Runtime Version: steam-runtime_0.20190626.0 Video Card: Driver: NVIDIA Corporation GeForce GTX 970/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 430.26 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 59 Hz VendorID: 0x10de DeviceID: 0x13c2 Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1200 Desktop Resolution: 3840 x 1200 Primary Display Size: 20.43" x 12.76" (24.06" diag) 51.9cm x 32.4cm (61.1cm diag) Primary Bus: PCI Express 16x Primary VRAM: 4096 MB Supported MSAA Modes: 2x 4x 8x 16x Sound card: Audio device: Realtek ALC1150 Memory: RAM: 15979 Mb Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 1877664 Mb Largest Free Hard Disk Block: 401850 Mb VR Headset: None detected Recent Failure Reports: ```

zezic commented 5 years ago

@Oliver-1xok have you tried the VPN? I'm not sure about this case, but for me there was a similar problem because of my ISP or something else (network related) and VPN helped me to connect.

Oliver-1xok commented 5 years ago

@Oliver-1xok have you tried the VPN? I'm not sure about this case, but for me there was a similar problem because of my ISP or something else (network related) and VPN helped me to connect.

You're close. It just seems to be a problem with IPv6 on Frontier's side. If I disable IPv6, the launcher will work again and the game will start correctly. See: https://steamcommunity.com/app/359320/discussions/0/1642042464738387811/#c1642042464739749875

So it's very likely not a proton problem.

sjnewbury commented 5 years ago

Elite Dangerous on Vega 56 has shader problems

Issue transferred from #2701. @Byter09 posted on 2019-05-17T14:32:29:

Compatibility Report

* Name of the game with compatibility issues: Elite Dangerous

* Steam AppID of the game: 359320

System Information

* GPU: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3)

* Driver/LLVM version: Mesa 19.0.4-1 / amdgpu

* Kernel version: 5.0.15-1-MANJARO

* [full system information report](https://gist.github.com/Byter09/fc8f00ede19a42d32f67963a09b55c6b)

* Proton version: 4.2-4

I confirm:

* [x]  that I haven't found an existing compatibility report for this game.

* [x]  that I have checked whether there are updates for my system available.

steam-359320.log

Symptoms

* when in game, the lighting is way to bright
  ![ed](https://user-images.githubusercontent.com/16060697/57934746-a5123a80-78c0-11e9-83b0-a1404a6408c8.png)

Reproduction

Create a new prefix with:

export WINEPREFIX=~/SteamLibrary/steamapps/compatdata/359320/pfx
rm -rf $WINEPREFIX
winetricks -q dotnet40 vcrun2015 win7 dxvk

The reason for this can be found here: https://github.com/redmcg/wine/wiki#the-official-build-of-proton-42-runs-ed

After that start Elite Dangerous with VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" PROTON_NO_ESYNC=1 %command% The VK_ICD part is supposedly workaround to use radv instead of amdvlk as reported here to prevent exactly the problem I'm facing. It does not matter though, even without any modified launch options the same problem occurs.

I believe, that the VK_ICD_FILENAMES variable is not being passed to the Elite Dangerous process itself from the launcher. I already used it in X4: Foundations and that worked great.

With latest git RADV both ACO and LLVM backends also fail with the perhaps the same shader, but instead of being really bright, the colours appear inverted by the shader. I get the same output as the screenshot above and machine hangs with amdgpu-pro.

Update: I had to go back to Mesa18 to get this to work properly. Mesa19.1.x at least also shows the same problem. Going to try 19.0.x... (This is with a POLARIS10)

Update2: Confirmed 19.0.x also demonstrates the bug. I'm using Gentoo, and the Mesa ebuilds use by default llvm7 for Mesa18, and 8/9 for 19.x. I'm going to see if I can build a 19.x mesa with llvm7...

Update3: llvm7+Mesa19.0.8 shows the defective shader. I'm going to try to find the last release that works then bisect to find when/where it broke.

prikhi commented 5 years ago

Running the lastest Steam + Proton on Arch Linux.

I was getting the mscoree.dll error when starting ED:

err:module:fixup_imports_ilonly mscoree.dll not found, IL-only binary L"EDLaunch.exe" cannot be loaded

I tried running protontricks 359320 dotnet40 but it was telling me it was already installed. I tried completely removing the prefix & relaunching ED but the error was still occurring and I again got the message that dotnet40 was already installed.

The solution is to first uninstall the mono-support from the prefix, then run the dotnet40 installer:

export WINEARCH=win64 WINEESYNC=1 \
    WINEPREFIX=/home/$(whoami)/.steam/steam/SteamApps/compatdata/359320/pfx
cd ~/.steam/steam/SteamApps/common/Proton\ 4.2/dist/bin
wine64 uninstaller  # Uninstall the mono package from the window that pops up
protontricks 359320 dotnet40

That let me run the launcher and the game :heart:

madewokherd commented 5 years ago

That sounds like a winetricks bug, but I'd expect this sort of bug to affect anyone using winetricks to install .NET. Maybe you have an old version of winetricks?

prikhi commented 5 years ago

Maybe you have an old version of winetricks?

It's pretty recent, I'm on Arch & updated a couple days ago:

$ pacman -Qs winetricks
local/protontricks 1.2.2-1
    A simple wrapper that does winetricks things for Proton enabled games.
local/winetricks 20190615-1
    Script to install various redistributable runtime libraries in Wine.

Although I didn't try directly using winetricks instead of protontricks.

sjnewbury commented 5 years ago

Update3: llvm7+Mesa19.0.8 shows the defective shader. I'm going to try to find the last release that works then bisect to find when/where it broke.

3b3081479163475f25b908008250d83c31716c34 nir/algebraic: Optimize 1-bit Booleans

It's the conversion to 1-bit Booleans in NIR. The following commit optimizes the D3D case, but obviously something has been missed. I've left a comment on the commit in the mesa Gitlab repo.

kisak-valve commented 5 years ago

Hello @sjnewbury, that sounds like an irregular method of feedback. Perhaps using their bug tracker would be easier for them (https://www.mesa3d.org/bugs.html).

FurretUber commented 5 years ago

Using Mesa git today, the very bright environment happens with Intel HD Graphics 520 too.

ed_bright

When I tested with Mesa git (the comment I did previously) it was still OK. However, now I am using 19.0.2 with a patch (specified using the custom launch command) and I stopped following Mesa git for this particular game because of the shader loading.

How long do you have to wait for the shaders loading? Here the shader loading takes at least 30 minutes now, which greatly discourages doing bisects for Elite Dangerous, as bisecting a regression can easily take 7 hours.

If you report a new bug, could you send the link here?

Cyclic3 commented 5 years ago

I am using a vega 56, and I do not get this graphical bug. However, I do have some memory of this happening a while ago. I run the latest mesa drivers (debian/sid, with bits from xorg-edgers, and with the AMD staging kernel)

The only way I can get it to work is by installing in a 3.16 prefix, and then (optionally) upgrading to a 4.9. See if that works for you.

FurretUber commented 5 years ago

I'm not sure if I should be worried, but I did the bisect for Intel anyway. The bisect gave a different result here, it was:

[65df6122da9d171bc44f9ca969825478543b5384] intel/compiler: Use compare rematerialization pass

I reported the bug at Freedesktop Bugzilla.

Edit: the bug was fixed and the character photos are loading correctly now.

FurretUber commented 5 years ago

After playing for long enough and docking on some different stations, the game may crash with a message it failed to lock a buffer.

When the computer had 8 GB of memory that was understandable, as it barely had enough to run the game alone. Now the computer has 20 GB of memory and this crash takes a bit longer, but still is happening. When it crashes it opens the following window:

ed

steam-359320.log.gz EliteDangerous64_d3d11.log EliteDangerous64_dxgi.log

The log files get pretty interesting, the log fileEliteDangerous64_d3d11.log has the following:

err:   DxvkMemoryAllocator: Memory allocation failed
  Size:      1000960
  Alignment: 16
  Mem flags: 0x1
  Mem types: 0x2
err:   DxvkMemoryAllocator: Memory allocation failed

In the moment of the crash, intel-gpu-overlay was showing 3868 MB of memory used by Elite Dangerous and htop was showing the system had 10 GB of total memory used while having nearly 10 GB free. Here are the new system specifications.

There is one workaround for this, that is setting a DXVK configuration file with the following:

dxgi.maxDeviceMemory = 128
dxgi.maxSharedMemory = 1536
d3d11.maxFeatureLevel = 11_1

There should be more than enough free memory to allocate, but this workaround is still required. :frowning_face:

sir-ragna commented 5 years ago

I seem to have a variation on the brightness bug albeit with a bit more colors in the main menu.

System Info

OS: Manjaro Linux x86_64 
Host: Z87X-D3H 
Kernel: 5.2.1-1-MANJARO 
DE: Xfce 
CPU: Intel i5-4590 (4) @ 3.700GHz 
GPU: Intel HD Graphics 
GPU: AMD ATI Radeon R9 290X/390X 
Memory: 4695MiB / 7865MiB

The output of glxinfo | grep -i opengl

OpenGL vendor string: X.Org
OpenGL renderer string: AMD HAWAII (DRM 2.50.0, 5.2.1-1-MANJARO, LLVM 8.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.2
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Screenshots

The main menu has a bit more color. image When starting the second tutorial. image

Set up

I followed instructions from https://github.com/redmcg/wine/wiki to get it running. Here are the exact commands I ran. I'm using proton 4.2-9.

STEAMAPPS=/mnt/datadrive/SteamLibrary/steamapps
export WINEPREFIX=$STEAMAPPS/compatdata/359320/pfx
mv $WINEPREFIX $WINEPREFIX.backup
winetricks -q dotnet40 win7

This is how I start steam to get into ED.

export PROTON_USE_WINED3D=1
export PROTON_NO_ESYNC=1
/usr/bin/steam %U
FurretUber commented 5 years ago

Today, the bug that made Elite Dangerous: Horizons crash while loading shader on Intel HD Graphics was fixed. Here is the bug report, now RESOLVED FIXED.

I tested the initial patch and the final, merged version. Both were able to load shaders successfully and I was able to land in planets.

Here is a video with me landing in a planet for the first time:

https://www.youtube.com/watch?v=aBGA5gVZVTw

The remaining Linux-only bug I can notice is the blinking elements. Another thing is the dust particles which create some strange vertical lines, which is present on Windows too.

20190702212130_1

sir-ragna commented 5 years ago

I retried with Mesa 19.1.3 hoping the brightness fix for Intel HD might make a difference on my platform but it doesn't. The color and brightness issue remains for me.

supashang commented 5 years ago

For NVIDIA + "Ubuntu MATE 18.04 LTS" and "Linux Mint 19.2" users. I've created a guide here. And to install "dotnet" and "vcrun" via Lutris here.

You can do the same "dotnet" and "vcrun" install as my Lutris patch by using protontricks, but you will need to install it first. Details on doing that are also in the Google Doc.

This guide assumes you have the following correctly installed on your Linux distro.

Graphics Drivers Vulkan WINE See my Google Doc for installing WINE 4.13 (staging) winetricks (Ubuntu) sudo apt install winetricks

Lutris

shadywack commented 5 years ago

Tried the new 4.11-1 version, game still requires the prefix to be modified. Per Redmcg's wiki: Make sure Wine and winetricks are installed, then run STEAMAPPS=~/.steam/steam/steamapps export WINEPREFIX=$STEAMAPPS/compatdata/359320/pfx rm -rf $WINEPREFIX winetricks -q dotnet40 win7

fls2018 commented 5 years ago

Tried the new 4.11-1 version, game still requires the prefix to be modified. Per Redmcg's wiki: Make sure Wine and winetricks are installed, then run STEAMAPPS=~/.steam/steam/steamapps export WINEPREFIX=$STEAMAPPS/compatdata/359320/pfx rm -rf $WINEPREFIX winetricks -q dotnet40 win7

Reason being is that mono does not support WPF, which is needed for the launcher.

oblitum commented 5 years ago

I also have fixed the issue by removing the prefix that comes with the bundled mono dotnet that doesn't work and created a new one with manual dotnet40 install.

At the moment I just started the configuration screen and the demo. One caveat: the demo (which is the actual game) only runs if my controller is disconnected. There's a HID error in case I leave it connected, and it simply exits on start.

Unhandled exception: unimplemented function hid.dll.HidD_GetHidGuid called in 32-bit code (0x000000007b43d65d).
FurretUber commented 5 years ago

The blinking elements problem was solved on Mesa Git, so it's no longer needed to add patches to fix Linux specific issues on Intel. I'm using Mesa 19.2.0-devel (git-d7eb40962b).

The game got in a so stable state that I was fighting Thargoids with graphics set to Ultra on Intel HD Graphics 520. Of course the frame rate was not stellar (15 FPS), but it didn't crash and no rendering bug or any other problem happened.

The graphical problems currently noticed are the vertical lines when dust is present (planetary rings, Guardian ruins, damaged stations and others) and the crash after visiting a few stations due to failure to lock a buffer. As both problems happen on Windows too, there is a workaround to avoid the crash on Linux, Windows refuses to detect my controller and I got "sticky keys" on Elite Dangerous on Windows (losing 2 Imperial Cutter and 1 Python due to problems leaving the station), playing on Linux is the best option.

One year ago I wouldn't believe Elite Dangerous would be playable at all. It's impressive how Proton and Mesa evolved.

FurretUber commented 5 years ago

The development pace is impressive. Mesa 19.2.0-devel (git-16edd02bfa) has the dust bug fixed. Probably some other application had a related bug, as I just commented about this in another bug report and never opened a specific bug report or sent a relevant apitrace.

Now the vertical lines no longer exists in environments with dust, which makes better to see them.

20190818012223_1

kisak-valve commented 5 years ago

Elite Dangerous doesn't load: "Add value to collection of type System.Windows.Controls.UIElementCollection’ threw an exception\

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3027. @kingo55 posted on 2019-08-31T06:19:37:

Compatibility Report

System Information

I confirm:

Proton logs: https://gist.github.com/kingo55/8f5048c79a05dca708f1ece063074593

Symptoms

When I start the game, it fails with the following message:

Screenshot_20190831_131717

Internal error creating window: 

Add value to collection of type ‘System.Windows.Controls.UIElementCollection’ threw an exception.

And there are lines from the log which look suspicious:

11309.473:0037:0038:fixme:dbghelp:elf_search_auxv can't find symbol in module
11309.474:0030:0031:trace:seh:NtRaiseException code=80000003 flags=0 addr=0x7bcab604 ip=7bcab605 tid=0031

Proton logs: https://gist.github.com/kingo55/8f5048c79a05dca708f1ece063074593

Reproduction

I installed ED via Steam and originally the game would not start or show any messages.

Scouring the internet, I found I could use Winetricks to install certain dependencies: https://github.com/redmcg/wine/wiki

E.g. like: 

STEAMAPPS=~/.steam/steam/steamapps
export WINEPREFIX=$STEAMAPPS/compatdata/359320/pfx
rm -rf $WINEPREFIX
winetricks -q dotnet40 vcrun2015 win7

After this, ED stays active for longer but it now shows the prompt with the System.Windows.Controls.UIElementCollection message.

kingo55 commented 5 years ago

Sorry @kisak-valve - I misunderstood what was meant by compatibility report. Cheers for adding it in here.