Linux Tips, Tweaks and Troubleshooting Thread

Here I want to collect all good informations about linux support from community members. Please keep his thread clean and only comment your informations, tips or workarounds. Together we will rise up and make our main game ready for linux in the future.

Complete Tutorial: How to Get Ashes of Creation Running

For gaming, Fedora or Arch-based distros are recommended, as they tend to offer better performance and compatibility. Debian-based distros should be avoided for gaming due to potential issues.

Step 1: Install Faugus Launcher

Based on experience, I use the Faugus Launcher here. Why, you ask? Well, we kept trying Bottles and Lutris, but the development of both tools has practically come to a standstill. Due to their spaghetti code, errors arise that are becoming increasingly complex and bizarre. That's why I chose the Faugus Launcher — it's simply a GUI for the Proton prefixes and is very lightweight. This reduces potential sources of errors to a minimum, and as the saying goes: sometimes, less is more.

https://github.com/Faugus/faugus-launcher

Step 2: Install the Launcher for Ashes of Creation

Download the Intrepid Launcher from the official Ashes of Creation website.

Select GE-Proton latest in Faugus. Or to prevent breakage after updates use a fixed Version like GE-Proton10-15.

During installation, ensure you select everything in the checkbox like EAC, Webview2 and C++ Redistributable

Important: After installation, do not launch the launcher immediately. Instead, click Finish and uncheck the option to launch the launcher.

Step 3: Select the right EXE for Faugus

After installing the launcher and closing it afterwards, it might happen that the wrong EXE file was selected under "Game Path" in Faugus. Simply change this to IntrepidLauncher.exe.

Step 4: Set Up Steam for Launching

Open Steam and click on Add a Non-Steam Game.

Find and select AOCClient.exe from your Faugus Launcher prefix installation folder.

In the Steam Launch Options, add the following code:

eval $(%command% LauncherTetherPort=$(ss -ulpn | awk '/wineserv/ {split($4, a, ":"); print a[2]}') -USEEOS=0 -DXVK_FRAME_RATE=60)

I included a framerate limit in this command. If you don’t want that, you need to remove -DXVK_FRAME_RATE=60.

Also enable Proton Hotfix for the AOCClient.exe. You can use ProtonPlus to add Proton-GE latest to your Steam Client, if you want to try other Proton runner.

This will allow Steam to launch the game alongside the running launcher.

Step 5: Play the Game

Now, with the launcher open in Faugus Launcher and Steam configured, simply click Play in Steam. Ashes of Creation should launch successfully, and you can start playing!

Common Issues

If you change the Proton version in your Ashes prefix or Proton receives an update, WebView2 may break, causing the login form to appear black again. Here's how to fix it:

Open Winetricks in the Faugus Launcher settings

Then you choose the Standard Prefix

Choose the uninstaller

Select Webview2 runtime and press on change

Then you click on repair

Then it should reinstall and works afterwards

If you have issues with Nvidia cards out of memory try Proton Hotfix as runner in Steam.

Find more posts tagged with

Staff

Comments

ashesofbutt

mercfredis wrote: »

ashesofbutt wrote: »

mercfredis, see my Ubuntu instructions a few posts up. I'd imagine they also work for Debian.

OK so I am on ubuntu 24.04 as well... I didn't have to do the flatpak stuff. I just got the UMU-Proton package and made sure Lutris was using it for the Ashes installer. Worked pretty well. Thanks for the write-up!

You're using apt's version of Lutris? How exactly did you get UMU-proton to show up in there? I couldn't get it to show up there, and that's why I resorted to flatpak

mercfredis

ashesofbutt wrote: »

mercfredis wrote: »

ashesofbutt wrote: »

mercfredis, see my Ubuntu instructions a few posts up. I'd imagine they also work for Debian.

OK so I am on ubuntu 24.04 as well... I didn't have to do the flatpak stuff. I just got the UMU-Proton package and made sure Lutris was using it for the Ashes installer. Worked pretty well. Thanks for the write-up!

You're using apt's version of Lutris? How exactly did you get UMU-proton to show up in there? I couldn't get it to show up there, and that's why I resorted to flatpak

I use the up to date Lutris 0.5.18 .deb file on github. Extracting the UMU-proton into steam's compatibility directory, it shows up.

Azalroth

mercfredis wrote: »

