Glorious Alpha Two Testers!
Alpha Two Phase II testing is currently taking place 5+ days each week. More information about testing schedule can be found here
If you have Alpha Two, you can download the game launcher here, and we encourage you to join us on our Official Discord Server for the most up to date testing news.
Alpha Two Phase II testing is currently taking place 5+ days each week. More information about testing schedule can be found here
If you have Alpha Two, you can download the game launcher here, and we encourage you to join us on our Official Discord Server for the most up to date testing news.
Comments
```
warning: WINE is $HOME/.local/share/lutris/runners/wine/UMU-Proton-9.0-3.2/bin/wine, which is neither on the path nor an executable file
```
Again, please get rid of debian based distros!
Sometime soon I'll post the process I followed for Ubuntu 24 in case you want to link it in the OP. There are lots of folks who game on Ubuntu without any issues and also use it as a daily driver, so moving OS just to play Ashes is a non-starter for some folks. Especially if we can get it to work on Ubuntu, which it appears we can
I dont know how I could find out what the reason for this is. Does the game create any logfiles where I could check what happens in the moment when my PC crashes?
# Go to https://github.com/Open-Wine-Components/umu-proton/releases and get the latest .tar.gz release. I used 9.0-3.2 . Follow the installation instructions on that github; the tl;dr is: tar -zxf UMU-Proton-9.0-3.2.tar.gz -C ~/.steam/root/compatibilitytools.d/ sudo apt install flatpak sudo flatpak install flathub net.lutris.Lutris # install Flatseal, which is used to manage flatpak permissions sudo flatpak install flathub com.github.tchx84.Flatseal flatpak run com.github.tchx84.Flatseal # In Flatseal: select Lutris on the left. scroll down to the Filesystem section. Add the directory where you'll configure Lutris to store games. I used /games. Then exit Flatseal flatpak run net.lutris.Lutris # in Lutris: hamburger menu at top right -> preferences -> storage -> change the storage path to /games or whatever path you added in flatseal. # in Lutris: hamburger menu at top right -> preferences -> runners -> wine, click gear icon -> set wine version to UMU-Proton-9.0.3.2 # Click + in Lutris, "search the Lutris website for installers", input "ashes of creation", install, Alpha 2, next, etc. # Go thru installation process. When you have the tickbox choice to install Easy AntiCheat, install that and ensure the other 2 are unselected (for me they were already unselected) # After the launcher installs, run the launcher. The launcher will update the game. Leave the launcher open. The launcher is the window that has a blue button "play game" (don't click that) # In steam: click + at the bottom left, add a non-steam game. Add the AOCClient.exe that got installed. For me it was "/games/ashes-of-creation/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/AOCClient.exe" # Set compatibility tool to a proton-GE, UMU, or Proton Experimental. # Set launch options to: eval $(%command% LauncherTetherPort=$(ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0) # While the launcher is open (spawned from Lutris), launch the game you added on steam.I am also using NixOS and I had to just hard code the port into Steam launcher options. I'm not sure why it won't evaluate for us.
Any ideas on next steps?
Ahh, didn't see that, thanks... been running Linux since '93 and I see people saying "YOU HAVE TO DITCH DEBIAN-BASED DISTROS!" which can't possibly be correct... so I was looking for any details and then prove them wrong. :-) Thanks for the notes, I'll check it out.
Here is my explanation of why one should avoid Debian-based distros.
Tutorial is in the first post.
Same issue here, have been able to play for a week until I got blocked as well, I too have opened up a support ticket in hopes of resolving this for all of us.
You are being advised, when creating a support ticket, that an answer from the support staff will most likely be delayed due to the holidays. I hope to have the ticket get processed in the coming week.
I have been running it on Arch Linux through Lutris and had been working quite well. Not very many crashes. There are a lot of graphical issues though with shaders most likely not being processed and compiled quite right, things will look different to you than to Windows users, do make sure to cross reference with someone on Windows before submitting graphical bug reports.
I started out with not having any water in the game until it managed to compile it the right way a day after, along with hair for example just poking out of helmets at all times.
Edit:
I seem to have fixed it. I can't say for 100% what the issue was, as I have tried a few things, my guess it, that WebView2 attempted to update, or at least the launcher tried to do so and screwed it up for it to work under WINE.
I removed and reinstalled WebView2 and manually applied the regedit override as is explained on page 1 and got it working again.
I was getting this same issue using the Lutris install. I set it up with Bottles and was able to connect without an issue. I'm guessing there's something in the Lutris config that bothers CloudFlare and has them implement an IP block. For those of you affected like this (I nuked my Lutris install, sadly, without checking), check if the headers being sent are the same and if there is a difference I would also open an issue in the Lutris github.
Do you use the latest version of Lutris, because I always use the Intrepid Studios Launcher with the latest version (currently 0.5.18) and have never had such a problem.
Yes, I was using 0.5.18-2 AUR package in vanilla Arch. I will likely play with that and the flatpak again this weekend if there's enough time.
I have created a yaml file for installing the Intrepid Studio Launcher on Lutris on my own, so if you want you can give it a try. The file is mostly the same like the one on the lutris page but there are a few small differences. You can find the file here. I honestly doubt that this fixes the issue but its at least worth a try.
Edit: I finally figured it out. On the system that didn't work, I had ipv6 disabled as a kernel parameter in /etc/default/grub. I re-enabled ipv6 and viola. I wonder why this game needs ipv6..?
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.
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."
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.
Arch and Ubuntu have easy ways of installing the latest Nvidia drivers, as stated above.
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.
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.
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.
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.
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.
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.
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.
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 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.)
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.
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.
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/
(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.