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

Elite Dangerous (359320) #150

Open
KewaiiGamer opened this issue Aug 22, 2018 · 264 comments
Open

Elite Dangerous (359320) #150

KewaiiGamer opened this issue Aug 22, 2018 · 264 comments

Comments

@KewaiiGamer
Copy link

@KewaiiGamer KewaiiGamer commented Aug 22, 2018

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

@simon50keda
Copy link

@simon50keda simon50keda commented Aug 22, 2018

  1. Navigate to <steam>/steamapps/common/Proton 3.7
  2. Rename user_settings.sample.py to user_settings.py and try to run the game again.
  3. Now go to your home directory and you will find steam-<appid>.log file in there.
@BrandonDyer64
Copy link

@BrandonDyer64 BrandonDyer64 commented Aug 22, 2018

At the bottom of the log, I get this:

pid 30513 != 30512, skipping destruction (fork without exec?)

I think the terminal is asking a question and expecting a response. I tried running Steam in a terminal, but it didn't render this. I'm also not sure how to directly run the game itself in a terminal.

Somehow, I think I just need to answer this question. Adding -y to the launch options doesn't help.

@kisak-valve kisak-valve changed the title [BUG] Elite Dangerous doesn't start [BUG] Elite Dangerous doesn't start (359320) Aug 23, 2018
@Faeranne
Copy link

@Faeranne Faeranne commented Aug 24, 2018

This simply means that the game didn't fork, spawn a new process to continue, so wine/steam didn't need to kill the child process. This almost always shows up once a game using proton closes, successful or not. A sort of rhetorical question for anyone reading the logs.

@Faeranne
Copy link

@Faeranne Faeranne commented Aug 24, 2018

also, Elite: Dangerous still doesn't correctly run inside wine environments. It's mostly there, but so-far only one of the tutorials has actually been run using wine. Unfortunately, it appears that the launcher for Elite is still not successfully running, which is what is crashing. In general, if a game doesn't launch with Steam Play enabled, there is a good chance it just doesn't work in a wine environment yet.

@diraven
Copy link

@diraven diraven commented Aug 25, 2018

I tried it with proton and lots of standalone wine setups with and without dxvk. None have worked, sadly... Hopefully, this will change some day.

@unlimitedbacon
Copy link

@unlimitedbacon unlimitedbacon commented Aug 31, 2018

Here is a complete log file.
steam-359320.log

Running Proton 3.7-5 Beta.
Steam System Info

@physios
Copy link

@physios physios commented Sep 1, 2018

Probably the most important part of that log, idk just trying to be useful

`15872.052:0008:0009:trace:module:load_dll Loaded module L"Z:\home\neo\.local\share\Steam\SteamApps\common\Elite Dangerous\EDLaunch.exe" (native) at 0x400000

15872.052:0008:0009:err:module:LdrInitializeThunk Main exe initialization for L"Z:\home\neo\.local\share\Steam\SteamApps\common\Elite Dangerous\EDLaunch.exe" failed, status c0000017

15872.054:000c:0026:trace:module:MODULE_InitDLL (0x7feca1c40000 L"rpcrt4.dll",THREAD_ATTACH,(nil)) - CALL

15872.054:000c:0026:trace:module:MODULE_InitDLL (0x7feca1c40000,THREAD_ATTACH,(nil)) - RETURN 1

15872.054:000c:0027:trace:module:MODULE_InitDLL (0x7feca1c40000 L"rpcrt4.dll",THREAD_ATTACH,(nil)) - CALL

15872.054:000c:0027:trace:module:MODULE_InitDLL (0x7feca1c40000,THREAD_ATTACH,(nil)) - RETURN 1

15872.071:000c:0025:trace:module:MODULE_InitDLL (0x7feca1c40000 L"rpcrt4.dll",THREAD_ATTACH,(nil)) - CALL

15872.071:000c:0025:trace:module:MODULE_InitDLL (0x7feca1c40000,THREAD_ATTACH,(nil)) - RETURN 1

15872.072:000c:0028:trace:module:MODULE_InitDLL (0x7feca1c40000 L"rpcrt4.dll",THREAD_ATTACH,(nil)) - CALL

15872.072:000c:0028:trace:module:MODULE_InitDLL (0x7feca1c40000,THREAD_ATTACH,(nil)) - RETURN 1

15872.072:0018:001c:trace:module:LdrShutdownThread ()`