Azalroth wrote: »

Even though you're keeping your system up-to-date with the Kali and Debian repositories, it’s important to note that Kali, for example, is still using Kernel 6.8.0, whereas Fedora is running Kernel 6.11.8. This means Kali is at least 3 major versions and over 15 kernel versions behind Fedora. This can have a significant impact on performance and compatibility, especially with newer games or specific graphics drivers.

The appreciable difference between 6.8.0 and 6.11.8 will be negligible when it comes to playing Windows games via Wine/Proton/dxvk/etc. Kali of course is an absurd distro to run games on... doesn't mean it can't do it, but will require a lot more work, compared to a general purpose distro like Ubuntu/Fedora/Arch/etc. Debian is also usually hopelessly out of date and also will requite more work.

At any rate, the most important pieces will be graphics drivers and Wine/Proton stack. I have no idea about AMD GPUs, but my Ubuntu distro, despite utilizing kernel 6.8.0, has packages available for the latest binary GPU blobs, and the most up to date Wine/Proton packages. In my case, I would expect very little difference in games performance.

Azalroth wrote: »

I really doubt it’s a Wine issue and think it’s more likely related to the distro itself. If you look through forum posts, it’s often users with Ubuntu, Linux Mint, or other niche distros that report these kinds of problems. Fedora, on the other hand, provides a more stable "out-of-the-box" experience with the latest software versions and a newer kernel, which can make a difference, especially for gaming and using Wine or Proton.

Fedora does, in general, include more up to date upstream packages, but again, most distros will have facilities for installing the latest GPU drivers and Wine/proton packages... Lutris itself provides for the latter. If running 6.8.0 means the newest AMD drivers cannot be installed, that may be an issue.

ProtonDB is probably the largest centralized repository of Linux users self-reporting success or failure in getting a given Steam game to run on their system... I see way more "failures" on Fedora than Arch and Ubuntu. This isn't a real metric of any kind, as many times this is a "skill issue", and not due to the distribution. Just because a bunch of newbies run distro XYZ and collectively have a hard time getting things to work, doesn't mean that distro is "bad for gaming." Conversely, just because some distro happens, by dumb luck, to make getting a certain thing work easy, does not mean other distros can't work, or are "bad for gaming."

Azalroth wrote: »

Another factor to consider is the desktop environment. Fedora uses GNOME, which is one of the most polished and stable desktop environments out there. KDE is also a great choice, but for a productive and gaming-oriented setup, environments like XFCE (which Kali uses) are less optimized for modern software and games. So, if you're looking for a stable, easy-to-use, and well-supported environment for gaming and apps, I’d recommend trying Fedora before Arch. Arch is fantastic for experienced users, but it can require more manual setup.

This is nonsense. Desktop environments do not need to be "optimized" for modern software or games. The only possible feature that would have an impact is compositing, which is actually a negative. XFCE is much lighter weight than GNOME or KDE, which would provide more resources (CPU/Ram) for the game and its associated processes.

And you suggesting Fedora is especially confusing, as Fedora 41 ships with Wayland, and requires the user to install X by hand and do some systems twiddling to switch to it. Nvidia on Wayland and gaming do not really mix yet. The latest stable Ubuntu still uses Xorg, so would be more appropriate.

Azalroth wrote: »

Since I’m using the same processor (i9900k) and Nvidia GPU as you, I haven’t had any issues with Wine, so I’d rule out a Wine-specific bug and point to distro configuration being the main cause.

Arch and Ubuntu have easy ways of installing the latest Nvidia drivers, as stated above.

mercfredis, I appreciate your insights, but there are some important points you might want to reconsider based on more recent developments.

1. Kernel Version and Gaming Performance:
While it is true that many distros, including Fedora, can offer facilities to install the latest GPU drivers and Wine/Proton packages, you're overlooking the fact that kernel version does impact compatibility, especially with newer hardware and software. The difference between kernel 6.8.0 and 6.11.8 may seem small at first glance, but when dealing with modern games and cutting-edge hardware, those extra kernel versions contain crucial improvements, particularly in hardware support, performance, and bug fixes. Fedora’s more recent kernel ensures better out-of-the-box support for newer graphics cards and gaming technologies.

2. Desktop Environments and Gaming Performance:
You mentioned that desktop environments don’t need to be "optimized" for modern software and games, but this is a bit misleading. While XFCE is lightweight, it lacks optimizations in areas like window compositing and modern graphical features that are important for gaming. GNOME and KDE, which are more feature-rich, are much better suited for supporting technologies like Wayland, VRR (Variable Refresh Rate), and Vulkan, all of which can enhance the gaming experience. Fedora, for instance, provides GNOME by default, which offers a modern and polished environment that integrates well with newer display technologies, making it a better choice for users aiming for a seamless gaming setup.

3. Wayland and Nvidia Support:
You mentioned that Wayland and Nvidia don't mix well, but this is no longer entirely accurate. Nvidia has made substantial progress with Wayland support, particularly with more recent drivers. As of now, Nvidia drivers on Wayland support crucial gaming features like VRR, and Explicit Sync, which prevents issues like screen tearing and ensures smoother gameplay. The Explicit Sync support specifically allows for improved synchronization between the GPU and display, something essential for a fluid gaming experience. Fedora’s default use of Wayland is increasingly viable for gaming, as Nvidia's ongoing improvements ensure that these features work reliably. While it’s true that Fedora uses Wayland by default, the performance and stability improvements in recent months, especially regarding Nvidia’s support, make Wayland a much more viable option for gaming than it was in the past.

4. Wayland vs. Xorg:
It's important to point out that Wayland is, in fact, a significant improvement over Xorg in several areas, particularly for modern hardware and gaming. Wayland offers better performance, lower latency, and a more secure architecture than Xorg. One of its key advantages is its ability to provide native VRR (Variable Refresh Rate) support, something Xorg struggles with. Additionally, Wayland enables smoother and more consistent rendering, as it eliminates much of the legacy overhead and inefficiencies that come with Xorg's older design. For gamers, Wayland provides a more seamless experience, especially with Nvidia hardware, as it reduces screen tearing and latency issues that are common in Xorg. In short, for modern gaming and desktop usage, Wayland is the superior option.

5. ProtonDB and Distros:
While ProtonDB is a useful resource, it’s important to remember that user-reported success and failure can often be influenced by the user’s skill level and system configuration. The issues you mention on Fedora may not necessarily be the fault of the distribution itself, but rather the result of user errors or the specific setup being used. Fedora is a rolling-release distro that prioritizes up-to-date software, which means users can encounter edge-case issues, but at the same time, they benefit from cutting-edge features and the latest software improvements, including support for the latest gaming technologies.

In summary, while your points about the flexibility of distros like Ubuntu and Arch for gaming are valid, it's important to acknowledge the advancements in Wayland and Nvidia driver support, especially when it comes to gaming features like VRR and Explicit Sync. Fedora, with its more modern kernel, GNOME desktop environment, and better support for these technologies, can actually provide a superior gaming experience in many cases. Dismissing Wayland or assuming it’s unsuitable for Nvidia users is an outdated perspective, especially with the ongoing improvements in Nvidia's Wayland support.

mercfredis

Azalroth wrote: »

mercfredis, I appreciate your insights, but there are some important points you might want to reconsider based on more recent developments.

Impressive, I've never seen a post so clearly written by ChatGPT before. Your post is excessively verbose, but contains almost no detail or rationale for what you're saying, but makes several nonsensical claims.

1. Kernel Version and Gaming Performance:

While it is true that many distros, including Fedora, can offer facilities to install the latest GPU drivers and Wine/Proton packages, you're overlooking the fact that kernel version does impact compatibility, especially with newer hardware and software. The difference between kernel 6.8.0 and 6.11.8 may seem small at first glance, but when dealing with modern games and cutting-edge hardware, those extra kernel versions contain crucial improvements, particularly in hardware support, performance, and bug fixes. Fedora’s more recent kernel ensures better out-of-the-box support for newer graphics cards and gaming technologies.

On AMD hardware this may be true, I don't know the state of kernel-level AMD drivers. It's possible that many large, well run distributions (like Ubuntu) have back-ported AMD drivers that are more up to date. For Nvidia, your statement is just pure false. The binary blobs most people use are distributed separately from the kernel, and can be configured against any recent kernel. This section of your book-length post is the least egregious. I know you can't tell me what differences exist between 6.8.0 and 6.11.8 for "modern games and cutting-edge hardware", so I won't ask.

2. Desktop Environments and Gaming Performance:
You mentioned that desktop environments don’t need to be "optimized" for modern software and games, but this is a bit misleading. While XFCE is lightweight, it lacks optimizations in areas like window compositing and modern graphical features that are important for gaming. GNOME and KDE, which are more feature-rich, are much better suited for supporting technologies like Wayland, VRR (Variable Refresh Rate), and Vulkan, all of which can enhance the gaming experience. Fedora, for instance, provides GNOME by default, which offers a modern and polished environment that integrates well with newer display technologies, making it a better choice for users aiming for a seamless gaming setup.

Again, complete nonsense. Do you even know what window compositing does? It actually hurts game performance, as it introduces additional screen buffering for fancy window effects. There is absolutely no reason one would need "window ccompositing" for gaming. It's not an "optimization." It's for fancy/smooth window effects. That's it. (XFCE also has a compositor, and neither of us are familiar enough to compare the compositors for different window managers.)

Wayland on Nvidia is impossible for gaming. Some people may run some very select games on it, but it is unstable and not appropriate for a gaming rig, period.

Vulkan is separate from your desktop environment. It is a set of libraries and support in the graphics driver. I'm telling you, whatever ChatGPT is spitting out here, it's not helping your case. And what "newer display technologies" are you saying GNOME "integrates with"? And GNOME being polished, that is completely subjective and again, nothing to do with running video games on your computer.

This whole thing sounds like a marketing brochure written by someone who has no idea what's going on underneath the hood.

3. Wayland and Nvidia Support:
You mentioned that Wayland and Nvidia don't mix well, but this is no longer entirely accurate. Nvidia has made substantial progress with Wayland support, particularly with more recent drivers. As of now, Nvidia drivers on Wayland support crucial gaming features like VRR, and Explicit Sync, which prevents issues like screen tearing and ensures smoother gameplay. The Explicit Sync support specifically allows for improved synchronization between the GPU and display, something essential for a fluid gaming experience. Fedora’s default use of Wayland is increasingly viable for gaming, as Nvidia's ongoing improvements ensure that these features work reliably. While it’s true that Fedora uses Wayland by default, the performance and stability improvements in recent months, especially regarding Nvidia’s support, make Wayland a much more viable option for gaming than it was in the past.

Do you have an Nvidia graphics card? That's all I want to know. Wayland has nothing to do with VRR, I use G-SYNC with X11 just fine. You seem to be under the impression that newer=better. Nvidia+wayland and gaming do not mix. When you suggest this to Linux users, you are setting them up for failure, and they may not have the technical proficiency to switch back to X11, which is what they want right now.

4. Wayland vs. Xorg:
It's important to point out that Wayland is, in fact, a significant improvement over Xorg in several areas, particularly for modern hardware and gaming. Wayland offers better performance, lower latency, and a more secure architecture than Xorg. One of its key advantages is its ability to provide native VRR (Variable Refresh Rate) support, something Xorg struggles with. Additionally, Wayland enables smoother and more consistent rendering, as it eliminates much of the legacy overhead and inefficiencies that come with Xorg's older design. For gamers, Wayland provides a more seamless experience, especially with Nvidia hardware, as it reduces screen tearing and latency issues that are common in Xorg. In short, for modern gaming and desktop usage, Wayland is the superior option.

Wayland has many benefits over X11. However it is not ready yet for many applications, especially using Nvidia hardware. There is a difference between something being theoretically "better" in design, and being ready as a drop-in replacement for a previous technology.

5. ProtonDB and Distros:
The issues you mention on Fedora may not necessarily be the fault of the distribution itself, but rather the result of user errors or the specific setup being used.

That's exactly what I said, "This isn't a real metric of any kind, as many times this is a "skill issue", and not due to the distribution."

Fedora is a rolling-release distro that prioritizes up-to-date software, which means users can encounter edge-case issues, but at the same time, they benefit from cutting-edge features and the latest software improvements, including support for the latest gaming technologies.

Fedora is not rolling release. Arch is rolling release, Fedora cannot do so completely because it is the "testing ground" for RHEL. It is more up to date, but always using the most up to date software is not always a good thing. Rolling releases mean things break more often, because the software is not audited as thoroughly before being updated, and upstream releases may introduce incompatibilities. (talking mostly of Arch here.)

