I've been using the lutris launcher with wine 3.19, so I selected the audio option to use "ALSA" instead, inside lutris. ALSA is already configured to use pulse by default (I have the standard .asoundrc that routes to pulse). To switch audio devices, I just use pavucontrol to reroute ED's sounds. Seems to work great. I think you can do all this by using winecfg too (under the audio tab there).
How to install ED on Linux using Wine [EXPERIMENTAL, NOT OFFICIALLY SUPPORTED]
I've been using the lutris launcher with wine 3.19, so I selected the audio option to use "ALSA" instead, inside lutris. ALSA is already configured to use pulse by default (I have the standard .asoundrc that routes to pulse). To switch audio devices, I just use pavucontrol to reroute ED's sounds. Seems to work great. I think you can do all this by using winecfg too (under the audio tab there).
Is it just me or did the launcher just get much less buggy when running in wine? I'm no longer getting significant visual artifacting, and it seems to be downloading much more quickly.
Last edited:
Hey everyone!
We've had reports that the above "experiments" are causing some technical problems in-game. The issues aren't just happening for those playing Elite Dangerous on Linux, but also for players who end up in the same instance while playing on PC.
Just a reminder that Linux is not an officially supported platform, and we are currently investigating these issues. We wanted to let you know so you don't too much time on something that we can not support, and that could potentially change.
Thanks,
Ed
Thanks Ed for letting us know. There's no issue, you can fix things if you required to, we understand that. But if problem can be shared with us, it would be cool to let us know, so we can actually fix it so it doesn't bother you at all. Cheers
Please let us know if it's IPv6 or something we can possibly configure in Wine.
Then work. with. us. to get these issues sorted out. You have a lot of very clever folks working in Frontier, but there are a lot of very clever and knowledgeable Linux users and developers outside of Frontier. Would it not benefit everyone if you didn't go into an insular, walled-garden mode and instead did things like list any issues arising?
Regards.
What is the actual request here, Ed? Cease operations on Linux, only play in Solo, only play with each other in a Penguin Cmdrs private group?
I'm assuming from your message that the issue is in peer to peer connections between commanders in the same session, something like upnp or MTU discovery, or firewall state detection. Do you need our participation in helping identify the cause of the issue? We've got Wine committers here and Linux distribution people, and network protocol specialists, and there may be issues specific to one underlying flavour of Linux that someone of us is using.
I'm assuming from your message that the issue is in peer to peer connections between commanders in the same session, something like upnp or MTU discovery, or firewall state detection. Do you need our participation in helping identify the cause of the issue? We've got Wine committers here and Linux distribution people, and network protocol specialists, and there may be issues specific to one underlying flavour of Linux that someone of us is using.
Last edited:
Yes, but if not the fine people here then work with Valve to bring ED on Steam Play officially a reality: https://github.com/ValveSoftware/Proton https://github.com/ValveSoftware/Proton/issues/150
Yeah my post came off as a bit peeved - because I was. Combination of lack of sleep and a fear that FDEV will stomp all over attempts to run ED on anything but Winduhs.
ED's running really well on my Arch installation, so much so that I haven't really had to boot into Windows 10 and I'm attempting to make a linux port of my application.
It would be a pity if all the effort you guys have been putting into this was stomped on. :/
It would be great if Frontier would at less supported Elite through Steam play. Then a Linux version would be needed yet
.DC out
To be honest I can't tell from the language in Ed's post, whether it's a "we're shutting this down" or whether it's a "we don't want to break anything but we might have to remove this functionality which may cause issues".
It may even be just the case some disgruntled persons with a bad internet connections are reporting us Linux folk are breaking their game and they have to investigate.
I'm hoping they don't deliberately go out of their way to break this though, there are people who've been wanting to play this game on Linux since the kickstarter.
Muahahaha
Well then Mr Lewis it may just be time to officially support linux. That is the direction the winds are blowing! More and more people are dropping windows for linux.
Well then Mr Lewis it may just be time to officially support linux. That is the direction the winds are blowing! More and more people are dropping windows for linux.
For what it's worth, the ability to comfortably run on Linux might actually be the thing that gets me to log back in to Elite. It's the only thing on my Windows disk, and given that I have to have my main Linux installation running as much of the time as possible (for work reasons too in-depth to go into here), casually firing up Elite whenever I fancy it isn't really practical.
Go on, Ed - I know it's not "officially supported", but chucking a few hours of dev time into working out a solution that can be both community-supported and tolerable to FDev surely isn't out of the question?
Go on, Ed - I know it's not "officially supported", but chucking a few hours of dev time into working out a solution that can be both community-supported and tolerable to FDev surely isn't out of the question?
As far as I read Ed's comment I suspect this is more "if clients will cause trouble we will filter them out in matchmaking" vibe than "we will ban Linux users". Which as I said totally ok - if client behaves way it causes trouble for others, it should play alone (until it doesn't).
My only wish is FD letting us to know what exactly it is. I doubt they can or will ban Linux gamers.
Also depending on nature of issue we can recommend to play Solo if there's solution required that is not available in code yet.
Proof? Nah. Hyperbole? Yes.
Of Steam's 125m+ users, a whole 0.72% use Linux...
Windows Steam users outnumber them by 144-to-1, and even Mac Steam users outnumber them 4-to-1. This month Steam Linux usage dropped by 0.06%, oh dear
Looks like FDev might be correct in not allocating devteam to such a miniscule section of the gaming community. SteamPlay might be a worthwhile option if its userbase isn't also tiny.
Last edited:
Well, that's a very disappointing read from Ed. What do we think might the problem be here? Is it that Linux has a better networking stack - is it breaking timing for others? Maybe because Linux has better firewalling, meaning the instancing doesn't work as well?
This is a topic for discussing getting it working (or not). There's another thread where you can pretend over one million passionate gamers are not worth anyone's time.
they can't really do much more about it: either address the side effect or deliberately block wine usage (always good to remember, this is running on wine, not linux) which would be clunky, intrusive, legally dubious and really a bad reaction. however, if they do decide to support this they will be placing themselves in an awkward position regarding future incompatibilities. so, no, frontier is probably not happy with this.
Fun fact since the fix was discovered I've literally done two waypoints of an expedition on Linux without a hitch (well nothing out of the ordinary regarding connections etc in expeditions).
[video=youtube;MKZJMpCPafo]https://www.youtube.com/watch?v=MKZJMpCPafo[/video]
Stream from windows users perspective:
[video=youtube;t9NcJ-8x0Fw]https://www.youtube.com/watch?v=t9NcJ-8x0Fw[/video]
That's sort of why... 'while it is plausible' I'm not 100% buying that these reported issues are a result of Linux.
What am I looking for? A 2 hour livestream is a lot of footage to go through.
I will challenge your legal assertion about "blocking Wine usage". There have been historical instances of negative actions taken against Wine based players - I was once banned from WOW for a short period because I used Wine to play ~12 years ago (!). They quickly recinded the ban, but not for legal reasons but for PR reasons - it garnered significant negative attention. Legally, Blizz was fine - they can do what they want with their game. The same goes for Frontier - it's their game, if they want to ban Wine play, that is within their right.
Regarding "support" - I think that Frontier should join valve in partnering for official support on SteamPlay myself. Not only would that support Linux (we've got demonstrated functionality right into the current beta, working well), but it would also give them a way to potentially give Mac players a way to play again as well. I don't believe that program puts an onerous level of requirements on the partner, but rather Valve and the Proton team take the lions share of compatibility responsibility.
Watching that livestream a bit, I still haven't seen anything that could be uniquely ascribed to the presence of Linux - it sounds like the normal instancing glitchiness they've had for years at this point, and is as much a factor of running simulation code on the game PC as anything, and relying on customer's uplink to get timely updates to the rest of the instance.
Edit: one final thought on "blocking Wine". Feasible? Yes? Long-term viable? Almost definitely not. We know the game works now. If Frontier tries to detect and fail when Wine is present, we have the capability to fix that. Which becomes a really really stupid arms race. That's why Blizz blocked the users, not the client - users are much easier to lock out (well, that and it was a Watchdog bug, but meh).
Last edited: