Elite:Dangerous for Linux?

If i could play ED on Linux id do it.. I have a double boot system... i use ubuntu for baying bills..purchases ect. Just because its a lot more secure than windows. I use windows just for gaming. If ED would go to Linux id get rid of windows. Alot of other games have went to Linux. The x series X3 Albion prelude and Rebirth for example.
 
In the short-term, running Elite in a virtual machine on Linux (QEMU/KVM) with GPU pass-through (VFIO-PCI) works well enough with the newer kernels (If you have the spare hardware/licenses laying around.) As nice as a native Linux/SteamOS port would be all indications are that it is not going to happen anytime soon short of someone like Valve throwing a mountain of cash at FD.
 

Does it still get a CRC error if you try to use the normal client? It's nice to see the grahics cleaned up completely though. 8)

And does the launcher start with dxvk? It stopped working for normal wine as far as I can tell with 3.3-3.6.

Also, has anyone asked the people at frontier if they know about the program and risks about being banned for it. Did anyone ever shoot them an email and ask? There could always be an odd circumstance and having your game and money taken isn't exactly a fun thing.(I've always been under the assumption wine isn't modified but just has calls and this may be a new issue.)

https://hk.saowen.com/a/1241b027a4faaafe9e8fae93fd8c2def857513d2daa86df7a1b40194bd96789e

Online multi-player games

Manipulation of Direct3D libraries in multi-player games may be considered cheating and can get your account banned . This may also apply to single-player games with an embedded or dedicated multiplayer portion. Use at your own risk.

On a side note:

I've noticed people calling 3.5 wine as staging. Is this a different version or are they all staging now? and where is the option to turn off staging? I saw a video with someone showing 3.5 and it had an ability to activate/deactivate CSMT. This is missing from my version. Staging in earlier versions like 2.19-staging caused the launcher not to work. You needed the staging version of wine but it had to have csmt turned off to start the launcher. Or is the launcher working for everyone else with normal 3.5 wine?

Interesting. I just found a 3.6 staging in the winehq stuff. I didn't know it went up that far. which is giving me errors when trying to install from dnf?!

Am I the only one running into this? I get this every so often. Especially with the winehq stuff.
Code:
$ sudo dnf install winehq-staging-3.6 --best --allowerasing
Dependencies resolved.
===========================================================================================================================================================
 Package                                       Arch                             Version                             Repository                        Size
===========================================================================================================================================================
Installing:
 winehq-staging                                x86_64                           1:3.6-1                             WineHQ                            75 k
Upgrading:
 wine-staging-common                           i686                             1:3.6-1                             WineHQ                            26 M
 wine-staging64                                x86_64                           1:3.6-1                             WineHQ                            27 M

Transaction Summary
===========================================================================================================================================================
Install  1 Package
Upgrade  2 Packages

Total download size: 53 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): winehq-staging-3.6-1.x86_64.rpm                                                                                     512 kB/s |  75 kB     00:00    
(2/3): wine-staging64-3.6-1.x86_64.rpm                                                                                     3.2 MB/s |  27 MB     00:08    
(3/3): wine-staging-common-3.6-1.i686.rpm                                                                                  2.9 MB/s |  26 MB     00:08    
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                      5.9 MB/s |  53 MB     00:08     
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  file /usr/bin/function_grep.pl from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/msiexec from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/notepad from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/regedit from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/regsvr32 from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/widl from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wine from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wine-preloader from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wine64 from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wine64-preloader from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wineboot from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winebuild from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winecfg from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wineconsole from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winecpp from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winedbg from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winedump from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winefile from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wineg++ from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winegcc from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winemaker from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winemine from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/winepath from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wineserver from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wmc from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/bin/wrc from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/applications/wine.desktop from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/de.UTF-8/man1/wine.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/de.UTF-8/man1/wineserver.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/fr.UTF-8/man1/wine.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/fr.UTF-8/man1/wineserver.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/man1/wine.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/man1/wineserver.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64
  file /usr/share/man/pl.UTF-8/man1/wine.1.gz from install of winehq-staging-1:3.6-1.x86_64 conflicts with file from package winehq-devel-1:3.6-1.x86_64