In summary, while your points about the flexibility of distros like Ubuntu and Arch for gaming are valid, it's important to acknowledge the advancements in Wayland and Nvidia driver support, especially when it comes to gaming features like VRR and Explicit Sync. Fedora, with its more modern kernel, GNOME desktop environment, and better support for these technologies, can actually provide a superior gaming experience in many cases. Dismissing Wayland or assuming it’s unsuitable for Nvidia users is an outdated perspective, especially with the ongoing improvements in Nvidia's Wayland support.

Your "advice" and ChatGPT-written summary here sounds like a marketing brochure. You keep talking about cutting edge technologies, "superior gaming experience"... but neither GNOME, or Wayland, has any benefit when it comes to gaming, and for many, it is just not ready yet. It's very aggravating to have someone like yourself, who has a setup that works for them, and then going around telling everyone else what the best software is to use.

Azalroth wrote: »

Use Lutris flatpak. With the flatpak everything is bundled.

Again, please get rid of debian based distros!

Remember this? This is symptomatic. You told eeeeeverybody to stop using "debian based distros", because of your bias. I and others are running Ashes of Creation just fine in Ubuntu... just because you have a solution that works, doesn't mean everything else doesn't work.

Azalroth

mercfredis wrote: »

Impressive, I've never seen a post so clearly written by ChatGPT before. Your post is excessively verbose, but contains almost no detail or rationale for what you're saying, but makes several nonsensical claims.

Nope, I just want to save energy by arguing with a boomer over the internet who is not even grateful that this thread was created.

PS: On the subject of kernel and performance, just google NTSYNC to take one of the latest examples to broaden your limited horizons.

https://www.gamingonlinux.com/2025/01/ntsync-driver-for-improving-windows-games-on-linux-with-wine-proton-should-finally-land-in-linux-kernel-614/

ashesofbutt

Hi guys, I appreciate the big-brain distro war battle, but could we keep this thread on the topic of getting AOC to work on Linux and associated troubleshooting?

We're all on the same side here.

Bittah

Good lord, some of these comments. Either way, I've been having issues with the game every time there is a patch. Anyone else running into this? I have to re-install each test phase and troubleshoot it

notalent

Does anyone get this error after the last patch?

(sorry for the font)

I was using bottles without issue before last update to 0.3.275.39608 and my performance was strangely better on linux than on windows.

Alpha_Barrier

notalent wrote: »

Does anyone get this error after the last patch?

(sorry for the font)

I was using bottles without issue before last update to 0.3.275.39608 and my performance was strangely better on linux than on windows.

Are you switching between Wired and Wireless LAN? Or perhaps using a VPN?

Alpha_Barrier

Well good news and bad news for me!

I always got errors before getting to the point of the launcher actually installing AoC, but today I finally got it to install!

Sadly, after adding it to Steam and forcing Proton Experimental, I get this "Settings.json not found", any ideas?

(note: I did have the "Proton EAC Runtime" installed in Steam, I tried removing it and that did not seem to make a difference)

(edit: can confirm, Settings.json exists in the AshesOfCreation>PROD>EasyAntiCheat directory)

(edit2: playing around further, I get the same error regardless of whether the AOC launcher is running or not, so this perhaps means that it is erroring before it even evaluates launch options or tries to launch the game? Something wrong with Steam itself?

I also thought perhaps it was a permissions issue, like Steam could not get access to the Settings.json file, but from what I can tell, "others" can "Access Files" all the way thru the directory path, i.e., ~/.var/app/com.usebottles.bottles/data/bottles/bottles/Ashes-Beta-2/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/EasyAntiCheat/)

Azalroth

Azalroth wrote: »
Bittah wrote: »

Howdy folks! I've been getting this issue now for this weekend and I've tried reinstalling and repairing to no avail.I've looked through the file structure and I am able to locate the "Settings.json" file, so I'm not sure what the issue could be. Anyone got any clues? I'm running arch/KDE/x11
Error from launcher:

Last few lines of bottles instance:

Settings.json error is EAC related. Try installing EAC again manually in Bottles with the
EasyAntiCheat_EOS_Setup.exe
in this Folder
/home/user/.var/app/com.usebottles.bottles/data/bottles/bottles/Ashes-of-Creation/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/EasyAntiCheat/

@Alpha_Barrier Look here and try this

Funkychicken

Alpha_Barrier wrote: »

