KDE’s exclusion of xwayland has led to related issues.
This is probably related.
I’m using KDE and Wayland.
I think DE information is very important for determining compatibility.
Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.57+deb13-amd64 (64-bit)
Graphics Platform: Wayland
Not sure what you mean by “KDE’s exclusion of xwayland” …i think you mean KDE exclusion of x11, right? xwayland is a program that runs on top of wayland to display x11 software…i would wonder why and how KDE “excludes” that? But i could be wrong of course…
I use a classical x11 system:
OS: Debian GNU/Linux 12 (bookworm) x86_64
Kernel: 6.1.0-41-amd64
DE: MATE 1.26.0
WM: Metacity (Marco)
I am on EndeavourOS Ganymede, running EVE via Steam. Every time I read on the forum there is a problem with the launcher I wonder how I managed to doge it. I just assume they are running EVE via the launcher directly.
Can you elaborate if you are running EVE via steam or the launcher directly?
Sorry.
It seems I was mistaken.
I assumed that KDE’s plan to discontinue X11 in 6.8 would also mean discontinuing xwayland.
I checked and found that they plan to continue supporting xwayland and discontinue X11.
In any case, the wayland compatibility status of DEs and WMs, and each person’s use of X11 and wayland, should be important information.
Whether or not an executable file launches, the perceived speed, and actual FPS can all make a big difference.
And why would you need to downgrade the launcher? The whole point is that all the latest launchers after 1.9.4 DO run on wine without any problems as opposed to other methods with steam and lutris…
Also directx12 works.
My winetricks for reference (old but running, and also the components versions can break things):
./winetricks corefonts msdelta vkd3d vcrun2022 dxvk2030
How i launch EVE:
env WINEPREFIX=“/home/USER/.wine” WINEESYNC=0 WINEFSYNC=0 VKD3D_CONFIG=force_raw_va_cbv wine C:\users\USER\AppData\Local\eve-online\eve-online.exe
Steps to create a new EVE Online play environment using wine
Since I received valuable information, I created a new /home and experimented.
Thank you Power Armor.
Starts without environment variables or some components
I compared it with adding environment variables, etc., but I can’t tell the difference.
I suspected wayland because I kept having problems with wayland, but it didn’t matter.
My environment is Radeon, so there may be a big difference in the case of Nvidia.
(If you have an nvidia environment, please report)
Supplementary notes for Wayland environment
・To enable discord screen sharing in a wayland environment, [wayland to X11 Video bridge] and pipewire are required.
・OBS or Spectacle are convenient for shooting EVE gameplay videos. Spectacle is easy and quick to use, but requires pipewire.
The Wayland environment in EVE Online offers a very smooth operating feel.
This is especially noticeable in environments with relatively low specs.
Even if the FPS drops to around 20, you will no longer feel stuck.
The reason I needed app-1.9.4
was because I was having trouble launching the new EVE launcher.
I never thought DXVK would affect whether the launcher would launch or not.
I knew some people had successfully launched the new launcher,
but the necessary steps were unclear for a long time.
Yes i run nvidia and also this dxvk issue for the launcher was unknown to me…i added it about a year ago according to a forums suggestion somewhere here to enable directx12. Back then there were no launcher problems without it and i don’t know if i would have them today on nvidia.
Both Arch and Manjaro make it simple to swap Wine versions. Currently from a terminal prompt, I can type;
sudo downgrade wine
This will display 189 wine builds to choose from, starting at wine 4.0rc6 and ending with wine 10.2 but these are only the stable builds. For staging, I would need to use the package manager.
It’s nice to have options for application version control.
But switching to a different distribution just for that reason isn’t worth the effort.
I’ve tried various methods, including local archive storage with Lutris and ProtonUpQt, and Flatpak.
I’m very happy with the convenience of installing and updating a single metafile, winehq-stable, only when necessary.
I thought you were using debian…downgrading and upgrading winehq-stable, winehq-devel and winehq-staging is all the same on debian, very easy and already described in post #2 of this thread: WINE 11 - Eve launcher broken - #2 by Power_Armor
Not attempting to coerce anyone to swap to Arch/Manjaro or anything they are not comfortable using. I currently run wine tests in 3 versions of Ubuntu variants, Arch Linux, Manjaro, and 2 different Debian versions. I also have a small SSD with VenToy installed as a bootable internal drive with ISOs of Android OS and Windows 10, among others.
While I do depend on Manjaro the most, my colleges think Arch Linux is the way. In my experience Arch Linux community tends to be full of the power elitists. I prefer to ask most of my technical questions in the Ububtu and/or Debian community forums, unless they are Arch specific. Those are more user friendly people there. 
Since the laucher is actually a Chromium based browser, I came up with this shortcut to expedite my launch. Where your Wine executable reads “eve-online.exe --product=eve-online” I added after that the Chromium command line --disable-gpu
This disables GPU hardware acceleration for the browser. Here is a long list of other commands that may or may not be of use. Be gentle and don’t break it.
Have a happy new year!
Thank you for mentioning it…i don’t even have “–product=eve-online” in my custom startup command…works as usual, but i have seen it in the parameter line on the EVE icon. Seems they changed it at some point…i wonder what it actually does.
“–disable-gpu” should be covered by the option to not have the launcher accelerated ticked in the launcher options menu. So i wonder how this would expedite your launch beyond having the option unticked?