@ghost ghost mentioned this issue Sep 26, 2018
@fls2018
Copy link

@fls2018 fls2018 commented Oct 19, 2018

I'd like to add some update on this, with latest Proton versions dotnet installing is fixed so using winetricks/protontricks with a version of wine where dotnet40 doesn't fail (in my case I got 3.17 staging as my system wine) you can install dotnet40 into the Proton prefix.

i.e.
1/ cd to the 359320 compatdata folder

2/ WINEPREFIX=$PWD/pfx winetricks corefonts dotnet40 vcrun2012 quartz

3/ WINEPREFIX=$PWD/pfx winecfg - then set mode back to win7

After doing that launcher should open,but that's only the first half of the battle. There are a number of issues, first is openvr_api_dxvk.dll prevents the main game from displaying the splash screen. Second is a problem previously a roadblock in wine where the CRC check fails making the main game unplayable. Third is another new issue where even the previously playable combat demo would freeze despite working perfectly in standard wine.

@fls2018
Copy link

@fls2018 fls2018 commented Oct 22, 2018

Update: Game is now working in wine but not proton, here's my compatibility report.

Compatibility Report

  • Name of the game with compatibility issues: Elite Dangerous
  • Steam AppID of the game: 359320

System Information

  • GPU: GTX 1070
  • Driver/LLVM version: Nvidia 396.54.09
  • Kernel version: 4.18
  • Proton version: 3.16-3

steam-359320.log

Symptoms

Game now works in Wine staging 3.18 with DXVK using a simple registry fix listed here: https://forums.frontier.co.uk/showthread.php/366894-How-to-install-ED-on-Linux-using-Wine-EXPERIMENTAL-NOT-OFFICIALLY-SUPPORTED?p=7082698&viewfull=1#post7082698

However game still freezes in Proton even after applying the same fixes, the login issue has been resolved but something "Proton specific" causes the game to freeze a minute after starting up.

Here's it running under Wine staging: https://youtu.be/JcDY4WFENug

Reproduction

Similar to the steps in this video: https://youtu.be/jG7TUOXZhng

1/ winetricks corefonts dotnet40 vcrun2012 quartz into the 359320 pfx.

2/ regedit the 359320 pfx and do the following to match the machineGuid of both keys:

Navigate to HKLM/Software/Microsoft/Cryptography
Copy Value
Navigate to HKLM/Software/Wow6432Node/Microsoft/Cryptography
Paste Value

3/ winecfg and set mode to Win7

The above will make the launcher and game start in Steam/Proton and will also fix the authentication error, however game will freeze in about a minute (sometimes sooner). This doesn't happen under Wine staging therefore issue is to do with Proton.

Also @byte1024 post from other thread:

From the log

159005.320:0008:0034:trace:module:LdrUnloadDll (L"rsaenh.dll") - START
159005.320:0008:0034:trace:module:MODULE_DecRefCount (L"rsaenh.dll") ldr.LoadCount: 2
159005.320:0008:0034:trace:module:LdrUnloadDll END
159005.320:0008:0034:fixme:ole:Context_CC_ContextCallback (0x3aadd80/0x3aadd84)->(0x791c8272, 0x30ecc38, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil))
159005.320:0008:0034:fixme:ole:Context_CC_ContextCallback (0x3aadd80/0x3aadd84)->(0x791c8272, 0x30ecbc4, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil))
159005.320:0008:0034:fixme:ole:Context_CC_ContextCallback (0x3aadd80/0x3aadd84)->(0x791c8272, 0x30ecbc4, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil))
159005.320:0008:0034:trace:seh:raise_exception code=c0000005 flags=0 addr=0x15de5665 ip=15de5665 tid=0034
159005.320:0008:0034:trace:seh:raise_exception  info[0]=00000000
159005.320:0008:0034:trace:seh:raise_exception  info[1]=00000000
159005.320:0008:0034:trace:seh:raise_exception  eax=00000000 ebx=000000d5 ecx=030eca20 edx=1d4d94a0 esi=03eda098 edi=03ab3a1c
159005.320:0008:0034:trace:seh:raise_exception  ebp=030ecae8 esp=030eca80 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010206