Well good news and bad news for me!

I always got errors before getting to the point of the launcher actually installing AoC, but today I finally got it to install!

Sadly, after adding it to Steam and forcing Proton Experimental, I get this "Settings.json not found", any ideas?

(note: I did have the "Proton EAC Runtime" installed in Steam, I tried removing it and that did not seem to make a difference)

(edit: can confirm, Settings.json exists in the AshesOfCreation>PROD>EasyAntiCheat directory)

(edit2: playing around further, I get the same error regardless of whether the AOC launcher is running or not, so this perhaps means that it is erroring before it even evaluates launch options or tries to launch the game? Something wrong with Steam itself?

I also thought perhaps it was a permissions issue, like Steam could not get access to the Settings.json file, but from what I can tell, "others" can "Access Files" all the way thru the directory path, i.e., ~/.var/app/com.usebottles.bottles/data/bottles/bottles/Ashes-Beta-2/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/EasyAntiCheat/)

Assuming that steam has been installed via flatpak then try a reinstall of EAC. Check the permissions on the directory. On mine group and user have access to it. group = rw and user = r

Funkychicken

Hello I want to re-itterate what works for me for linux:

Hardware Setup
Intel i9 9900k
DDR4 4000 16GB
RTX 3080 10GB
PCI3.0 M.2 SSD
Custom loop cooling with x3 radiators and GPU/CPU waterblocks

System Setup
Fresh Nobara 41 Install
Nvidia Drivers
Flatpak
Limited system applications. Everything is installed through flatpak.
Wayland and Xorg switcher
Everything system wide default.

Software setup
Flatpaks: Bottles, Steam
Configuration, as per page 1 of this thread. But in a nutshell - make sure you can see the UDP port, make sure you have EAC through bottles installed and VC2022. Setup AOCCLient in steam and run in proton experimental.

Video Installation
Video running ashes

What I tried previously
Kali
Ubuntu
Arch
Fedora Core

Applications which were unsuccessful
Lutris
Wine native
PlayonLinux

None of these worked, with varying degrees of success running from, launcher would not work to game would crash 10 seconds in. With a variety of error messages by using these applications, this is when I gave up and switched to Nobara.

Wayland plays a lot better on gaming now - to the point where I can play the game for hours without issue. But I have noticed that there is the occasional issue when alt-tabbing - especially if you want to alt-tab and load another application or 2, then go back to the game. But if you load all of the apps up before you load the game, then it is fine.

Xorg doesn't seem to have the same issue here and works a lot better.

Alpha_Barrier

Thanks @Funkychicken and @Azalroth , you guys are great and it's nice to have community members like you and others willing to be so helpful.

Once the realms come back online I will see if this works.

@Azalroth - I did run the EAC executable from bottles (using the "Run Executable..." button), not sure it did anything as there is no splash screen or progress bar, but I hope that is what you meant by reinstalling it inside the bottle, if there is a better way to reinstall EAC, I am all ears.

@Funkychicken - I am on ZorinOS, I have had luck in the past running most games that others can run on Unix OSs, especially debian-based. I have never needed to run Wayland or Xorg Switcher, but curious if you think using either of those would bring some benefit to gaming or, if everything runs relatively well without them, just ignore them? Keep it simple? One example is Path of Exiles 2 beta via Steam/Proton Experimental, it ran and was playable, but really never reached 100-140 FPS and tended to downscale the graphics quality alot when things got busy ingame. My system is no slouch, but not top-of-the-line. Would Wayland or Xorg possibly help in situations like this? Seeking better performance?

Funkychicken

Alpha_Barrier wrote: »

Thanks @Funkychicken and @Azalroth , you guys are great and it's nice to have community members like you and others willing to be so helpful.

Once the realms come back online I will see if this works.

@Azalroth - I did run the EAC executable from bottles (using the "Run Executable..." button), not sure it did anything as there is no splash screen or progress bar, but I hope that is what you meant by reinstalling it inside the bottle, if there is a better way to reinstall EAC, I am all ears.

