Script (under Test): Elite Dangerous + Steam

[suamor]

I'm trying out the script to install EliteDangerous. Unfortunately I'm stuck in the Steam Installation step.
Up to this step the installation seemed to work fine (wine 4.0 staging, .Net 4.5.2, DX10 and other dependencies installed, not sure why staging was used as stable is released since a longer time).

I have Elite Dangerous from Frontier Store. It is a quite common way to get Elite Dangerous.
Steam should be one of two options (select Installer Package or Download from Steam).

Also it would be great to know how to proceed from here (apart from looking into the script itself).

System: Ubuntu 18.04 (with all updates installed).
Phonicis: SnapShot just downloaded and installed.

[Zemogiter]

Just tested it and I got errors at dotnet452 installation. The same I had in #840 (comment)
Steam installed fine though.

[suamor]

Yes, I have the same here. The Prefix was updated to 4.0 upstream.
Steam works fine, I can install the ED Launcher too, but not start because .Net is broken.

Installing 4.0 via "Verbs" or any later versions fails, independently if wine-mono was installed previously or not. One of the scripts fails on this check and may crash or whatever (no log).

I have not tried anything else than win10 as configuration option.

Update: Issue cause probably related to win7 or (more likely) the preinstalled wine-mono that was not uninstalled. Before quitting Steam I uninstalled manually with wine uninstaller. Afterwards installation of .Net 4.0 and .Net 4.5 went smoothly.

After ED Launcher installation the program crashes.
"mscorlib recursive resource lookup" and "Infinite recursion during resource lookup..." Resource Name: Arg_ExternalException.

The only things I will try now is going back to the latest wine version and trying different win versions.

[ImperatorS79]

"mscorlib recursive resource lookup" and "Infinite recursion during resource lookup..." Resource Name: Arg_ExternalException.

Generally this is the sign of a broken .NET instalation.

Up to this step the installation seemed to work fine (wine 4.0 staging, .Net 4.5.2, DX10 and other dependencies installed, not sure why staging was used as stable is released since a longer time).

You should not use the dx10 verb here, it is far better to use DXVK.

[suamor]

Ok, then I will better try do a completely manual installation so I have a better control and understanding of the individual steps.

I found myself out that 4.5.2 is likely broken, because some winecfg entry had not been set as described here for newer .Net installation including 4.5.2:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=34219

The original 4.5.2 page states that additionally some registry entries need to be set manually. Not sure if this step is still required as it was not mentioned on the other page.

I don't know how dx10 was installed. I checked the script but it is not calling anything related to dx.

Update: I was unable to get rid of the .Net installation problem. It is broken everytime I try it. I tried both 4.5.2 as well as 4.6.1 verb. Next I will try to do it without verb (after installation of 4.0).

[ImperatorS79]

Yes, I just tested it in winetricks and dotnet452 fails also. Maybe try with just dotnet40 or dotnet45. Those verbs (dotnet) seem really broken, even in winetricks :/

[Zemogiter]

Tried installing dotnet472 on Space Engineers prefix via Verbs tab and didn't get any errors.

[suamor]

Simply installed 461 without 452 (manually with /q option) and afterwards I could run EDLaunch (but login gives me graphical error, will have to check logs tomorrow). Also you may need to install libjpeg62. (No verb for dotnet472 on my system, maybe my scripts are already outdated ? or are the downloaded scripts from a different branch ?)

[ImperatorS79]

@suamor when I launch dotnet461, it simply fails...

[suamor]

What I did:

1. Create wine-prefix with phoenics (wine 4.0 upstream)
2. open shell (terminal button, engine tools)
3. $ wine uninstaller -> remove/uninstall wine-mono
4. $ winecfg -> set to windows-xp
5. Install Net 4.0 using phoenics
6. $ winecfg -> set to windows-7 (and check mscoree is set to "native")
7. Install quartz, corefonts etc. using phoenics
8. $ wine64 ../../resources/NDP461-KB3102436-x86-x64-AllOS-ENU.exe /q
9. $ wine64 /path/to/elite/installer (exe) -> can be done with phoenics too (use win7)
10. $ cd /drive_c/Program\ Files\ (x86)/Frontier/EDLaunch/
11. $ wine64 edlaunch.exe

Also I was able to start synching as the graphics sometimes seems to get stable...
For the rest I will probably have to check compatibility with my graphics card (RX 470 8GB Sapphire Nitro), Mesa (on 18), engine settings etc.

[ImperatorS79]

Well, doing this NDP just output 5 fixme's and then nothing on my side...

[suamor]

For a different game I wanted to try out with wine I even was able to install 452 using the resource file. The rest similar as above.

What I was unable to do is to get it working without installing dotnet40 before (in xp mode after having removed wine-mono). I have now edited above steps to make it more clear.

[plata]

Is this discussion still about Elite Dangerous or is it now above dotnet problems in general? If so, we should change the title.

[suamor]

Well for me it is that somebody should fix everything so Elite can be installed and played using phoenicis. We could however create sub-issues for each script that may need to be adjusted.

[ImperatorS79]

@suamor I still do not manage to install dotnet461, it just fails after 3 seconds. So I wonder how it works on your computer 🤔 .

[suamor]

No idea.. just in case, this is my 461:
$ ls -al ../../resources/NDP461-KB3102436-x86-x64-AllOS-ENU.exe
-rw-rw-r-- 1 67681000 Feb 7 17:51 ../../resources/NDP461-KB3102436-x86-x64-AllOS-ENU.exe

Personally I think that the installation in general fails because it first tries to install dotnet40 (because we switched from xp to win7)

[ImperatorS79]

Same... Really strange.

[ImperatorS79]

In phoenicis verbs or in winetricks, the os version is modified multiple times to avoid this.

[suamor]

Hmm.. I can only tell you that I cannot install it with verbs (which should be the same as winetricks). However I'm not sure if I tried verbs 461 without dotnet40 being installed. I can try this on a different prefix...

Update: I have made a test, but like other tests it fails when installing 452 / 461 (not quite sure which step) with a broken dotnet installation. From wine64-uninstaller it looks like net40 was working and 461 is also visible (though apparently broken). So it seems there is a difference between what I was doing manually and what verbs / winetricks are doing.

One small thing I did not mention: When starting up winecfg first time I have no windows version at all. I also think it is after another verbs run, but don't remember which one.

[ImperatorS79]

@suamor Please tell us if this is fixed with latest git.

[plata]

Closed due to inactivity. @suamor please re-open if you have any news.