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
@Alpha_Barrier Look here and try this
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
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.
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.
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
Also tried moving the Settings.json file into the "Start In" folder that Steam uses, also no change.
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
Thank you, however Steam will not launch if that is selected. I turned it off and Steam launched again.
Maybe I should try installing the Non-flatpak version of Steam?
(edit) Yeah, non-flatpak Steam worked, I'm ingame for the first time!
So I got to about lvl 7, no issues, finally wandered up to Winstead and my GPU crashed, now every time I load into the game world, after character select, it crashes. Even when loading a new character at starting area.
Sound continues, but monitor goes to sleep.
I have to hard reboot to recover.
Tried changing various graphics settings from character select screen, but nothing changed the behavior.
I have seen others have similar issues in this thread, but has anyone found any possible fixes for this or have any troubleshooting ideas?
Running on ZorinOS with an AMD 6700XT, Risen 5 3600.
Thanks to @Azalroth @Funkychicken @Guillemets @icedown & Everyone else!
FunkychickenTV Youtube: https://youtube.com/watch?v=ecWbxoojQsI
Computer Setup
OS: Fedora Linux 41 (KDE Plasma) x86_64
Display (ROG PG348Q): 3440x1440 @ 60 Hz in 34"
DE: KDE Plasma 6.2.5
WM: KWin (Wayland)
CPU: AMD Ryzen 7 9700X (16) @ 5.58 GHz
GPU 1: AMD Radeon RX 7600 XT
Memory: 30.45 GiB
Software setup
Flatpaks: Bottles, Flatseal, Steam
What steps to reproduce this?
- Install Bottles, Flatseal, & Steam
- Download Intrepid Installer from Website
Bottles
1. Create new bottles
- Name it Anything (Ashes), Pick Gaming Optimized
- Change Bottle Directory to Home Folder (Documents Folder) or External Drive
2. Go to Options, Dependencies and install vcredist2022 and webview2 ONLY
3. Then go to Tools, Legacy Wine Tools and click on configuration
- In Applications select msedgewebview2.exe and change Windows Version 8.1 to 7
- Now select the library's tab and in New override for library: add urlmon, click add then apply
4. Run Executable for Intrepid Launcher and select Easy Anti-Cheat Service Only then finish install
5. If you get black screen, close launcher
- Go to Bottle Directory, (Documents/Ashes/drive_c/Program Files/Intrepid Studios/Launcher/)
- Create file named dxvk.conf if you don't have
- Add d3d9.shaderModel = 1 and save
6. Relaunch launcher, Click Login. login and download game
7. After game is installed in bottles add Shortcut to AOCClient.exe
- location: Documents/Ashes/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/
Flatseal
- Select Bottles & Steam and in File system secion add file path to game install
- You can add Environment variables for netstat here but I never got it to work
- eval $(%command% LauncherTetherPort=PORT -NOSPLASH -USEEOS=0)
- eval $(%command% LauncherTetherPort=$(netstat -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0)
Steam
- Add no steam game and select the AOCClient.eve
- In Properties add launch options eval $(%command% LauncherTetherPort=REPLACEWITHPORT -NOSPLASH -USEEOS=0)
- In Compatibility select Proton Experimental
Getting Game to Run
- Start Launcher and Login from bottles
- In terminal type netstat -ulpn | grep wineserv to get port number
- netstat -ulpn | grep wineserv
- In steam properties add portnumber from terminal
- Click Play, say no to driver and Play Game
PREREQUISITES:
1. The latest tarball from https://github.com/Open-Wine-Components/umu-proton/releases. As of 2/3/25, this is UMU-Proton-9.0-3.2.tar.gz
2. Recent Lutris. If Fedora, you probably have this (0.5.18.) If Ubuntu, grab the latest tarball from Lutris github at https://github.com/lutris/lutris/releases
PROCEDURE
1. Extract UMU-Proton-9.0-3.2.tar.gz into ~/.steam/steam/compatibilitytools.d so that Lutris will see it as a runner.
2. Run Lutris -> Settings menu -> Preferences -> Runners -> Wine -> Choose UMU-Proton for Wine version.
3. At Lutris main window, click + in top left to add game.
4. Choose "Search the Lutris website for installers", search for Ashes of Creation, choose to install.
5. Go through installation process. When you have the tickbox choice to install Easy AntiCheat, install that and ensure the other 2 are unselected.
6. 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.)
7. Add new non-Steam game to Steam, Add the AOCClient.exe that got installed. For me it was "/home/merc/Lutris/ashes-of-creation/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/AOCClient.exe"
8. Set compatibility tool for Ashes of Creation in Steam to a proton-GE, UMU, or Proton Experimental. I use Proton Experimental, seems to run the best.
9. In Steam, set the Ashes of Creation launch options to:
eval $(%command% LauncherTetherPort=$(ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0)Now you can launch Ashes of Creation from Steam. Anytime you want to play, you must first open up the launcher from Lutris. Again, thanks to anyone who figured this stuff out, and ashesofbutt in particular. I removed his Bottles step, as it was not needed in my case (Ubuntu or Fedora.) The important part is using UMU-Proton in Lutris to install/run the launcher. (Some other runner may work as well, I don't know of one.)
It seems that this patch has quite a lot of graphics problems. I had to turn everything down to low setting - small animations causes the game to freeze sometimes (although not crash) Things like tree animation, water animation and a few other things. In some areas I was down to 1fps (entering Carphin Tower). Also I have noticed that although the background doesnt cause any issues, certain player models will. I have had to come out and reboot and go back into the game if there is a "crash" although I have always managed to get out of the game by doing alt-tab or something.
I will wait for the next patch to see if there is a difference. I am running 1440p and tried the game at 1920x1080 but still had the same issues.
The weird thing is that I go from 90fps to 20 fps without moving on the game. If I turn around it will hit 1fps for a few seconds, then go back up to 90 and then maybe 30. It seems that there is something that is being processed on the CPU and the queue is getting large that the game has to stop to play catchup. I thought that everything was supposed to be processed on the GPU but my CPU is getting used a lot when playing the game. Lucky I have it watercooled as its not hitting over 60 but I dont think this should be happening. It seems to have got worse with the new patches recently.
Yeah, yours demands flatpak, I'm carefully listing the steps and making sure everyone knows that's not necessary. It looks like different things work for different people, so the more the merrier!
(Also making sure people know it works fine in Ubuntu, after you told everyone it wouldn't work.)
Yes, I wrote in my tutorial to use the Flatpak version of Lutris to save the step of manually installing the UMU-Launcher, because everything the user needs is bundled in the Flatpak version and UMU-Launcher updates itself.
Could you please provide me with the link to the post where I supposedly claimed that it doesn't work in Ubuntu?
This was super helpful. One thing not sure if you run into also.
When I'm done playing Ashes, and I close out and then tell Lutris to stop the client it often hangs. After a while it does close, but from then on if I re-launch it fails to properly load the "are you human" auto-capcha thing. This will continue to happen until the computer is rebooted.
It's more an annoyance than anything else. Just curious if you have run into it. I've been using Proton Hotfix on Lutris not UMU, so maybe it's the runner.
I am using GE-Proton9-25 instead of UMU-Proton and have the same behavior. So I think this seems to be more of a general problem and has nothing to do with UMU-Proton in particular.
I just right click on the Launcher icon in KDE's notification area and click "Exit." I've never had the game hang from Lutris with this method. If you are running window manager/DE without notification area, not sure.