@Funkychicken - I am on ZorinOS, I have had luck in the past running most games that others can run on Unix OSs, especially debian-based. I have never needed to run Wayland or Xorg Switcher, but curious if you think using either of those would bring some benefit to gaming or, if everything runs relatively well without them, just ignore them? Keep it simple? One example is Path of Exiles 2 beta via Steam/Proton Experimental, it ran and was playable, but really never reached 100-140 FPS and tended to downscale the graphics quality alot when things got busy ingame. My system is no slouch, but not top-of-the-line. Would Wayland or Xorg possibly help in situations like this? Seeking better performance?

Well I have noticed that although wayland does bring some benefits, some things don't work on it as well as they do on xorg - for example the game client for Ashes show up black, and you have to guess where to click to login. On xorg, everything shows up and works better.

If you install xorg, you can install the switcher that lets you choose which window manager. I use both kde Plasma but I also have xfce because I like the lighweightness of it all. So sometimes when plasma crashes, I switch to xfce to see if the same happens on that using xorg and most of the time it is more stable. I notice this mainly when using alt-tab. Sometimes the wineserver crashes and processes are left hanging. This only happens rarely.

Funkychicken

@Alpha_Barrier Another things which may help is installing xfce. Xfce uses lightdm or xfwm4 on the new version. If you install this and you configure the system to login then you can switch between plasma and xfwm4 or lightdm (whichever you choose to install when you configure xfwm). What I have noticed is that on wayland, the window renders only render black on the form when you log in. This is true for webview2 so both the web page and the form fields will not render correctly. If you move to xfwm4, then this will work ok and then you can see the forms and the username you are entering. On wayland the form will still work but you will not be able to see what you are clicking. You may click the login screen or you may click a new account registration. What is good to have is a window of the login form next to the wayland window so you know where you are clicking.

Azalroth

To shed some light on the topic, because my previous posts may have been too long or overlooked:

Regarding Xorg and Wayland. Wayland is the spiritual successor to Xorg. In principle, Wayland is superior to Xorg in many aspects (e.g., Wayland provides better security, smoother graphics, and less input lag compared to Xorg). It is important to keep in mind that not every desktop environment, like XFCE for example, supports Wayland. This means that the desktop environment automatically selects the default display server protocol. Most are still on X11 because it causes the least amount of problems. In general, GNOME and KDE are the front-runners when it comes to fast adoption, and they fully support Wayland. Nevertheless, there are distributions that, even when using GNOME or KDE, force X11 because it still maintains the familiar stability. Modern distributions that like to implement new technologies as soon as they are usable, like Arch Linux or Fedora, force Wayland. Of course, with Arch, you can choose everything before installation. Taking Fedora as an example, since Fedora 41, only Wayland is available as the default.

However, you can still switch to Xorg in all of them. What many forget is that good distributions also run Xwayland in parallel (Xwayland is a compatibility layer that allows X11 applications to run on Wayland). In this case, you’re always running Wayland, and applications that don’t yet support Wayland fall back to Xwayland. It's essentially a middle layer that translates between Wayland and Xorg to allow the applications to run. This means that regular Linux users can now take the step towards Wayland, and I would actually recommend it.

There are still a few growing pains, like Alt-Tabbing, but this has been fixed in GNOME, for example. Ultimately, it’s up to each individual, and that’s the beauty of Linux. I’m someone who likes to adopt new technologies quickly, which is why I use a distro that suits my needs for everyday use, which in this case is Fedora. Arch is for enthusiasts and could be dangerous for beginners who don’t know what they’re doing. For example, many don’t know that Arch doesn’t even come with a firewall installed, and you have to manually install it. Fedora, on the other hand, comes with many security features like SELinux and firewalld by default, and just gives me fewer headaches. I hope I could shed some light on this topic.

By the way, since Wine 10, Wayland is now natively supported. This might also fix the black screens that occasionally appear in software using old libraries, like our Ashes Launcher.

https://www.phoronix.com/news/Wine-10.0-Released

Alpha_Barrier

Grr, still getting the Settings.json not found error.

Alpha_Barrier

Also ran CMD in the Bottle and tried to verify/install/repair the EAC install there, doesn't seem to have worked or made any difference.

Also tried moving the Settings.json file into the "Start In" folder that Steam uses, also no change.

Azalroth

Alpha_Barrier wrote: »

Grr, still getting the Settings.json not found error.

Is your Steam a flatpak install? If yes, the last step is to give Steam permissions.

Download Flatseal Flatpak
Select Steam
Scroll down until filesystem
Check the box filesystem=host
restart Steam

Child Item