We’re overhauling our wine delivery pipeline as part of the work for the 64bit client. The mac environment needs a combined 32/64 bit wine and I have side-ported that work to linux too.
If you’d like to give it a spin:
Set your launcher to beta mode
Wait for it to patch to at least version 1500694 and restart it
check settings->wine options->Use dev versions
Set Dev branch to winehq-linux-binary (this is only available if you have the latest beta)
Wait for wine to install and launch
Be aware that if you’ve done custom things in the CCP wine folder, this will replace them, and the replacement may not work. Only give this a try if you’re willing to re-create your old wine setup from scratch if it doesn’t work. This is alpha, and you’re the first testers.
Please check in with what distro you’re on, whether you’re using dx9 or dx11 and how it went!
It’s not different. That’s the biggest change to the wine delivery pipeline. The last major revision of CCP wine, which is at this point very old, had a lot of custom patches in it. Some graphics card ID’s that weren’t in upstream wine at the time, a few custom patches to solve eve-specific graphics bugs, stuff like that.
At this point a lot of those custom changes have been solved in upstream wine independently, and we’re working at upstreaming some of the stuff which hasn’t made it. There’s very little left in our custom fork that we can’t upstream and that isn’t already fixed in newer versions of wine, so we’re jettisoning our custom fork.
Instead, we’re taking binaries from the winehq website, fiddling with their shipped libraries a little to make sure they work on the systems we target and then repackaging them so they can be installed by the eve launcher.
Hopefully this will allow us to ship wine builds much faster. Instead of having to custom build them (and have something go wrong every time), we can just grab the most recent binaries, give them a quick QA pass to make sure no regressions have popped in and then “bless” them for delivery through the launcher.
alpha-testing is always such a … bracing experience!
It seems to run on my system, but now that I’ve closed and re-opened the launcher, it’s downloading wine again. Are you still rolling new builds?
UPDATE: OK, it turns out that alt-tabbing doesn’t work. When I go back to the EVE client, the window doesn’t come back up to full screen or grab the mouse. I only see a part of the screen in the upper left, and although I can move the mouse outside of that area, I can’t actually alt-tab back out again, and mouseclicks on what appears to be my desktop actually click things in EVE that I can’t see.
Since the “Log Out” button is outside of the area I can see, I can’t actually log out of the game. I have to use Ctrl-Alt-F4 to kick back out to a terminal and kill the wineserver manually (which additionally kills the X server, so I can’t get back to it).
Yep, I can repro it here too. I’m not gonna look at it today, for the moment I recommend fixed window mode if you want to keep playing with the new build
… Or I could just make sure TeamSpeak/mumble/whatever is setup before I log in for now.
No worries. I’ll fiddle around with seeing if I can get local wine to work again, and see about swapping back and forth between them to check for issues. But otherwise it seems OK.
wow, wow and wow! this is truly an amazing linux client. everything is so smooth and snappy now. even without dxvk. i love it – thanks for your great work!
i think i’ll stick with it, 64bit seem to make a big difference!
Ubuntu 18.04
CPU usage seems to be a bit insane now. Previously with 4 clients I would average ~70% usage. Now i’m averaging 80% usage with 3 clients, and running 4 clients is unplayable. Using dx9 or dx11.
I noticed this before I switched to the beta launcher and winehq-linux-binary, which prompted me to give this a go so it may not be directly related. Previously I was using winehq-stable, btw.
While that sounds cool, I am currently trying out the upcoming MESA 19.01 and the dx11 performance.
Looks like MESA 19 gets a nice push even without Vulkan libs.
I have re-appropriated Steam to install EVE and run with proton 4.23 to check MESA with Vulkan.
So if you like roller coasters and have an iron stomach, you should give it a go.
Surprise everyone, if you have a Steam account, you can run EVE with Steam and your account data.
Vulkan support is active and running by default but Steam runs its own wine libs, which are hidden deep in the Steam folder.
hooo boy I just loaded the client this morning, and man, something went really wrong. It took me nearly 20 minutes to get to the character selection screen, even though CPU load wasn’t any more than usual and there wasn’t any unusual RAM or disk use. And when I got there, the background was a garbled collage of stuff from my browser cache (including a mosaic of my discord page, some fragments from twitter, and a couple news sites) like some sort of google-AI recursive image soup. No visible text, the buttons were all blank. It was wild. When I tried to log out, I got a “Windows has encountered a serious error” popup and had to close out.
But when I started the launcher back up, everything was fine again. Far out.
Also, ever since I switched to the CCP wine binaries, I’ve been unable to switch back to my local wine. I’m using a shell script; is there anything that might be going weird?
Ubuntu 18.04.2 LTS
Intel® Core™ i3-4010U CPU @ 1.70GHz × 4
RAM: 4GB
Radeon™ Software for Linux® 18.50
gpu: AMD Radeon HD 8670M
Running on an old laptop.Tried beta with the said wine version
missing texture patches all over the space ,nothing seem to be missing when inside structure,maybe its the driver idk for sure but everything runs good in dev branch winehq-stable version with release game version.
Participated in some SISI stress testing, with two clients on max settings (DX11). Client was stable and responsive throughout.
OS: Mint 18.3 (with kernel 5.0.15)
CPU: Ryzen 1700, 16GiB ram
GPU: Radeon RX 570, 8 GiB ram
If this is the black cubes in space, it’s a shader problem with gas clouds rather than a texture problem I think. I might try pushing the linux dev build even further upstream and see what happens to this. Science!
So i take back what i said about everything was fine with release version on winehq stable, the same patches appeared on the space again the shape is kinda hard to explain.Also noticed these patches in the map on each of the solar systems when i zoomed in.So then i switched to the opensource driver
OpenGL renderer string: AMD HAINAN (DRM 2.50.0, 4.15.0-48-generic, LLVM 8.0.0)
No issue so far.
On a side note there is some serious fps drop when i launch the map so i keep it minimised all the time and i’m using the new map,this was the case even when i was using 32bit version,i’m guessing this is because of the not so great hardware spec.
