Heh, that is a pretty strange criteria to chose a distro if you ask me.
What I mean is that you sometimes have to compile your own stuff, but Gentoo has made it into mainstream. It allows for everything to be compiled, but nobody really needs this. It then doesn’t really offer the flexibility of a self-made script, which performs only very specific tasks and steps. So you’ll only end up making your own scripts again with Gentoo.
I then prefer a normal distro where I can get the binaries, but also the source if I want to compile them myself. However, I pull my sources from git and sometimes choose not the master branch, but some other branch. I then apply my own patches to them in some cases.
Gentoo just doesn’t have that, hence I call it mainstream.
Gentoo’s ebuilds can build/install directly from a git branch. An ebuild is nothing else than a build script with a library of useful helper functions called by the package manager which handles dependencies, sandboxed compilation, and tracking of installed files so you don’t pollute the system.
But by all means if you like custom scripts then use them
Version 1330184 worked for me as well.
I found the way to bring all to work.
At first I wondered that after switching to development version and restarting the launcher it switches back to beta. Then I’ve saw that after switching to development it restarts first time and the version is correct 1330184, but for some kind of reason it switches back to beta and asking to restart again, after I agreed to restart the version was 122XXXX.
So the true way is:
- Start the launcher
- Switch to the development version
- Say yes to warning about using development version
- Say OK when the first restart is required
- After restart - say cancel to restart request
- And here we go, logging in successful
Thank you, this worked for me as well
workaround form Alyx works like a charm…
It would be nice from CCP that she give a clear statement about the linux launcher and when she are not willing to support them, then a statement, that the linux launcher are no longer usable.
Hey all, just to helicopter in and let you all know what’s going on:
a) the linux launcher is, and always has been, an unofficial side project that a few linux-using devs have run during their spare time. It is not supported by CCP, which means it’s not guaranteed to be up to date, and the GM’s can’t help you much if you have issues.
b) I’m taking up the torch from CCP Snorlax, but I will literally be working on this in my spare time, kicking off builds at like 9pm. That means I won’t be working on it every day or even every week, but I’ll put in what I can, partly because I use it as well and partly because I believe linux support is worthwhile.
c) I’m working on an updated build now, but I can’t give any timeline at all. I’m porting the whole shebang forward 5 minor revisions of QT and moving the build chain to base on 16.04 at the same time. If I understand the situation correctly this will fix the ssl symlinking issue, but to be honest I’m re-learning skills I haven’t used in about 4 years so we’ll see.
Thank you for having at least an opportunity to run eve on Linux. And it’s great that at least somebody does it.
I would buy you a beer at a meeting for what you are doing
Waiting for fixes.
@CCP_Bartender, Nice to hear that, which are a bright spot atm. I have today my launcher scripts updated so she can handle now the problem, that after an restart of a updated/changed launcher he hangs again while the updater cleaned up the launcher directory from foreign files or links (which are ok and he should always do that). If you want to use my stuff, you are welcome. See the thread EVE Installing where i have posted links for my downloads and my website.
I know its not christmas, but in this post Help Installing EVE on Ubuntu 18.04 i have written my wishes for an updated launcher.
Thank you so much for even considering bringing this side project forward! How can I buy you a beer for that?
So if this isn’t an official piece by CCP then why not just open source it and put it on GitHub?
I’ll be looking at updating the wine version once I’ve got the current launcher building. A casual look suggests that the mac and linux wine builds are currently linked by a common repo (https://github.com/ccpgames/wine) which I know essentially nothing about at the moment.
I’d be keen to know what peoples experiences with DX11 under wine 3+ are, I’ve been sticking to dx9 mode myself. Stable? Artifact free? Not yet? Specific versions of wine that seem to work better than others?
I’m using DX11 mode since Wine version 3.0 and it is stable on my hardware so far (using Nvidia GTX 750 TI with driver version 390.77 stable branch). If you use the DX11 mode over OpenGL, which are the default setting in wine you have as penalty a lower frame rate than in DX9 mode but better visual effects like you have, when you run EVE on Windows.
Steam uses for her beta version from Steam Play a customized version of Wine 3.7 so should the CCP git version wine 3.10 do the same job as well. As an afterburner for the DX11 mode uses many of us DXVK which the Steam Play beta has already included.
Its not a must but it is preferable, because the using from DXVK with EVE in DX11 mode gives higher frame rates, lower power consumption and you can more graphics settings like in WIndows using with it. Disadvantages are for me atm i have little artifacts on the HUD outside of the Stations if i use DXVK, but i can live with that.
@Whitehound has more experience with this problematic he uses the last Nvidia beta drivers which should not have these artifacts anymore, but its beta. Besides if you use the linux launcher or windows launcher which he does, both uses in the end wine to run EVE himself.
Early WINE 3 version had issues with anti-aliasing under DirectX11 over OpenGL. They showed a black screen when it was turned on. This later turned into a working GUI, but with the 3D graphics still black, and latest version I’ve tried is 3.15 and AA is working correctly now.
But if you’re really looking at DirectX11 then do look at DXVK, too, or else you’re already behind before you even started.
And to be quite frank, if you’re not going to make the Linux launcher open source then you might just drop it altogether and focus on getting EVE to run smoothly with Steam Play / Proton, because this seems to be the future for gaming on Linux in the near future. People can already install Steam on their Linux boxes and from there it’s pretty easy to get EVE running with DirectX11 at high frame rates, because Steam is using DXVK and a couple other patches to bring the speed up. To pack the EVE Linux launcher with a version of WINE is what Steam has now done with Steam Play / Proton and you’d be copying them at best.
Hrm, DXVK is going to increase the minimum system requirements to mandate cards which support vulkan though, right?
Is DXVK a more faithful implementation of directx in terms of the final visuals, or just faster?
My preference would be to keep the default wine as compatible as possible, and let people make their own computer specific setups for higher performance, unless the non DXVK performance is going to be too poor to use, or unless non-DXVK implementations look broken.
See here for a comparison:
Speed of DirectX11 over Vulkan is almost twice as fast when compared to OpenGL and the power consumption is a lot lower, too.
The author is being payed by Valve Software. So this is likely the more faithful implementation, probably the best you could ever hope for. I don’t like how it’s a set of DLLs and that it wasn’t put directly into WINE, but this is just how it is now.
DirectX12 is also being worked on for WINE and while it, too, gets rendered over Vulkan, is it a part of WINE’s source code unlike DXVK. There is no DirectX12 over OpenGL implementation from what I’ve seen and don’t think anyone would want this. Vulkan then is available for Nvidia and AMD as well as Intel on-board graphics.
There is Vulkan for Android, which lets players run WINE on their mobile phone and means they could play EVE Online on their phones.
The system requirements don’t increase necessarily. You’d still have to use WINE, which means you’ll also be able to run with DirectX9 and X11 over OpenGL. Only Vulkan is the way forward and what people will want, but it’s not somehow exclusive. It would be an optional feature to have with OpenGL always being available as fallback.
Your problem will be that when you don’t add DXVK straight to it, then why should people use it when they can just get it all over Steam and all inclusive? With Steam you get EVE news and special EVE offers, you can play other games with it, and so forth. With Steam do players get to use the Windows launcher and they can be certain not to be using any software that is somehow different from the Windows version. It’ll be difficult to see an advantage in using a Linux-native launcher over Steam when it isn’t at least on par with the Steam performance.
I would prefer using the CCP git version 3.10 as first test without any changes, which Valve has done, as long the CCP version are not changed in any cases from the WineHQ version. If the user has the choice to select the used wine version it should be a good start for this. If the user want to using DXVK so he can install it later with winetricks.
But you get it only, when you have always a Steam account. The advantage from a linux launcher is in this case, he dont need an installed Steam. Sure you can use the windows launcher with a pure wine, but why not a linux launcher also? So please, let CCP or in this case @CCP_Bartender decide, what to do or not.