Error Summary
-------------

I'd prefer they continue developing on the platforms they support.

This would result in unofficial support so they don't have to divert or get new resources necessarily.
 
Last edited:
Alright it has been a long time since I have posted in here but here goes.

Clean install of wine-staging 3.6 installed the dxvk patches for vulkan. I am running mesa 18 on both buntu and arch (tested on both).

Installed . Net 4.5 through wine tricks (have to run winecfg to change back to win7 after it installs) . Net is a bit of a mess but it gets there.
Quartz through wine tricks and then get wine to run EDLauncher from my steam install.

The launcher is a bit of a mess but it does allow for logging in and verification.

The game itself launches and the shaders compile properly.
Sadly the game pops up with a login error shortly after.
Might be something simple like a regedit that could allow the login to work. I will keep persevering with a few things.
 
You might be able to bypass the launcher if it works by referencing the individual files for the game.

$ WINEPREFIX=~/ed-wine wine64 "c:/Program Files (x86)/Elite Dangerous/Products/COMBAT_TUTORIAL_DEMO/EliteDangerous32.exe"
$ WINEPREFIX=~/ed-wine wine64 "c:/Program Files (x86)/Elite Dangerous/Products/elite-dangerous-64/EliteDangerous64.exe"

No gaurantees though.

NVM, totally misunderstood that somehow. 8) My brain is farting today.

Did you try the tutorial? It's generally easier to get into. If it's as stable as it was in 3.2 it shouldn't be hard to get basic keyboard shortcuts setup(assuming they are still missing) and then play the tutorials for fun. I've beaten all but the last one with the crappy graphics before DXVK was working.

Edit: Can someone help me with this?!

https://github.com/doitsujin/dxvk/blob/master/README.md

./package-release.sh master /your/target/directory --no-package

I installed all the things it said it needed(Except maybe, "(requires threading support).") I downloaded the package to my downloads folder. I then put the zip/tar in the DXVK folder.

And, I previously made the DXVK folder. mkdir /home/user/DXVK

user = shorthand for user name.

I ran the script from within the DXVK folder and it just puts a tar file there instead of doing anything. But it has lots of errors...

Code:
$ sudo ./package-release.sh master /home/user/DXVK --no-package
Error during basic setup:

Neither directory contains a build file meson.build.
ninja: error: loading 'build.ninja': No such file or directory
cp: cannot stat '/home/user/DXVK/dxvk-master/install.64/bin/d3d11.dll': No such file or directory
cp: cannot stat '/home/user/DXVK/dxvk-master/install.64/bin/dxgi.dll': No such file or directory
cp: cannot stat '/home/user/DXVK/dxvk-master/install.64/bin/setup_dxvk.sh': No such file or directory
rm: cannot remove '/home/user/DXVK/dxvk-master/install.64': No such file or directory
Error during basic setup:

Neither directory contains a build file meson.build.
ninja: error: loading 'build.ninja': No such file or directory
cp: cannot stat '/home/user/DXVK/dxvk-master/install.32/bin/d3d11.dll': No such file or directory
cp: cannot stat '/home/user/DXVK/dxvk-master/install.32/bin/dxgi.dll': No such file or directory
cp: cannot stat '/home/user/DXVK/dxvk-master/install.32/bin/setup_dxvk.sh': No such file or directory
rm: cannot remove '/home/user/DXVK/dxvk-master/install.32': No such file or directory

Do I have to manually put those files in there?

I've also tried to install ninja into the directory with the github CL, but it didn't do any good.

git clone git://github.com/ninja-build/ninja.git && cd ninja

Do I have to install ninja in the correct place? It's not available in the fedora repository that I can tell.