rsaenh.dll is Microsoft Enhanced Cryptographic Provider. Must have to do with the registry change. Not sure why it works differently with Wine VS Proton though.

Wine 3.18 does have two changes however, so not sure if that makes a difference here:

  rsaenh: Move PKCS1 padding and unpadding functions.
  rsaenh: Implement RSA OAEP.

https://www.winehq.org/announce/3.18

Would have to see where the exception is going to.

Wonder if the dll provided with Wine would solve it with Proton?

I've tried this and it doesn't work, it seems Proton itself uses a builtin rsaenh library and doesn't launch when you try to use a native version.

Also I'm not sure Cryptography is the issue anymore as this freeze occurs even on the combat demo which was working perfectly fine in wine before the registry fix.

@fls2018
Copy link

@fls2018 fls2018 commented Oct 26, 2018

Another update: Thanks to RedMcG again on the frontier forums I have now got into the game in Steam Proton... BUT using anymore than one CPU core will freeze the game.

screenshot from 2018-10-26 13-35-38

Simply follow the winetricks, regedit & winecfg steps in the post above, to get into the game without it crashing "taskset -c 0 %command%" needs to be set in the launch options. Obviously not very playable but it works.

Bu the question is why using more than one thread cause issues with this game in Proton yet not with Wine Staging?

@mirh
Copy link

@mirh mirh commented Oct 26, 2018

The esync patch set is probably the first diff that comes to mind..

@fls2018
Copy link

@fls2018 fls2018 commented Oct 26, 2018

The esync patch set is probably the first diff that comes to mind..

I'be already tried PROTON_NO_ESYNC=1 %command% , tried older versions of Proton too no difference. Tried WineD3D instead of DXVK still freezes up.

Maybe some implementation Wine has which Proton's missing?

@LudusLight
Copy link

@LudusLight LudusLight commented Oct 27, 2018

I'm having trouble with your solution. I feel like I could be missing something obvious, considering I'm new at troubleshooting Proton, but perhaps this may come in useful anyways.

I tried the following on two distributions (Solus 3.9 & Ubuntu 18.04):

  1. Run winetricks corefonts dotnet40 vcrun2012 quartz in the pfx
  2. regedit the pfx, copying the key from /HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/ to /HKEY_LOCAL_MACHINE/Software/Wow6432Node/Microsoft/Cryptography
  3. Set the mode to Windows 7 in winecfg within the pfx
  4. Set the launch options to taskset -c 0 %command% (as well as trying without)

After doing that, launching the game has no effect. There is no launcher, and no game. Here are the log files:

steam-359320-ubuntu.log
steam-359320-solus.log

@ghost
Copy link

@ghost ghost commented Oct 27, 2018

I'm having trouble with your solution. I feel like I could be missing something obvious, considering I'm new at troubleshooting Proton, but perhaps this may come in useful anyways.

I tried the following on two distributions (Solus 3.9 & Ubuntu 18.04):

1. Run `winetricks corefonts dotnet40 vcrun2012 quartz` in the pfx

2. `regedit` the pfx, copying the key from `/HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/` to `/HKEY_LOCAL_MACHINE/Software/Wow6432Node/Microsoft/Cryptography`

3. Set the mode to `Windows 7` in `winecfg` within the pfx

4. Set the launch options to `taskset -c 0 %command%` (as well as trying without)

After doing that, launching the game has no effect. There is no launcher, and no game. Here are the log files:

steam-359320-ubuntu.log
steam-359320-solus.log

At least with Ubuntu you're getting:
13053.551:0008:0009:err:module:LdrInitializeThunk Main exe initialization for L"Z:\\media\\bigboy\\SteamLibrary\\steamapps\\common\\Elite Dangerous\\EDLaunch.exe" failed, status c0000017

I'm not sure why though. The log doesn't have anything immediately noticeable to me. Comparing it to Solus is the only difference I notice:

"19373.147:0008:0009:trace:module:load_dll Loaded module L"Z:\\home\\light\\.local\\share\\Steam\\steamapps\\common\\Elite Dangerous\\EDLaunch.exe" (native) at 0x400000" ... continues on ...

