Glorious Alpha Two Testers!
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Comments
Hello, thanks for this. I had to do a reinstall because I wanted to move it onto an M.2 NVME SSD instead of a 6GB/S SATA SSD. But anyway, cheers
Error from launcher:
Last few lines of bottles instance:
Settings.json error is EAC related. Try installing EAC again manually in Bottles with the in this Folder
The game generally worked OK and was nice and smooth but when hitting a busy area in the game (such as towns) or fighting with lots of mobs and there was a lot of drawing on the screen then the game would crash. A total lockup like the previous issues I had. I am not sure if this is a problem with the nvidia microcode in the driver version or a kernel change on nobara vs fedora.
I tried turning the settings to low, turning off a lot of things, changing to window mode etc and still the same issue. I had it running at 1024x768 in low detail at one point and it still crashed.
So now I am back to nobora, using the kde plasma build but I am using X11 instead of wayland. I have noticed that wayland is a bit unstable at times, so I switched back to X11 using
Since doing this, I have had no plasma crashes or anything. I have also installed XFCE and may get that setup later this week but in the meantime ill stick with KDE to see how that holds up.
Do you have gnutls installed ?
Hey, I really appreciate the help with this. This is my folder structure inside the bottle for Ashes:
I will try the manual install within the bottle and see if it helps. I have gnutls 3.8.8-1 currently installed on my system. I'm fairly new to Linux in general, so, any suggestions are welcome. Just went with Arch/KDE plasma x11 because from what I researched it was a good system to run for gaming specifically.
Thanks again and I'll try the suggestion
Also lib32-gnutls if you don't have that one. If you can install and run Steam you should have it, I think. But worth checking.
I just want to confirm and share my experience. I tried running Ashes with Linux Mint and I didn't get the game running. When I was very lucky I was able to load the game and run for 10 seconds before the game crashed. I now switched to Fedora and it runs fluid.
If you really want to stay at linux mint and got the same problems, there is an edge version using a newer kernel than the usual mint. Sadly I just found out today, but meanwhile I used to love Fedora with KDE, so I wasn't able to test it. But maybe worth a try before you consider changing the distro or going for virtual machine solutions and stuff.
I am not sure about steam deck but if you load up the game and it doesnt show the realms or the menu it means it is not authenticating correctly. The graphics drivers error you get isnt a problem really. You can just click no and it should go away but you may get some other errors after that.
If it goes into the game but it freezes then I think this is a kernel problem. I can replicate this on Kali or debian or ubuntu. I dont know if there are any updates to the steam deck which you need to do and then try it again
I get into the character select screen but the game freezes once I hit “play” and try and load the game. Steam deck just gave me various updates today to do so I’m crossing my fingers come Dec 20 something will work….. I’m going away for two weeks so getting this working is my only way of playing the first two weeks of phase 2
How do you know what version of Linux you are running on a steam deck? Sorry I’m new to Linux so don’t know much about it
You can find this via a few methods. Firstly you can try running -dx11 to the launch options of the application.
Make sure that all the vulkan updates have been installed. Vulkan and dxvk replace directx in linux so if these are running then you shouldnt get the directx issue.
To find your environment either:
echo `uname -r`
cat /etc/system-release if you have it
cat /etc/os-release
You will need to all of this in a shell in desktop mode.
It works fine. My setup: Nobara, X11 plasma. Nvidia Drivers using the Nobara custsom build. Install bottles and steam. Setup bottles like in page one of this thread, gaming bottle, webview2, vc2022. Set webview2 to Windows 7. Download and install the game in the bottle.
If you are on wayland, look at the dxvk.conf issue and create the config file then create an environmental variable in bottles for the launcher. But you dont get the issues with X11 - again on the first page of this thread.
When you have logged in and installed the game (when it can download) and you see launch game then in steam, add a custom game to steam, select AOCClient.exe. Force run Proton Experimental, Shortcut options as in the first section but mine are:
eval $(MANGOHUD=1 MANGOHUD_CONFIG=time,gpu_stats,gpu_temp,gpu_junction_temp,gpu_power,gpu_fan,cpu_stats,cpu_temp,cpu_power,vram,ram,swap,fps,frametime,fps_limit=50 %command% LauncherTetherPort=$(netstat -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0)When the servers are up then run the game.
If you are getting issues, black screen, game crashing, instability then if you are not using fedora, nobara, Arch linux then it is likely your kernel is using an older one or is missing some configuration or microcode. I have tested this on: Ubuntu, Kali, Redhat, Debian. I can say that all these distributions out of the box are missing something because the game was unstable. On arch, the game crashed about 30 seconds into the game. The only stable distro I have seen is Nobara, however on the other distros, I could get into the menu and create a character but after that it would crash on the loading screen. So because it is consistent across all of the distros I think there is something missing in the kernel of them. On Nobara it works though without any issue.
I also tried with the actual kernel 6.12.4 and there was no way to pass through loading screen with the exact same setup.
So my way to go for tomorrow is: Trying with Kernel 6.11.11 -> Try the solution with nobara from Funkychicken and last would be a trash windows installation.
We got so close guys, but we are still missing a little key
Running artix with an amd graphics card, but I was under the impression wine should be handling this for me. Just in case I am running a system update, but it will be a bit before I can test if that worked.
Quick edit: Did find VKD3D is set to vkd3d-proton-2.14, with no other options for version (other than disabled)