Edit: I was reading a reddit thread about them dumping mac. They kept mentioning they should change to vulkan. Made me wonder. Can't they just make a custom layer to make their current setup work through vulkan or literally do like wine and translate... I would think since it's their custom coded tools they could do this. And possibly more. Then maybe they could get it up and working on all systems. Is vulkan low level enough they can just do what they want with it and design equivalent custom Vulkan references or something?! I've been wondering lately why all programs just don't go through translation layers with their tools and have a massive tool with references to all languages in binary or other neutral code to give custom language references and translate or work through multiple tools in multiple way.s There is a natural neutral language for computers.
 
Last edited:
Extremely excited to hear news about your (or anyone's) results with trying to get Elite:Dangerous to run with the new Steam Play!

If i understand correctly, it does report back to the publisher that the game is being played in Linux via Proton.. if that's so, then I will have no more qualms about waiting to buy it, as I will show up as a statistic TO FRONTIER that people with Linux want to play this game..

With any luck it'll actually be something resembling playable, and maybe all you brave dualbooters will have one less reason to dual boot after all!

fingers crossed!
 
Curious as why linux is so special. I've been using osx for productivity for many years now, and can easily accept to play games i'm going to need a separate install / hardware / partition.

If you need something to help, placing windows as nothing more than a games console will help your unix platform feel superior :) Sitting in a vm and a games console is all it does now. Even this is old news to me, meh who cares about windows.

EDIT: If its because your linux is feeling underwhelming, try hackintosh. If you have the right hardware its been so trivial to get up and running for many osx versions now. You get transparent terminal windows, and it plays games! Not elite, but you'll be fine.
 
Last edited:
Curious as why linux is so special. ...

Can't speak for everyone else, but for me it's because it is my OS that does what I want, the way that I want it, when I want it to, and not what/when I don't. Sure, it can be a bit of a headache at times, but at least it works for me as apposed to working for someone else as a "service" for me. Debian/KDE. YMMV

It's kind of like the difference between owning a home and renting one, if that makes sense. :)
 
Last edited:
I'm continually amused in my deployments - we'll plop in a z13 platform here, overhaul a 360, maybe even prod some life back into AS/400 - and the question I always hear is "How can we make Linux cheaper?"
 
Can't speak for everyone else, but for me it's because it is my OS that does what I want, the way that I want it, when I want it to, and not what/when I don't. Sure, it can be a bit of a headache at times, but at least it works for me as apposed to working for someone else as a "service" for me. Debian/KDE. YMMV

It's kind of like the difference between owning a home and renting one, if that makes sense. :)

Yep. Osx is still like that. At least in intent, osx is still a pure os, theres no services business model meta put ontop of it, and its far from an appliance as it was pitched a decade ago. Its only the most rare thing you get turned away from, and on hackintosh none. In the utility + development context its incredibly powerful to make your own. Too long ago now i used to main linux... funnily enough as a command line os i was in love. It was only when x got involved that it felt flakey enough to look elsewhere. OSX has an iron clad windows environment for graphics and a mouse. Having said, im sure especially with ubuntu doing what it does i'm sure its alot better these days. The OSX distro of bsd isn't too bad :p


I'm continually amused in my deployments - we'll plop in a z13 platform here, overhaul a 360, maybe even prod some life back into AS/400 - and the question I always hear is "How can we make Linux cheaper?"

Lol given frontier is frontier id laugh if the stellar forge was being powered by a 400.
 
This is kind of offtopic.

Yep. Osx is still like that. At least in intent, osx is still a pure os, theres no services business model meta put ontop of it, and its far from an appliance as it was pitched a decade ago. Its only the most rare thing you get turned away from, and on hackintosh none. In the utility + development context its incredibly powerful to make your own. Too long ago now i used to main linux... funnily enough as a command line os i was in love. It was only when x got involved that it felt flakey enough to look elsewhere. OSX has an iron clad windows environment for graphics and a mouse. Having said, im sure especially with ubuntu doing what it does i'm sure its alot better these days. The OSX distro of bsd isn't too bad :p




Lol given frontier is frontier id laugh if the stellar forge was being powered by a 400.

OSX is not a "distro", it's a product, made by a company, to extract capital and personal data (to sell for more capital) from you, the consumer. Saying there's no services on top of it (hello iTunes) is disingenuous at best.

Linux (like BSD (which OSX is not)) is a project, often distributed with many other projects, plain and simple. Derivitaves of OSX are not sanctioned by its maker, and OSX's maker consciously obsoletes the OS (and its dedicated hardware) out from under the user for profit, while legally challenging those who would dare use their "Product" on non-licensed platforms.

Linux, being a project, has no such agenda, nor puts (legal or technical) barriers or limits on who can develop it to run on what. Linux, instead, runs on nearly any platform and processor regardless of age, and as a result; you are free to maintain it all yourself.

Freedom is sometimes work, so if you want to pay someone for a product and let them do the work for you and force you to pay them more when they want, go for it, it's a free market, in fact most people don't seem to mind this arrangement.

People don't use Linux out of a sense of smugness or superiority. People use it for saftey, privacy, and a sense of ownership over one's own bits. Caring about your digital life is a lamentable rarity among computer users.

As for AS/400s, 360s and zSeries.. Those aren't relevant to gaming at all, they're not even x86 compatible architectures. Freedom is sometimes paid work, and obviously you're a professional managing enterprise concerns if you're dealing with Linux and that kind of iron. It is not relevant to the topic of gaming or Elite: Dangerous's ever coming to Linux.

Meanwhile, nobody's tried E: D in Steam Play yet??
 
Last edited:
I've not tried ED for various reasons but can see from a reddit post that its not launching, doesn't look like any workarounds have been tried.
I was trying out a few VR titles and they actually work OK with a bit of reprojection happening, have to say for a beta it looks promising though !
 

While the differences in effect may be marginal in practice depending on someone's specific needs, I've changed some fundamental things about how Debian runs for me, such as how it handles reading, writing, moving, and deleting data for my SSDs, what it loads and does when it boots, and similar type things that would generally be obfuscated from end users, if not downright functionally unavailable in some other proprietary/private OSs without "hacking" them.

I did mean in the literal sense that "Linux" was my OS, as these sort of modifications are actually supported by the OS itself and the community of development around it, passing some of these sort of things back upstream and around to others publicly.

But hey, I still use Windows 7 too and like it for what it has to offer. Haven't done as much myself with Mac OSs, but I have run into some issues supporting them from time to time and likewise with Windows where Apple or Microsoft would push out an update that would break some functionality, slipping through our vetting process at the time. That's neither here nor there really though. If an OS works well for someone, that's the main thing, though I wouldn't necessarily call it their OS.

YMMV
 
Last edited:
I've not tried ED for various reasons but can see from a reddit post that its not launching, doesn't look like any workarounds have been tried.
I was trying out a few VR titles and they actually work OK with a bit of reprojection happening, have to say for a beta it looks promising though !

rats! I guess I'm stuck waiting still then..
 
I think it is a time for small update for wine staging 3.16. Steam Play uses DXK convertor, but that really means little in scale of things at the moment. Not sure what's their plans to allow winetricks levels of modifications though. However again it will mean little if we will be able to run ED directly via Wine.

1. There are issue with .NET launcher - donet452 is required from winetricks (Mono doesn't cut it), but it doesn't install clearly in 3.16. However people report it installs properly with wine git master. Will try at some point and report findings;
2. Issue however remains with CRC error. It seems FD does internal encrypting/decrypting of communications and that doesn't work properly under wine, generating wrong fingerprints. if anyone feels fun poking that bear, be welcome;

Anyway, be welcome to join the party, links with ideas and instructions

https://bugs.winehq.org/show_bug.cgi?id=43464
https://forums.frontier.co.uk/showt...ng-Wine-EXPERIMENTAL-NOT-OFFICIALLY-SUPPORTED
 
Back
Top Bottom