Glorious Alpha Two Testers!
Alpha Two testing is currently taking place five days each week. More information about Phase II and Phase III 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 testing is currently taking place five days each week. More information about Phase II and Phase III 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
Today I did some more tests on launching the game with the "Launch Game" button. As it looks to me it seems to work with Proton Experimental but not with Proton-GE9-27.
Can somebody confirm this?
Caution to those switching from Proton-GE to Proton Experimental: this breaks the WebView installation in Lutris. In this case, you need to download exactly this version from that website (Webview2 Installer) and launch it in Lutris as an .exe file, then switch back to Windows 7 in the Wine configuration.
Sorry, I forgot to mention that I am using the bleeding edge version of Proton Experimental. I had the same problem with the normal version. Maybe you can try with this version.
As for the problem with WebView, I had these problems too, but the other way around. In my test, the problem occurred when I switched back from Proton Experimental to GE Proton.
Now I can confirm, that the bleeding edge version fixed the Error 33 and the game is now fully starting from Lutris. Nice find!
For people who want to replicate that you need to go to steam and do a right click on Proton Experimental and change in Betas to bleeding-edge.
Then you right click again and follow the local folder for Proton experimental
Then copy the Proton - Experimental folder
And put it in your Lutris runners/proton folder and rename it like Bleeding Edge Ashes because Lutris already have Proton Experimental if you use flatpak.
Then you go to Lutris and restart it if it is already running and change the Ashes Runner to your renamed Proton Runner
Have fun
PS: I think it will be native if Proton 10 gets out of Beta and you can wait until Proton-GE latest gets the update.
I updated my kernel to 6.12.27.
I changed the apt tree to use unstable for the newest packages and did a full system update.
Did all of the modules again and then tried again but the same thing happened.
I disabled the default CFS in the kernel and then set up BPF and then verified this with that show its enabled after installing a scheduler from git. This was OK on debian so long as all of the dependencies were there. As A test I tried some other games and this worked OK.
I still get the same issue in the log even though the scheduler was active. Its weird because other games seemed to have seemed a big improvement but not really ashes.
Now I check my Windows Machine log file which is successful for login. It seems that the ones for Debian still have a code issue:
Successful login:
Unsuccessful login and frozen system on linux:
Now even though the system had been updated to the latest patches, kernel etc with the latest nvidia drivers. There still seemed to be an issue.
To write it all off I decided that another rebuild was needed. I got to the point where debian was not really doing what I wanted to do.
So instead I installed catchyOS as the sched_ext is build into the kernel and the binaries are already loaded into the system. The kernel is tweaked for performance too and it seems a lot better than debian initially.
I installed ashes OK and tried the steam proton and used the steam proton-catchyos package for the runner but it seemed to have network problems too, so I switched back to the proton-hotfix one and this seemed to be OK for a few minutes but the game bombed out when in a town. When the serves are back up ill have a play with this again.
So in all I managed to get past the black screen but I think Steam still has some work to do on some of their runners, especially with the application hooks when using certain runners.
As for now ill get used to CatchyOS and pacman and see how this goes. At least I am on kernel 6.14 now, where as the stable on debian was still on 6.1 which is way out of date. I think it just goes to show that debian isnt really made for gaming.
Nobara is OK for gaming but I had a few issues with some of the upstream servers. I just wanted to try catchy to see what it was like and it appears that the documentation and the support for it is much better than Nobara.
I personally use Fedora because I still want to decide for myself which tweaks I want and which ones I don’t.
90% of the errors in Linux gaming are due to missing or incorrectly installed drivers, or because the packages are outdated, as is the case with all Debian-based distros like Ubuntu, Mint, and others.
You just have to look through the forum, and you’ll see that most of the people who have problems are those using Debian-based distros. And even when they get it working, they’re often getting 20-30 fps, which is due to missing drivers for Nvidia or AMD. Most of the time, it’s Nvidia, and the average user doesn’t know how to install the drivers correctly. I mean, Mint and Pop OS are the only Debian distros that make it easier during installation by asking whether you have AMD or Nvidia and automatically installing the drivers.
For me, it’s also difficult to convince people that it’s easier to get into Linux gaming by telling them to use an Arch or Fedora-based distro when everywhere on the internet it says you should start with Ubuntu & Co as your first distro.
I kind of feel like this is a psychological operation by Microsoft, where people try it, fail with the drivers, and then switch back to Microsoft. If they’d just choose a gaming distro from the start, we’d have a much larger Linux gaming community.
While I feel like ashes has a lot of work to do on the optimizations side ( A LOT! ), I had a pretty decent experience, ofc, thanks to this thread, as I wouldn't ever knew to do this on my own.
Yes I agree there. I came from Gentoo years ago with a stage 1 build which was kind good because you got to customize everything. But the process for this took about 3 days to build a system so its not feasible anymore not having much time for anything later in life. In the young days you had no responsibility but now things have changed tremendously so spending that amount of time does not exist anymore when trying to build a system. These days I rarely have time to research patches and test a system build. I would love to get paid for doing something like this but everyone needs to work to earn money to live and spare time do things like this without being paid for it are scarce.
Fedora is a good OS I know and a lot of new distros are based on that. Debian is good for some things but not good for others. Especially the modern applications for these days. The stable version ships with 6.1 kernel, BPF isnt even in the kernel yet. Kernel 6.14 is in stable now, so the time to get Debian to this will be 2-3 years almost. I feel like this is setting back the community in terms of moving to linux because its confusing even at the best time trying to choose your distro. For a new user, who has never installed linux before, which do they choose as there are so many with pros and cons.
For me, I like to try something, configure it, patch it, get it working and when I know that it is not possible ( for example having to resort to unstable apt branches to get the basic kernel functions that I should be using) sometimes rings alarm bells for me making me think I shouldn't be doing this, and there is a better way to do things.
The other thing which I think doesnt help are the software developers only making the games on Windows. If we had a native linux port for most of the games then it would be a lot easier to use any distro. If Dota2 can do it then I am sure others can do it also, but the investment and SDL model sometimes does not allow for this due to financial constraints.
Anyway, I am going to stick with CatchyOS, it seems OK so far. Both from the functionality and the support point of view. I liked both Nobara and this originally but I am not a fan of Wayland in Nobara - yes it looks cool, but it comes with other technical glitches that I dont need right now, and I know you can switch to xorg which is cool, but it gets installed by default (the last time I checked) where as CatchyOS you can choose what you want on install which I think would be good for newer users of linux and make it easier for them. Anyway, time for work
I was able to test the installer so far, and everything works. I just can't download the game at the moment because the server is down. But I assume that the Steam hook is no longer needed either. Kudos to Valve and Proton!
will you update the steps to install it via Lutris? I seem to be stuck on the auth part after running the launcher. Also, do we still need to use the flatpack version of lutris?
I will update the tutorial when Proton 10 is out of beta. For now your can just download the Intrepid Installer and the webview2 i linked above. Then you need to switch in Lutris BEFORE the install the Wine Runner to Proton-GE Latest and then you install in Lutris via the exe install and only choose Intrepid Installer. Also in the Installer you only choose EAC as before and close the Installer after it is finished and uncheck the box where asks for launching the Launcher. After that Ashes is in your Lutris Overview. Then you need to change in Executables in the first row to the Intrepid EXE. After install there is the dll choosen which not work to start.
Then your start webview2 as EXE inside the Wineprefix and install it. After that you can launch Ashes and can update and play.
It doesn´t really matter if you pick flatpak or not. But Flatpaks are designed to run in every distro as the same, so all dependecies get updated and are equal.
Interestingly when there is an error 31 or an error 407, I see this in the log when running directly from bottles.
So it looks like its having an issue as launching AOCClient.exe directly from bottles so it cant make a connection on localhost to the port. Although this normally does work ok in Steam, and even thought the tetherport is issued in the command it still fails.
When it fails in Steam after the character screen I get this:
So has there been a new framework for models or new types of shaders or something that the runner cant load.
Is everything still working on Lutris OK ?