Perhaps bad exe on Ubuntu or the storage location doesn't work well? If there's something else in the log, I don't feel like trying to find it =)

With Solus:
19373.233:0008:0009:err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed
So that's self explanatory.

@fls2018
Copy link

@fls2018 fls2018 commented Oct 27, 2018

I'm having trouble with your solution. I feel like I could be missing something obvious, considering I'm new at troubleshooting Proton, but perhaps this may come in useful anyways.

I tried the following on two distributions (Solus 3.9 & Ubuntu 18.04):

  1. Run winetricks corefonts dotnet40 vcrun2012 quartz in the pfx
  2. regedit the pfx, copying the key from /HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/ to /HKEY_LOCAL_MACHINE/Software/Wow6432Node/Microsoft/Cryptography
  3. Set the mode to Windows 7 in winecfg within the pfx
  4. Set the launch options to taskset -c 0 %command% (as well as trying without)

After doing that, launching the game has no effect. There is no launcher, and no game. Here are the log files:

steam-359320-ubuntu.log
steam-359320-solus.log

I should be clearer as you don't appear to have mscoree listed in your log.

First thing needed is having at least wine staging 3.17 or higher installed on your system to install dotnet40, along with installing winetricks.

Assuming you have steam installed in the default place open terminal and type (replacing yourusernamehere with yours):

WINEPREFIX=/home/yourusernamehere/.steam/steam/steamapps/compatdata/359320/pfx winetricks corefonts dotnet40 vcrun2012 quartz

Install those clicking on the accept when installers pop up then:

WINEPREFIX=/home/yourusernamehere/.steam/steam/steamapps/compatdata/359320/pfx regedit

Edit the keys as stated above then:

WINEPREFIX=/home/yourusernamehere/.steam/steam/steamapps/compatdata/359320/pfx winecfg

Change to win7.

All done the launcher should work, you might get rundll32.exe errors but just continue on.

@LudusLight
Copy link

@LudusLight LudusLight commented Oct 27, 2018

I'm having trouble with your solution. I feel like I could be missing something obvious, considering I'm new at troubleshooting Proton, but perhaps this may come in useful anyways.
I tried the following on two distributions (Solus 3.9 & Ubuntu 18.04):

  1. Run winetricks corefonts dotnet40 vcrun2012 quartz in the pfx
  2. regedit the pfx, copying the key from /HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/ to /HKEY_LOCAL_MACHINE/Software/Wow6432Node/Microsoft/Cryptography
  3. Set the mode to Windows 7 in winecfg within the pfx
  4. Set the launch options to taskset -c 0 %command% (as well as trying without)

After doing that, launching the game has no effect. There is no launcher, and no game. Here are the log files:
steam-359320-ubuntu.log
steam-359320-solus.log

I should be clearer as you don't appear to have mscoree listed in your log.

First thing needed is having at least wine staging 3.17 or higher installed on your system to install dotnet40, along with installing winetricks.

Assuming you have steam installed in the default place open terminal and type (replacing yourusernamehere with yours):

WINEPREFIX=/home/yourusernamehere/.steam/steam/steamapps/compatdata/359320/pfx winetricks corefonts dotnet40 vcrun2012 quartz

Install those clicking on the accept when installers pop up then:

WINEPREFIX=/home/yourusernamehere/.steam/steam/steamapps/compatdata/359320/pfx regedit

Edit the keys as stated above then:

WINEPREFIX=/home/yourusernamehere/.steam/steam/steamapps/compatdata/359320/pfx winecfg

Change to win7.

All done the launcher should work, you might get rundll32.exe errors but just continue on.

This was a full fix. Thank you.

@FurretUber
Copy link

@FurretUber FurretUber commented Nov 4, 2018

After using all the winetricks and changing the values in regedit as proposed here, the game crashes in the shader loading stage. When I'm lucky I can see the shaders loading until 10% and then the game crashes. I tried both with DXVK and with Wine D3D11, tried setting video memory in regedit to 128 MB and to 2048 MB but had no luck.

The errors using DXVK and Wine D3D11 are different but seem related:

Wine D3D11:

