Glorious Alpha Two Testers!
Alpha Two Phase III testing has begun! During this phase, our realms will be open every day, and we'll only have downtime for updates and maintenance. We'll keep everyone up-to-date about downtimes in Discord.
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 III testing has begun! During this phase, our realms will be open every day, and we'll only have downtime for updates and maintenance. We'll keep everyone up-to-date about downtimes in Discord.
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
Thanks it works now
I need to read about Faugus and have a look at it
I'm facing a problem.
I'm running the launcher through Faugus and the game through Steam, os: Arch. I've tried "Proton-GE 10-4", "Proton-GE 10-1" and "Proton Experimental" and launched with these arguments:
eval $(%command% LauncherTetherPort=$(ss -tulpn | grep wineserv | ak '{split($4, a , ":"); print a[2]}' ) -USEEOS=0 -DARK_FRAME_RATE=60)andeval $(%command% LauncherTetherPort=$(ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -USEEOS=0 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only) game-performancebut I keep getting the same problem, I get to the character menu and after I select it and try to enter the world, the screen goes black and my computer freezes, so I have to reboot it. I've updated all my drivers, tried reinstalling the game and steam, but nothing has changed. Has anyone encountered this issue? Do you have any ideas on how to fix it?For Proton Experimental, I have set it up to use Bleeding Edge in Steam. After that, delete launcher in Steam, and recreate with Proton Experimental. See if that helps. If you switch between Proton versions that screws things up, and best to just create new connection in Steam. Leave up the AOC Launcher, when you start the Steam Launcher, so you have security connection.
I just started getting this today, didn't have this issue prior to Alpha 3 launch
Full Screen Windowed mode, low graphics settings, Nvidia RTX 2060 with reported 93% VRAM usage in Nvidia X Server Settings
Try the hotfix branch of proton. Worked for me.
Maybe will help some one, https://forums.tomshardware.com/threads/error-out-of-video-memory-trying-to-allocate-a-rendering-resource.3838977/
Tried to change Power Management from Performance to Balanced, but that did not help. Installed CPUPOWER-GUI using OCTOPI to install. Was able to changed top end of CPU Frequency, did not seem to work either. For CachyOS, going into the HELLO screen and Checking Cachy Update Enabled, this will help keep your system updated, specificly Tell you when there is a Firmware Update. To Update, had to delete the old version then install the new version. The version I had was original version from the May 2025 Distro install, so was fairly out dated. Though even with new firmware, did not help with GPU memory error. One thing I did notice, with NVTOP running in console, was video card memory was 7600 out 8000 when the crash happened.
Currently, several players on Discord have reported getting kicked by EAC. Maybe things will change again, and we'll be able to play Ashes natively with a launcher once more.
What came to my eye is your Z:/ folder. I remember this folder is for Wine/Proton something like a cache folder. I installed years ago a game wrongly on this emulated drive and got some weird errors, when it is installed outside the defined prefix.
Please try to completely reinstall Ashes and be sure that you Select C:/ for your installation. Sometimes this is preselected and sometimes not.
Maybe this will fix your issues. Try it with the updated Tutorial on the first page.
got the same error today, however I believe my installation is alright
Oddly, I had the opposite experience. I did it fresh last night from the downloadable installer, ran it in Steam, changed the binary to point to the launcher, and it worked beautifully. Played for a couple hours without any issues. This is using Steam runtime and Proton GE 10-13.
since the last update, every time I try to run the game through Steam, I get error code 31 for some reason (tried Proton GE 10-13, 10-10, 10-4 and Experimental)
Oh damn
I guess they fixed something with EAC, because also Windows players had the EAC kick issue. Would be nice if it works native again.
The other errors maybe not Linux related. Let's see what updates come from Intrepid.
I have AMD R9 9950/AMD 9070XT and was able to run everything in ultra settings yesterday, but now even just the menu runs like a slide show.
No idea, but do crash with my 2070s 8GB, and cannolisquid with his 2060 6 GB gets the same error
Started seeing in PTR before this version of Live, which carried over the changes I would guess. After that will have to see if I get the error sinrost gets for the Wine C++ Runtime Library. Though hopefully that is fixed, did new install. One thing at a time
So I have a fix for this. Basically running %command% inside the eval is jank, and isn't really running the game from proton directly. steam runs a shell, which runs proton, which reruns the shell, which launches the game. I have spent some time trying to get this to work without eval. I have had nothing but problems trying to get it to all work inside the command line arguments. The fix I found, is to make a script and launch the script then %command% .
So make an eac-wrapper.sh file and add the following:
#!/bin/bash PORT=$(netstat -ulpn | grep wineserv | awk '{split($4,a,":"); print a[2]}') exec "$@" LauncherTetherPort=$PORT -NOSPLASH -USEEOS=0open a terminal wherever the script is saved at and run:
in the steam launch options, do:
This runs it as a normal argument and runs as a child process, instead of having to pipe the game through shell before proton.
I still have to run the game via proton hotfix version instead of proton experimental or else I get the insufficient memory error.
I was getting this error and fixed it. Unfortunately, since I was having to wait for 5+ minutes "compiling shaders" every time I tested something new, I changed two things at once, so I'm not sure which of these was what did it. I have a 2080Super with 8G VRAM.
1) Change running Ashes with "Proton Hotfix"
2) Turn off DLSS in Ashes settings (I think it is this, but not certain.)
I am tired of waiting through shaders, so I am done testing for now... I will test later tonight and narrow it down, by turning DLSS back on and seeing what happens. But if you do the two things above, you might have success. (Someone here was saying Hotfix worked for them, and on the Ashes discord, someone was saying DLSS was giving them problems.)
Here is a bit for you to go on... Switched to Proton Hotfix with DLSS on, was able to get in. Though I had to turn off browser, discord, being the game started locking up. Also tried using Proton-GE Latest, but game the same error as Proton Experimental.
Was using Launch Options in Steam: eval $(%command% LauncherTetherPort=$(ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -USEEOS=0 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only) game-performance
Though this probably works as well: eval $(%command% LauncherTetherPort=$(ss -tulpn | grep wine serv | ak '{split($4, a , ":"); print a[2]}' ) -USEEOS=0 -DARK_FRAME_RATE=60)
Appreciate the suggestion! Unfortunately that didn't seem to fix the problem, I'm still getting single digit fps and a 2 second input delay running through steam with the launch options, but removing any of the launch options cause an error before I make it to server selection, and launching the game through the launcher with faugus doesn't have the fps issue, at least in the menu, but gets EAC Kicked when trying to log in. I feel like I don't know enough to even begin trying to troubleshoot this. I'm also on arch, I forgot to say it in the previous post, if that matters. Does anyone with Linux have a playable game today?
I'm comparing to phase three. Day one of phase three (26th) I installed through faugus, had no issues launching or with fps, did not need to add the game exe to steam or any launch options. It just worked.
I stopped playing on the 26th due to a half hour downtime that kicked us off the game. Either that maintenance or the 4 hour one on the 27th caused all the issues I've been having now with launching and playing. No idea which one it was because I didn't attempt to play between them.
1. Add non-Steam game > Add the IntrepidInstaller > Change Compatibility to ProtonGE.
2. Start the Installer via Steam > Install (with EAC, WebView2 and Visual C++ enabled) > Don't start the launcher after install
3. Edit the paths. Replace USER and APP_ID. APP_ID should be the longest in the compatdata folder.
a) Edit the Target path: "/home/USER/.local/share/Steam/steamapps/compatdata/APP_ID/pfx/drive_c/Program Files/Intrepid Studios/Launcher/IntrepidStudiosLauncher.exe"
b) "Start In' path: /home/USER/.local/share/Steam/steamapps/compatdata/APP_ID/pfx/drive_c/Program Files/Intrepid Studios/Launcher/
4. Start Client > Login > Install Ashes of creation > Don't start the game afterwards
5. Add another non-Steam game, the AOCClient.exe
a) find it in /home/USER/.local/share/Steam/steamapps/compatdata/APP_ID/pfx/drive_c/Program Files/Intrepid Studios/AshesOfCreation/PROD/AOCClient.exe
b) set launch options: eval $(%command% LauncherTetherPort=$(ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -USEEOS=0)
6. Have the launcher running via Steam > Start AOC Client via Steam, not via launcher > enjoy
Note: 5.b) ss -ulpn is interchangeable with netstat -ulpn
That sounds like maybe it's using your integrated GPU (the one on your CPU) and not your dedicated GPU (nvidia? amd?) There are some things that can fix that.