MESA is actually just the name for OpenGL, but because OpenGL is a trademark is the free version of it called MESA. The Nvidia driver then provides a library for MESA, which accelerates the graphics operations and this is why it then says Nvidia in the version string.
In short, your OpenGL seems just fine.
Next step is to either make a clean installation of EVE, or clean out any DLLs you may have installed in your WINEPREFIX directory and also to reset any library settings in winecfg (the part where one can specify of native should come before builtin and so forth).
The last step results in, a repeat of last time. I get a crash notification (there is some output in the terminal that I wont post because we donāt have code tags.) The launcher pops up as a grey box. I can interact with the little E icon (which changes settings), the minimize and close buttons, but the rest of the lanucher is just grey.
We do have code tags. Itās called Markdown. Somebody thought that with all the markup defintions it was time for one more and he called it markdown ā¦ anyhow:
You can start an inline code block with a single ` character and end it, too. When you start an entire line with three of them ``` then it acts like a code tag and also needs three more for the end.
example
example
When you write something directly after the first ``` then it selects the syntax highlighting style. I often use text as the style to remove any highlighting.
When I said I had wine 3.0 running that was true. I was however screwing with the versions earlier. The install I had eve working on was using wine 3.7 so I wanted to get to a newer developer version. Since I canāt find a guide (or even bad instructions) on how to run a custom wine version inside a wineprefix I just ran
I use a chroot environment to build my own wine version. One for the 32-bit part and another for the 64-bit part. This means I run make three times. Once for 32-bit, then for 64-bit and the last for the combined build. Sounds tedious bit it doesnāt take that long really (20min or so). The documentation for this is here:
The tedious part is really only the setup part for the build environment. You basically have to install two small Linux distributions into the chroot environments and use each to build a part of WINE.
Have you tried installing the game with the 3.0 version? Does this work at all? Iād start with getting to a WINE version that is known for you to work and then from there try newer ones.
I am a little sceptic though about the āartfulā part. It should probably say ābionicā or ābeaverā, but there are no packages for it. No idea why this is.
Itās getting late for me, but one more thing which comes to mindā¦ I know Debian likes to call itās binaries for the development version not āwineā or āwinecfgā but it calls them āwine-developmentā and āwinecfg-developmentā. If this is something Ubuntu does too, then you need to watch out for it and use the right ones.
I went back to using the playonlinux GUI. So far itās a bit better then just entering the commands manually.
I started a new 32bit virtual drive and installed wine 3.9.
I ran the launcher install and it proceeded normally.
I decided to just do the same thing I did last time I had it working and just spam install things from the winetricks list. (FYI play on linux has a different GUI then the usual winetricks interface.)
Installing Microsoft Core Fonts had no effect. I still got an identical crash message and a grey box. However, installing dotnet40 and running the launcher again opens a normal looking EVE Online Launcher.
I got the __GL_THREADED_OPTIMIZATIONS=1 and the WINEDEBUG=-all tweeks working and FPS is tolerable (about 20 FPS per client) with two clients running with all high in dx11 mode.
In dx9 mode about 3 clients are working at about 30 FPS each. In dx11 mode 3 clients is total garbageā¦ 1-2fps.
Iāll see what having the game fully downloaded does to FPS and try swapping to Xfce tomorrow.
Thereās nothing else really to do about the FPS in dx11 mode is that right?
Not on the OpenGL part. Only by going over to DXVK can one get framerates for DX11 close to those of DX9. Xfce4 should give you another boost when youāre under GNOME right now. In Xfce4 when you there go into the settings Window Manager Tweaks and disable the compositor, too, then youāre as close to the bare X11 server as you can get.
Iām a bit baffled why it would need dotnet40 for you. It isnāt needed for Debian and I wouldnāt have expected Ubuntu to need it either. It may be a playonlinux requirement perhaps.
Thanks, that appears to a fixed a ton of annoying behavior with the way different wine windows interact. It would have made xfce unusable for EVE.
There was some performance gain with the new desktop. FPS didnāt really climb but there are fewer periods where the frame rate tanks down to 1-2 due to too much CPU usage. (All 4 cores run at 100% with 3 clients running.)
Do you know any other ways to optimize CPU usage?
I have absolutely no idea.
I installed dotnet40 via winetricks on the last prefix I was working yesterday. And when I went to run the lanucher there was no change in behavior. I just had a grey box again.
Hereās the logfile play on linux keeps.
There has to be something unrelated to dotnet that their winetricks script does which is un-breaking/breaking something in the right way.
This is the part where DXVK really shines. The use of Vulkan has dropped CPU usage heavily. When I minimize both my clients then the CPU is at 6% and clocks down. This is great with summer knocking at the door.
Let me know if you want help with DXVK, but itās all the same as before and how Iāve described it earlier.
After reading your thread i have Ubuntu 18.04 reinstalled to have a look, if i have the same problems like you. Installed Nvidia drivers 390.48, wine-development 3.6 with software manager.
Then i setup a 32bit wine prefix and run inside the windows installer. Installation runs fine leave me a desktop launcher which i have launched. EVE Launcher comes up and crashed as by you before. Then i installed via winetricks corefonts, launcher comes up and gives me a white window but after a while filled the white window with launcher datas and run normal as expected. The funny part for me is, that the windows launcher open a little window for the systray icon which i have not with the linux launcher. FPS around 20 with dx11 all settings high and AA of high too. GL_THREADED_OPTIMIZATION gives no advantages by me (4 core cpu).
On my standard installation (Debian Buster/Sid) i have csmt for EVE disabled maybe its a solution. BTW wine or better qtwebengine under wine seems to be problematic, its not only the EVE Launcher, who has these problems, even Battle.net app from Blizzard has these too.
CSMT seems to improve performance for several games, which is why I left it on. Itās now officially enabled since WINE 3.5 (I think) and considered stable as well as beneficial. Most users should not change it unless they have a reason to.
True, i put this off, because my cpu are without CSMT enabled 10 degress cooler and it brought me no advantages. FPS are the same with or without CSMT.
I have this test made again with wine-devel 3.9 from WinHQ with the same result, FPS around 20, AA high, cpu frizzles around 75 degrees after a while with CSMT enabled.
I have noted that framerates under dx11 start out slow and laggy. Super odd but very repeatable: Start game; immediately pull up fps window. Slow. 20-30 fps. Then about 30 seconds in it kicks up to 70-110 and normal without lag.