2851.011:00ab:00c8:err:seh:call_stack_handlers invalid frame 58a3c478 (0x58b02000-0x58c00000)
2851.011:00ab:00c8:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.

DXVK

2169.251:00aa:00d3:err:seh:setup_exception stack overflow 3760 bytes in thread 00d3 eip 00007f85128ef532 esp 0000000058ed0760 stack 0x58ed0000-0x58ed2000-0x58fd0000

The complete logs:

steam-359320-d3d11.log
steam-359320-dxvk.log

On Windows, both host and iGVT-g guest, shader loading takes 1 or 2 seconds.

System specifications.

@amalon
Copy link

@amalon amalon commented Nov 5, 2018

Wine D3D11:

2851.011:00ab:00c8:err:seh:call_stack_handlers invalid frame 58a3c478 (0x58b02000-0x58c00000)
2851.011:00ab:00c8:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.

DXVK

2169.251:00aa:00d3:err:seh:setup_exception stack overflow 3760 bytes in thread 00d3 eip 00007f85128ef532 esp 0000000058ed0760 stack 0x58ed0000-0x58ed2000-0x58fd0000

I get the same thing with Haswell desktop integrated graphics:

cpuinfo:
model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz

vulkaninfo:
apiVersion = 0x401050 (1.1.80)
driverVersion = 75505668 (0x4802004)
vendorID = 0x8086
deviceID = 0x0412
deviceType = INTEGRATED_GPU
deviceName = Intel(R) Haswell Desktop

glxinfo:
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Haswell Desktop (0x412)
Version: 18.2.4

I had put it down to being Intel graphics specific (there's a warning about the vulkan driver being incomplete), which you also appear to be using.

@FurretUber
Copy link

@FurretUber FurretUber commented Nov 5, 2018

I don't think it's Vulkan, more specifically Intel ANV, the problem. If it was, the bug that happened when using Wine D3D11 translation to OpenGL would be different. Notice how the addresses from the error messages are very close, it seems to be some common code between i965 and ANV or even the i915 kernel driver.

@redmcg
Copy link

@redmcg redmcg commented Nov 5, 2018

But the question is why using more than one thread cause issues with this game in Proton yet not with Wine Staging?

I looked in to that and found the answer lies with a single patch in wine-staging:
https://github.com/wine-staging/wine-staging/blob/master/patches/ntdll-futex-condition-var/0001-ntdll-Add-a-futex-based-condition-variable-implement.patch

I patched Proton 3.16-4 Beta with this patch and now it runs fine without needing any tweaks to the launch options.

I just created a fork which, in addition to the above, fixes a few other things with ED in Proton 3.16:

  • key-bindings (and presets)
  • intro videos (winetricks quartz not needed)
  • CRC Error (no work-around required - it runs launcher with wine64)

I'm happy to share the binaries if anyone knows a decent place to upload them. I haven't tested them on another machine yet, but I compiled against the Steam Runtime - so I think they should work on distros other than Ubuntu 18.04 (on which I compiled).

@agates
Copy link

@agates agates commented Nov 5, 2018

In case anyone comes here with "preparing planet generation system" issues on Horizons, there are some AMD-specific DXVK issues along with some work arounds. Check out doitsujin/dxvk#36.

@Rabcor
Copy link

@Rabcor Rabcor commented Nov 6, 2018

This game apparently can run pretty well but it requires wine 3.19 staging. Requires dotnet452 vcrun2012 to run correctly.

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

@redmcg why don't you create a pull request for proton's wine with that patch?

@redmcg
Copy link

@redmcg redmcg commented Nov 6, 2018

@redmcg why don't you create a pull request for proton's wine with that patch?

I have now (see ValveSoftware/wine#33) - but taking a look at the ones that are there I don't see much success (after all - these patches are for one game tested on a single machine).

But I do think Valve cherry-pick the ones that interest them from upstream - so this may bring the individual patches some attention.

@Rabcor
Copy link

@Rabcor Rabcor commented Nov 6, 2018

@redmcg why don't you create a pull request for proton's wine with that patch?

I have now (see ValveSoftware/wine#33) - but taking a look at the ones that are there I don't see much success (after all - these patches are for one game tested on a single machine).

But I do think Valve cherry-pick the ones that interest them from upstream - so this may bring the individual patches some attention.

This patch was upstream in wine staging right? They'll probably apply it then, if it was good enough for wine-staging, it's probably good enough for proton.

@redmcg
Copy link

@redmcg redmcg commented Nov 7, 2018

I've created a Git 'release' that includes a tarball with the binaries from my fork. It's compiled on Ubuntu 18.04.1 but against the steam runtime - so I think it should be fine on other distros. I'd be interested to hear how it goes (on other machines and potentially with other games). You can find instructions and the release here:
https://github.com/redmcg/wine/releases/tag/ED_Proton_3.16-4_Beta

@redmcg
Copy link

@redmcg redmcg commented Apr 11, 2021

@madewokherd Thanks for letting us know. I just tried the latest (after the revert) and fortunately you can still launch the game, but any other interaction with the launcher will generally cause it to crash.

@Atamisk
Copy link

@Atamisk Atamisk commented Apr 11, 2021

Replying to #150 (comment)

I just realised i forgot to tell everyone that my particular appears to have its roots in Mesa. Downgrading to resolved my problem.

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented Apr 11, 2021

@redmcg
Copy link

@redmcg redmcg commented Apr 23, 2021

Unfortunately, I had to revert one of the commits because it was causing the wine tests to hang, so this may not make it into 6.2 after all.

Good news, as of commit madewokherd/wine-mono@90fd1a4, this is now working again. Thanks again to @madewokherd @g-insn.

I've updated my wiki to include a link to the GitHub CI build of this commit (which is a zip with the MSI in it).

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 19, 2021

Okay Odyssey does RUN for me (with either patched or old mesa), but performance on foot is pretty awful. Hopefully something can speed it up

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 19, 2021

Looks like Im getting the wrong GPU reported in odyssey (RX 470 vs RX 570 -- people have seen similar things with NV GPUs)

@lorddickfist
Copy link

@lorddickfist lorddickfist commented May 19, 2021

Odyssey unable to even start launcher even after mkdir. Getting error initiatlizing, here is the log.
steam-359320.log
Running mesa latest on Arch

@redmcg
Copy link

@redmcg redmcg commented May 20, 2021

@lorddickfist It looks like you're running Proton-6.1-GE-2 and wine-mono version 5.1.1. You'll need wine-mono 6.1.1 or later - otherwise you'll get the following error:
image

You can follow the instructions here to install a custom version of wine-mono:
https://github.com/redmcg/wine-mono/wiki#install-custom-version

But if you'd prefer to use an official wine-mono version - you can download those here:
https://github.com/madewokherd/wine-mono/releases

@dsalt
Copy link

@dsalt dsalt commented May 20, 2021

Looks like I'm getting the wrong GPU reported in odyssey (RX 470 vs RX 570 -- people have seen similar things with NV GPUs)

It's probably looking at the PCI ID and ignoring or not recognising the revision number (which will be 0xDF for your 570, vs. 0xCF for the 470). The same misidentification seems likely for the RX 480, 580 and 590.

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 20, 2021

Likely performance issues caused by that? someone with a 3xxx card was misidentified as a GTX 470 as well, I believe

@Atamisk
Copy link

@Atamisk Atamisk commented May 20, 2021

I am having no performance troubles, RX590 with mesa git latest on arch. 40ish fps on planetside, which is ...fine... I think it's down to optimization now.

@lorddickfist
Copy link

@lorddickfist lorddickfist commented May 20, 2021

@lorddickfist It looks like you're running Proton-6.1-GE-2 and wine-mono version 5.1.1. You'll need wine-mono 6.1.1 or later - otherwise you'll get the following error:
image

You can follow the instructions here to install a custom version of wine-mono:
https://github.com/redmcg/wine-mono/wiki#install-custom-version

But if you'd prefer to use an official wine-mono version - you can download those here:
https://github.com/madewokherd/wine-mono/releases

It got the launcher and the game running but odyssey isn't installed still unfortunately.

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 21, 2021

Odyssey will take a giant download etc

@kisak-valve
Copy link
Member

@kisak-valve kisak-valve commented May 23, 2021

Elite Dangerous: Odyssey DLC performance issues

Issue transferred from #4846.
@artemantcev posted on 2021-05-23T06:35:12:

Compatibility Report

  • Name of the game with compatibility issues: Elite Dangerous (only with Odyssey DLC)
  • Steam AppID of the game: 359320

System Information

  • GPU: NVIDIA GeForce GTX 1060 6GB
  • Driver/LLVM version: NVIDIA 460.73.01
  • Kernel version: 5.8.0-53-generic
  • Link to full system information report as Gist:
  • Proton version: Proton 6.3-4

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

There's a problem that makes Odyssey DLC totally unplayable for me: it's a huge FPS drop (from 30 to 1-3 FPS) that happens if I open and close the System map while being on a station or any other space-leg location. After this my VRAM is used at 100% and the only way to return the game to its normal state is to restart it completely.

Reproduction

  1. Start the game
  2. Visit any space-leg location
  3. Open the system or galaxy map one or multiple times while standing there
  4. Get a huge FPS drop after closing the map
@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 23, 2021

Odyssey performance issues are an odyssey thing not a proton thing. The game is awfully optimised as it stands. People on windows with recommended specs are having awful performance.

@kakra
Copy link
Contributor

@kakra kakra commented May 23, 2021

Yeah but a drop from 30 to 1-3 fps is still quite huge. For me it started the same on a GTX 1660 Ti (which is probably a lot more powerful but still). After some testing it looks like the new engine with its new effects is a lot more sensitive to screen resolution: Previously, I was running at 4k with 0.85 scaling, I'm now using 1440p with 1.0 scaling. This makes text appear a little less sharp, the overall quality is not affected much. Next, I followed recommendation to delete the graphics settings folder in the user profile to let ED re-init the settings. I'm now going with medium profile instead of high (I think they updated the profiles to be more demanding), and now I'm back to steady 60 fps in space, and inside space stations I get around 25 fps. It's still quite poor, other games look a lot more polished at that resolution with 50+ fps, so there's still a lot to be done by Frontier. But it is a good compromise until that happens.

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 23, 2021

Yeah there are lots of things they still need to do. Someone picked apart their draw calls and found a significant lack of culling etc. as for the memory issues, thats also a known bug I believe.

@Mallchad
Copy link

@Mallchad Mallchad commented May 23, 2021

It's not a Proton problem, not even slightly.
I'd like to remind to that at this point a poor experience under Proton is more and more often becoming a problem
with the game itself just generally being problematic, not Proton itself.

As was mentioned there are significant problems for all players with Odyssey, and I'm not sure any of them, at all are
Proton related.

@Oliver-1xok
Copy link

@Oliver-1xok Oliver-1xok commented May 24, 2021

Elite Dangerous: Odyssey DLC performance issues

Issue transferred from #4846.
@artemantcev posted on 2021-05-23T06:35:12:

Symptoms

There's a problem that makes Odyssey DLC totally unplayable for me: it's a huge FPS drop (from 30 to 1-3 FPS) that happens if I open and close the System map while being on a station or any other space-leg location. After this my VRAM is used at 100% and the only way to return the game to its normal state is to restart it completely.

My specs:

  • GPU: NVIDIA GeForce GTX 970
  • Driver/LLVM version: NVIDIA 460.73.01
  • Kernel version: 5.4.0-73-generic
  • Link to full system information report as Gist
  • Proton version: Proton 6.3-4

I think I have exactly the same problem with Odyssey. I just hadn't figured out how to reproduce it. When it happens, the described performance drop also happens in space as soon as you call up a map. It is permanent until restart. I have about 20 FPS in space afterwards, before that I always have 60 FPS.

My VRAM is also completely full except for a few bytes. However, this already happened under the normal Elite and did not lead to this FPS drop. I don't know why this drop happens with Odyssey, but it happens at some point during play. The last time it happened was after I was walking on a planet. I flew back into space and called up the system map. After that I only had around 20 FPS. I then quit the game after about a minute. I had the Proton log running:
steam-359320.log

Odyssey's performance is not great as we all know, but this drop goes far beyond that and really makes the game unplayable. Of course, it is possible that the problem also exists under Windows. Unfortunately, I cannot test this.

@CSahajdacny
Copy link

@CSahajdacny CSahajdacny commented May 24, 2021

Keep in mind the 3.5GB issue of GTX 970...

@Oliver-1xok
Copy link

@Oliver-1xok Oliver-1xok commented May 24, 2021

Keep in mind the 3.5GB issue of GTX 970...

Yes, that's right. But then it would be likely that the problem also occurs under Horizon. The VRAM is completely full after an hour at the latest. I have over 400h in Horizon. Often up to 8h at a time without encountering this problem. And @artemantcev has a 1060 with 6GB. However, apparently these 6GB are also filled.

I have also tried to limit the memory via dxgi.maxDeviceMemory in my DXVK conf. This did not help. Elite always occupies everything that is available after a certain time. Nevertheless, the game has been playable so far. This drop is new. I cannot judge whether this is a Proton problem. It would be interesting to see if this behaviour can also be observed under Windows.

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 24, 2021

its a reported bug on frontier's issue tracker

@Oliver-1xok
Copy link

@Oliver-1xok Oliver-1xok commented May 24, 2021

its a reported bug on frontier's issue tracker

Thank you. Do you have a link to it?

EDIT: https://issues.frontierstore.net/issue-detail/32129

OS Linux

Are there reports that explicitly mention Windows?

@Oliver-1xok
Copy link

@Oliver-1xok Oliver-1xok commented May 24, 2021

https://issues.frontierstore.net/issue-detail/31191 as well

This is a different problem. The point is that the FPS drop in the normal game is permanent as soon as you leave the system map or the galaxy map. And that permanent drop adds to Oddysey's already poor performance and FPS drops. The VRAM problems also exist under Horizon. They can lead to temporary FPS drops, but do not make the game unplayable. At least not until Oddysey.

I have found two tickets for the problem described here. Both mention Linux:

https://issues.frontierstore.net/issue-detail/32129
https://issues.frontierstore.net/issue-detail/25349

The ticket that has already expired also mentions Windows 10, which is the only reference to Windows that I have found for this problem so far.

If it is a problem that also exists with the supported version of the game, then it should be fixed in the next few weeks. Let's wait and see.

Once again: The performance of Oddysey is poor. But this permanent drop makes it unplayable. You have to restart the game after it. At least on my system.

@A-UNDERSCORE-D
Copy link

@A-UNDERSCORE-D A-UNDERSCORE-D commented May 24, 2021

That was a thing that people experienced during the alpha, though I never saw it, there were also a lot of LOD issues. But agreed, this is gonna be a few months in the making so we shall see. Personally Im still waiting for mesa 21.1.1 in repos

@Mallchad
Copy link

@Mallchad Mallchad commented May 24, 2021

Can I ask for some help from people?
As we know a lot of people have been getting game crashesm Windows users and all, so I'm wondering if I have inadvertently found a game bug.
In my steam proton log I repteatedly have been getting this message before a crash.

[0000000000000714:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: `MonoBtlsPkcs12.Import` failed.
[0000000000000714:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: Missing private key

Can anybody else replicate this? I've discovered it happens far more frequently around players in open.
To get your proton log right click on your steam game and click on propetries
Navigate to Advanced Launch Options and fill in the STEAM_LOG=1 enviornment variable appropriately,
You will have to place in %command% after if it's empty
for example PROTON_LOG=1 %command%

@JT8D-17
Copy link

@JT8D-17 JT8D-17 commented Jun 3, 2021

The performance issue I've had in Odyssey's tutorial (did not try anything else), i.e. 20-30 FPS and massive stutters on a 6900XT and 5800X, no matter the detail level, resolution and Mesa version seems to have vanished after running it with Proton 6.9-GE-2. Getting 100 FPS now, which is more in line of what can be expected.

@madewokherd
Copy link
Collaborator

@madewokherd madewokherd commented Jun 5, 2021

Unfortunately, I had to revert one of the commits because it was causing the wine tests to hang, so this may not make it into 6.2 after all.

Good news, as of commit madewokherd/wine-mono@90fd1a4, this is now working again. Thanks again to @madewokherd @g-insn.

I've updated my wiki to include a link to the GitHub CI build of this commit (which is a zip with the MSI in it).

Wine Mono 6.2.0 has been released and should work as well as that build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet