How to install ED on Linux using Wine [EXPERIMENTAL, NOT OFFICIALLY SUPPORTED]

[Flyinspaghetti]

Okay so basically on Arch this is running really well...



Wine version : ==> Making package: wine-staging-git 3.18.r8.g8519a9ea+wine.3.18.r75.ge55aca8f49-1
Nvidia driver : 410.66.0
Vulkan : 1.1.82
DXVK : 0.90

Working pretty darned good.

Note the FPS seems low but for an AMD Phenom II X4 945 - which I'm pretty sure holds the GTX 1070 back a lot - and Ultra settings and supersampling set to 1.5, that FPS isn't too bad at all.

Most definitely your CPU holding you back, same settings (plus 1.5x SS) & same GPU I get 80 fps sitting in a station, Windows is around 8-10 fps more:

Spoiler

That did it! [heart]

Copied my horizons install over, synced files, now in-game!

Two issues left:

1. "Keyboard" and "Mouse" devices are "missing".
Yea, I just copied over my config file too... I'll fiddle with that some more.

2. Page tearing at ~70% down the screen (vsync not work so good). But that's pretty minor considering it's running!

For bindings both wstephenson and eagleboy have wine patches in this thread that require patching wine source then compiling, wstephenson has also built pre built packages but for openSUSE which are not install-able on Manjaro. I'm not affluent in building and patching wine myself yet but extracted both the 64 & 32 bit rpm packages and manually put together a directory that Lutris could read, kind of dirty way of going about it but it works for me.

You can try this but I don't guarantee it would work for you.

1/ Download this: https://drive.google.com/file/d/1L-YT29YwSZD6HeG93o7wVjW1jxqM6lqO/view

2/ Navigate to /home/yourusername/.local/share/lutris/runners/wine and extract the folder into here.

3/ In Lutris right click game>configure and in the games "custom runner" options change your wine version to custom.

4/ In the select custom executable bit below navigate to: home/yourusername/.local/share/lutris/runners/wine/staging-3.18-x86_64_patched/bin

In that folder you'll see a file called just "wine" (don't use the wine64 ones). Add that.

Then attempt launching the game, if that doesn't work you can simply roll back to Lutris wine staging by going back to step 3.

As for the screen tearing, in your nvidia settings going to X server display configuration>Advanced then clicking force composition pipeline will fix that. Also while you're there disable flipping inside the OpenGL settings tab.

 

[Flyinspaghetti]

So for Arch users, there is an AUR package called wine-staging-git, which when used makes it super duper straightforward to compile the latest bleeding-edge wine-staging from a github repository which just happened to have incorporated the keyboard fixes and whatnot.

I have libopenCL "file already exists" errors when trying to build staging git from the package manager for some reason, but if it's in the latest staging git that means 3.19 staging packages will probably have it as standard.

3.19 just released so in the next couple of weeks we'll most likely see staging versions popping up in distro repositories.

 

[wstephenson]

Logs (<20MB compressed each), links expire after 24 hrs :
ed32_wine_dinput_before.log.tar.xz
ed32_wine_dinput_after.log.tar.xz
ed32_native_dinput_before.log.tar.xz
ed32_native_dinput_after.log.tar.xz

The "after" logs has the lines of the "before" deleted, also were generated without any device connected via usb only keyboard and mouse of the laptop.

Thank you, those are great - except that you've used the URL for ed32_wine_dinput_before.log.tar.xz twice, also for ed32_native_dinput_before.log.tar.xz . Could you tell me the correct url for that file?

 

[Genar-Hofoen]

I have libopenCL "file already exists" errors when trying to build staging git from the package manager for some reason, but if it's in the latest staging git that means 3.19 staging packages will probably have it as standard.

3.19 just released so in the next couple of weeks we'll most likely see staging versions popping up in distro repositories.

Hmm the build operation was flawless for me - then again this was on a completely fresh install of Arch and thus I hadn't tried to do clever things on the system like manually building wine or what have you - you might have had some stray cruft from previous build attempts or something - I've had that before on other projects in other distros many a time.

This is the git repo that AUR uses btw : https://github.com/wine-staging/wine-staging - when I was deciding how to build wine on Arch and had spotted that AUR, I checked where it was getting its source from and spotted that the latest commits at the time included the keyboard fix and decided to give it a go. Works great running ED.

 

[Cmdr Eagleboy]

I have hard time to follow news, everything changes so fast. Will try to do complete overhaul of OP today.

In mean time I can report that it seems my performance issues are down to some weirdness with CPU boundage within Vulkan and/or dxvk. However, when everything just shakes off and game finally gets backing it needs, GPU is turned up to 11, and I get smooth good frame rate. Still with penalty due of translation, but it is way more usable (close to 60 fps everywhere except stations with medium settings). That's with GTX 760. Played for four hours straight today and it was comfortable. Can start to live with that.

Will try to turn some knobs and switches suggested by Flyinspaghetti in nvidia-settings.

 

[Cmdr Ricey]

Same problem here on Ubuntu 18.10, I can't seem to find the missing library.

No, I couldn't fix it either - maybe because 18.10 has dropped 32bit support completely?? Dunno.

I've switched back to Antergos and everything (mostly) is working again.

Haven't seen a change to the keyboard mapping etc with 3.19 though I'll try harder!

Cheers

 

[qgnox]

Thank you, those are great - except that you've used the URL for ed32_wine_dinput_before.log.tar.xz twice, also for ed32_native_dinput_before.log.tar.xz . Could you tell me the correct url for that file?

Oops sorry, I upload those two again because the links are almost expiring
ed32_wine_dinput_before.log.tar.xz
ed32_native_dinput_before.log.tar.xz

 

[qgnox]

This is the git repo that AUR uses btw : https://github.com/wine-staging/wine-staging - when I was deciding how to build wine on Arch and had spotted that AUR, I checked where it was getting its source from and spotted that the latest commits at the time included the keyboard fix and decided to give it a go. Works great running ED.

I think that is the repo that Lutris people manage, so maybe in a few days they are going to release a wine-staging (+esync) version for their client with the normalizestring patch and machineguid fix, or someone has to tell them, and then it will be needed a lutris install script to make it more simple the installation.

If you want to try an esync patched wine-staging-git you can use this repo with Arch.

git clone https://github.com/Tk-Glitch/PKGBUILDS.git
cd PKGBUILDS/wine-tkg-git
makepkg

Supposedly esync helps some games with cpu load, steam proton uses it. I've tested for a few hours and it was a little bit more smooth the gameplay.

 

[wstephenson]

I just found a way to crash ED on Wine repeatably - switch to another virtual terminal ('text console'). On openSUSE, X runs on the traditional vt7, and I was running shred on an old hard drive on vt1, which I went to check - boom.

 

[Noobilite]

I was able to run launcher in my system by following wstephenson's guide but using Wine 3.17. But now I have a new problem - mouse cursor disappears when entering launcher window and I simply can't click any button (they even don't get highlighted). I switched to another WM without any compositing (bspwm), but it does not help. Can't find similar problem in Google and running Wine with emulated desktop doesn't help too.

UPDATE:
I was wrong. That problem with mouse cursor is related to the network connectivity. Currently there is some problems with it in Russia, they blocking many addresses. And it looks like after going into big network via VPN launcher finally works. Now waiting for shaders to prepare.

UPDATE #2:
Was able to login and start online session. Now messing with hotkeys.



UPDATE #3:
Building multiarch Wine is complicated... Got problems when trying to install wine32 build which I compiled under i386 LXC, but that's another story, probably. Will wait for binary 3.19 builds.

Is there supposed to be a mouse curser after going into your ship in open/normal play? I assumed there was a lack of mouse keybind to go to mouse mode to start selecting stuff after you are in your cockpit. Or was the lack of mouse when in the menu screen before starting the game? I haven't played the game besides the demo so I'm not really sure.

 

[BurntJello]

You can try this but I don't guarantee it would work for you.

1/ Download this: https://drive.google.com/file/d/1L-YT29YwSZD6HeG93o7wVjW1jxqM6lqO/view

2/ Navigate to /home/yourusername/.local/share/lutris/runners/wine and extract the folder into here.

3/ In Lutris right click game>configure and in the games "custom runner" options change your wine version to custom.

4/ In the select custom executable bit below navigate to: home/yourusername/.local/share/lutris/runners/wine/staging-3.18-x86_64_patched/bin

In that folder you'll see a file called just "wine" (don't use the wine64 ones). Add that.

Then attempt launching the game, if that doesn't work you can simply roll back to Lutris wine staging by going back to step 3.

As for the screen tearing, in your nvidia settings going to X server display configuration>Advanced then clicking force composition pipeline will fix that. Also while you're there disable flipping inside the OpenGL settings tab.

It worked. Keyboard is "working" in game. But there is still the problem of the device IDs of "Keyboard" and "Mouse" not existing under linux... which I assume is the reason that the default binding configs are missing.

I had edited my copied config to swap "Keyboard" and "Mouse" with the device IDs from wine. (the config file still saved, it just couldn't load with nonsense keys saved in it)

That Composition Pipeline thing fixed the V-Sync issue. Thanks!


The next trick will be to get steamVR working with it... my headset starts, but I've no idea how to get it connected to the game. :S

 

[IndigoWyrd]

1. Boot Linux

2. Open Wine

3. Drink Wine until you've forgotten about Linux
4. Play Elite in Windows because it just works.
5. ????
6. Profit
----


Really, I wish you folks all the success there is, but... by the time you've gotten this all worked out and working, Elite: Deadly will be released, also on Windows.

 

[cpw]

1. Boot Linux
2. Open Wine
3. Drink Wine until you've forgotten about Linux
4. Play Elite in Windows because it just works.
5. ????
6. Profit
----
Really, I wish you folks all the success there is, but... by the time you've gotten this all worked out and working, Elite: Deadly will be released, also on Windows.

Missing a few steps there:
4a. Reboot to windows.
4b. Wait for windows update. (this is a great opportunity to enjoy quite a lot of wine, you'll be here a while. Maybe find some nice cheese and crackers to go with it. And maybe in a good restaurant, because you're gonna be a while. Typically 6-12 hours).
4c. Reboot lots of times because windows updates are fun. (Get more wine, because wine will make this slightly less annoying).
4d. Hope that windows update works, because otherwise you get to watch "update rollback!" messages for the next 6 hours. (Get even more wine. Protip: get a winery, because you'll be drinking a LOT of wine).
4e. Windows finally loads! OK, now wait for steam updates. And for your IO to finally subside (This is usually just a quick glass or two of wine though, just a chaser of wine really).
4f. Play ED. Yay! I hope you're legal to fly with all that wine in you...


Compare: I solved the main problems with Linux + ED a couple of days ago. I have played more ED in the last three days than in the previous two YEARS because windows is just so awful, for me.

 

[Genar-Hofoen]

1. Boot Linux


2. Open Wine


3. Drink Wine until you've forgotten about Linux
4. Play Elite in Windows because it just works.
5. ????
6. Profit
----


Really, I wish you folks all the success there is, but... by the time you've gotten this all worked out and working, Elite: Deadly will be released, also on Windows.

I've been playing ED on Linux all night tonight. Works great thanks o7

 

[IndigoWyrd]

Missing a few steps there:
4a. Reboot to windows.
4b. Wait for windows update. (this is a great opportunity to enjoy quite a lot of wine, you'll be here a while. Maybe find some nice cheese and crackers to go with it. And maybe in a good restaurant, because you're gonna be a while. Typically 6-12 hours).
4c. Reboot lots of times because windows updates are fun. (Get more wine, because wine will make this slightly less annoying).
4d. Hope that windows update works, because otherwise you get to watch "update rollback!" messages for the next 6 hours. (Get even more wine. Protip: get a winery, because you'll be drinking a LOT of wine).
4e. Windows finally loads! OK, now wait for steam updates. And for your IO to finally subside (This is usually just a quick glass or two of wine though, just a chaser of wine really).
4f. Play ED. Yay! I hope you're legal to fly with all that wine in you...


Compare: I solved the main problems with Linux + ED a couple of days ago. I have played more ED in the last three days than in the previous two YEARS because windows is just so awful, for me.

6-12 hours? What's your bandwidth? 4 µ-bits per second?

The absolute longest I've ever seen a Windows update take from download to desktop has been 11 minutes. Long enough to fix a snack and a cup of coffee.

If your updates are failing and rolling back, DISM is your best friend.

And besides, Linux updates too, and when those go bad, and they do, they don't have a rollback. They have a Restore from Previous Image. Or a Start All Over Again.

I'm not down on Linux though. It does what it was designed to do exceptionally well. Those things it wasn't designed to do... well... maybe they can be made to work, maybe they'll mostly work, maybe someone will recompile the kernel to make them mostly work, write a Not-An-Emulator for, or finally just admit that it's far easier to make this thing do what it's supposed to do in the operating system it was designed for and accept that no one operating system is the be-all-end-all of operating systems.

I have more than a few Linux machines myself - a Spam Filter, a Mail Server, a Router (runs my render farm better than either my Cisco or Juniper ever could), and an FTP server. I love reading the logs showing me some loser in Burma or the Czech Republic has been spending hours sending various Windows exploits against my mail server trying to find a spam-farm, and can neither get in or get them to work - because it lies and says it's Exchange 2016, when it's not.

Could I do these things with Windows servers? Sure. But I don't want to. Linux does excellent jobs of these things, and the licensing... it's so much cheaper... well... actually no, because I receive Microsoft Partner packs and Enterprise editions of various things to use in my own environment (Gold Partner), but it weren't for that, it certainly would be!

 

[Genar-Hofoen]

6-12 hours? What's your bandwidth? 4 µ-bits per second?

The absolute longest I've ever seen a Windows update take from download to desktop has been 11 minutes. Long enough to fix a snack and a cup of coffee.

If your updates are failing and rolling back, DISM is your best friend.

And besides, Linux updates too, and when those go bad, and they do, they don't have a rollback. They have a Restore from Previous Image. Or a Start All Over Again.

I'm not down on Linux though. It does what it was designed to do exceptionally well. Those things it wasn't designed to do... well... maybe they can be made to work, maybe they'll mostly work, maybe someone will recompile the kernel to make them mostly work, write a Not-An-Emulator for, or finally just admit that it's far easier to make this thing do what it's supposed to do in the operating system it was designed for and accept that no one operating system is the be-all-end-all of operating systems.

I have more than a few Linux machines myself - a Spam Filter, a Mail Server, a Router (runs my render farm better than either my Cisco or Juniper ever could), and an FTP server. I love reading the logs showing me some loser in Burma or the Czech Republic has been spending hours sending various Windows exploits against my mail server trying to find a spam-farm, and can neither get in or get them to work - because it lies and says it's Exchange 2016, when it's not.

Could I do these things with Windows servers? Sure. But I don't want to. Linux does excellent jobs of these things, and the licensing... it's so much cheaper... well... actually no, because I receive Microsoft Partner packs and Enterprise editions of various things to use in my own environment (Gold Partner), but it weren't for that, it certainly would be!

If I might politely suggest - this thread is about "How to install ED on Linux using WINE" - i.e. getting ED running on Linux. Probably a good idea to start your own thread about whether you approve of running Linux to play games, on some other thread, leaving this one to the technical effort and reports it's meant to be

 

[Darth Ender]

Does the x52 work in Ed: wine? If so it might be worth the effort of being an early adopter.

 

[qgnox]

Lutris already added wine-tkg versions 3.19..

They have esync + wine-staging .

 

[Flyinspaghetti]

Lutris already added wine-tkg versions 3.19..

They have esync + wine-staging .

Yes confirmed keybinds working, my splash screen has gone again though (even with quartz).

 

[Flyinspaghetti]

It worked. Keyboard is "working" in game. But there is still the problem of the device IDs of "Keyboard" and "Mouse" not existing under linux... which I assume is the reason that the default binding configs are missing.

I had edited my copied config to swap "Keyboard" and "Mouse" with the device IDs from wine. (the config file still saved, it just couldn't load with nonsense keys saved in it)

That Composition Pipeline thing fixed the V-Sync issue. Thanks!


The next trick will be to get steamVR working with it... my headset starts, but I've no idea how to get it connected to the game. :S

You don't need to use that as of a few hours ago, the patch for keybinds is in the latest "wine 3.19 tkg" in Lutris.

Keyboard device ID's is an ongoing thing, as someone mentioned in this thread using a native dinput8.dll that is version 6 might make the device ID's normal but you also break controllers doing that.

SteamVR no clue probably a long shot at this stage.