Glorious Alpha Two Testers!
Phase I of Alpha Two testing will occur on weekends. Each weekend is scheduled to start on Fridays at 10 AM PT and end on Sundays at 10 PM PT. Find out more here.
Check out Alpha Two Announcements here to see the latest Alpha Two news and update notes.
Our quickest Alpha Two updates are in Discord. Testers with Alpha Two access can chat in Alpha Two channels by connecting your Discord and Intrepid accounts here.
Phase I of Alpha Two testing will occur on weekends. Each weekend is scheduled to start on Fridays at 10 AM PT and end on Sundays at 10 PM PT. Find out more here.
Check out Alpha Two Announcements here to see the latest Alpha Two news and update notes.
Our quickest Alpha Two updates are in Discord. Testers with Alpha Two access can chat in Alpha Two channels by connecting your Discord and Intrepid accounts here.
Comments
Can you post what you are putting in the launch options? I'll see if I can see anything.
I use
and it works fine. Think some people do the -USEEOS=0 outside the brackets which is not working.
@Vaknar Would be awsome if you can pin this tread for new players to get Ashes work on linux. Because they ask in Discord and in the forums on a daily basis for it
I can confirm this works for me as well. Thank you everyone for making this possible and sharing with us. I feel like I might have a few fps less than on windows but I need to double check. I guess I can t expect too much when my PC can't even meet the minimum required specs.
Thanks again!
Anyone know how I could get gamescope working? My attempts have been futile since the AOCClient is seperate from the game client.
I just copy pasted again to make sure I'm not crazy.
Doesn't work for me, on NixOS. I'm not sure if Steam can't use netstat, or what my issue is but pasting in the value after just running the netstat command in a terminal works.
Netstat works fine via terminal. That's how I'm able to get the port to just paste in. I'm not on my PC today but I'll try to figure it out tomorrow. Not a huge deal to just paste in the value every time.
there's an extra space that should not be after the "print a[2]}')"
here's the code that worked for me once:
in case wineserv doesn't give you a result, replace it with IntepridStud, that might be cause after the port it connects for launcher it will re-direct to another port for game servers
and if you want to add mangohud add it after "$(" and before "%command%"
my current launcher option looks like this:
make sure to be careful as steam has a launch parameter character limit, it will work till a point then cuts out
thank you all for the good work doing here
o7
I cant seem to get it to load in on mine, what compatibility are you running it on? any other specifics that I may be missing? I can get in fine, its once I load my character the screen will get to about 12% black out and freeze the whole system requiring a restart of the deck on experimental.
Launch Error Settings.json not found.
running linux mint 21.3
As far as I am aware the launcher is OK and going into the game is OK. I think this must be something to do with graphics or something although other vulkan games work OK. I will do some more investigation and see what I can come up with.
will not be shown, you would have to be root to see it all.)" - you can adjust the command to redirect stderr to the null device. Be aware it redirects all errors.
"netstat -ulpn 2>/dev/null | grep wineserver | awk '{split($4, a , ":"); print a[2]}'"
I can launch the client in bottles with the same launch options, but I get Error 406 if I use the fancy version that automatically picks out the port number, and a connection timeout if I paste the port number into the launch options manually...
So first things first, anyone know how I can fix the DX12 error on steam?
You need vkd3d-proton
Do you remember where you logged out? Yesterday I got unlucky and was in the same node as Highwayman Hills and had this issue. It happens on Windows too, I confirmed. It was a bad node on the server (2 actually) that was causing the weird black screen for everyone trying to log in.
Yes I was at HH. Tried multiple times with multiple characters but still the same issue
Did you end up finding a way to fix this problem with cloudflare? I followed the instructions and ended up with this same problem.
If I try to use bottles with the same settings I am just hit with an error 406 which is the same as loading AOCClient.exe up without any parameters.
Every attempt tries to load up the graphics driver check:
If I use the steam launcher settings and put them in bottles I still get the error 9, so its picking up something thats different to the command with no arguments.
If I manually put in the port number for the listener I dont get an error 406 or an error 9 but eventually after a long time of trying to connect I am faced with:
Which leads me to believe that something in bottles is not passing on the output of the netstat command correctly over to AOCCLient.exe and then the Win64 exe file.
I have tried creating a system variable and a bottles variable with the port in but that doesnt work either. The interesting thing is that the steam version works and doesnt pop up with the graphics check or any of the errors which means there is something wrong with bottles
When you did the setup of the new one, did you change any of the settings before you installed it ? I have noticed that if you change MSwebview to Windows 7 before installing it, that breaks it sometimes and you have to start again.
I guess the issue is, that bottles missing some runtimes which are in steam. This is a common issue und thats why GloriousEggroll want to switch the whole proton runtime to umu-launcher where all needed dependencies are. At the moment only Lutris supports umu-launcher, but its early testing. We need to wait until bottles adapt the umu-launcher, then all these issues should be gone and we can only focus on fixes which are then in a central database.
https://github.com/Open-Wine-Components/umu-launcher
(Maybe someone answered it already but I'll post a quick solution here)
I had the same issue because of Steam flatpack version. The flatpack version of steam creates weird shortcuts to the AOCClient.exe like "run/123412341234/AOCClient.exe" and might have other issues too.
You should try the steam version via terminal (sudo apt install steam). This version correctly sets the paths to the AOCClient.exe and it works for me (Linux Mint 21.3 Cinnamon).
You might need to start the game twice (when starting it the first time), because of an error/crash, but after that it should work. Something else I encountered: When the game crashes it also requires to be started twice to become playable again (a little annoying but better then nothing).
___
Also thanks to the creators of this thread! The guide was nearly on point!
Ok, i reinstalled it without changing it to windows 7 and only changed it after installation and i got past the cloudflare check. I'm not sure if it "fixed it" tough since it didn't require me to click it manually it just passed the check by itself, but thank you anyways!
Note that I did a bare install without an additional network manager so there are some things I needed to get running, I'll try to not bring those up.
for arch, there is no such thing as
`sudo pacman -S bottles`
The flatpak variant works though, or install through `yay` or build it yourself, I don't know if flatpak will have any performance issues, if anyone knows about that please comment.
so for arch I think people would do (at least I think I did this): In my case I needed to reboot, as flatpak apps were not available initially, surely there is a better way than rebooting, but just sharing what helped for me.
As for running the Launcher, all windows (besides the edge view) start off all black untill something changed, I did set the dxvk.conf to set the env var, and ensured it was active (did restart bottles, perhaps I need a reboot) I'll try this in a bit once ashes finished downloading.
Edit: I failed to set the config correctly because I missed the comments, put your environment variables up like this (or wherever you put the config file)
For bottle installation folder it might be good to hint where the installation folder is, I didn't check if there was a entry in bottles itself, i noticed the windows directory (C Drive) for me is under `~/.var/app/com.usebottles.bottles/data/bottles/bottles/Ashes-of-Creation/`
maybe this helps someone.
A step I missed, which might be an obvious one, I could not launch the game after following the steps, I could when I enabled proton compatibility.
[del]I did get an Error 406, and I have no idea what that one is, but perhaps I'll find out later.[/del]
It seems I get no Realms 32 after rebooting and opening the launcher.
That seems normal, lets see how it goes tomorrow. It starts WAY faster than on Windows though