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.
Linux Tips, Tweaks and Troubleshooting Thread
Azalroth
Member, Braver of Worlds, Kickstarter, Alpha One, Alpha Two, Early Alpha Two
Here I want to collect all good informations about linux support from community members. Please keep his thread clean and only comment your informations, tips or workarounds. Together we will rise up and make our main game ready for linux in the future.
Edit: Complete Tutorial: How to Get Ashes of Creation Running
Step 1: Install Bottles
Bottles is a compatibility layer that helps run Windows applications, including games, on Linux systems. To begin, you'll need to install Bottles.
Open your terminal and run the following command based on your distribution:
For Ubuntu/Debian-based systems:
For Fedora:
For Arch Linux:
If Bottles isn't available through your package manager, you can install it via Flatpak:
After installation, you can launch Bottles either from your applications menu or by typing bottles in the terminal.
Step 2: Create a New Bottle for Ashes of Creation
Once Bottles is installed, you need to create a separate "bottle" for Ashes of Creation.
Open Bottles and click the + button to create a new bottle.
Choose a Windows version (Windows 10 or 11 is recommended for compatibility).
Select a Gaming template for optimal configuration, or create a custom one based on your preferences.
Step 3: Install Dependencies
Once your bottle is created, you'll need to install some required dependencies.
Go to the Dependencies tab in Bottles.
Install the following dependencies:
vcredist2022 (Visual C++ Redistributables for 2022)
webview2 (for embedded WebView support)
Step 4: Configure Wine
Next, you need to configure Wine for the best compatibility.
Go to Legacy Wine Tools in Bottles.
Click Configuration.
Select msedgewebview2.exe in the Wine configuration options and change the Windows version from 8.1 to 7.
Step 5: Install the Intrepid Launcher
Download the Intrepid Launcher from the official Ashes of Creation website.
During installation, ensure you only select to install Easy Anti-Cheat (EAC) alongside the launcher.
Important: After installation, do not launch the launcher immediately. Instead, click Finish and uncheck the option to launch the launcher.
Step 6: Fix for Black Screen in Wayland (If Applicable)
If you're running a Wayland session, you might encounter a black screen when launching the game. Here's a fix:
Add the following environment variable to configure DXVK (for better DirectX handling on Linux):
Create the dxvk.conf file with the following content:
Important: If you are using Bottles as a Flatpak, ensure that the dxvk.conf file is placed in a location where Bottles has access. It's recommended to put it directly inside the Ashes of Creation bottle, as noted by @Guillemets.
After configuring the dxvk.conf file, restart Bottles and try launching the game again.
Step 7: Launch the Game
Once you've set everything up, it’s time to launch Ashes of Creation.
Start the launcher in Bottles and wait for it to load.
Log in to your account and let the game update as needed.
Important: Keep the launcher open in Bottles.
Step 8: Set Up Steam for Launching
Open Steam and click on Add a Non-Steam Game.
Find and select AOCClient.exe from your bottle’s installation folder.
In the Steam Launch Options, add the following code:
or if not work
This will allow Steam to launch the game alongside the running launcher.
Step 9: Play the Game
Now, with the launcher open in Bottles and Steam configured, simply click Play in Steam. Ashes of Creation should launch successfully, and you can start playing!
Good luck, and enjoy playing Ashes of Creation on Linux!
Credits to all who worked hard for this fix: Special thanks to @icedown for the final fix!
Edit: Complete Tutorial: How to Get Ashes of Creation Running
Step 1: Install Bottles
Bottles is a compatibility layer that helps run Windows applications, including games, on Linux systems. To begin, you'll need to install Bottles.
Open your terminal and run the following command based on your distribution:
For Ubuntu/Debian-based systems:
sudo apt install bottles
For Fedora:
sudo dnf install bottles
For Arch Linux:
sudo pacman -S bottles
If Bottles isn't available through your package manager, you can install it via Flatpak:
flatpak install flathub com.usebottles.bottles
After installation, you can launch Bottles either from your applications menu or by typing bottles in the terminal.
Step 2: Create a New Bottle for Ashes of Creation
Once Bottles is installed, you need to create a separate "bottle" for Ashes of Creation.
Open Bottles and click the + button to create a new bottle.
Choose a Windows version (Windows 10 or 11 is recommended for compatibility).
Select a Gaming template for optimal configuration, or create a custom one based on your preferences.
Step 3: Install Dependencies
Once your bottle is created, you'll need to install some required dependencies.
Go to the Dependencies tab in Bottles.
Install the following dependencies:
vcredist2022 (Visual C++ Redistributables for 2022)
webview2 (for embedded WebView support)
Step 4: Configure Wine
Next, you need to configure Wine for the best compatibility.
Go to Legacy Wine Tools in Bottles.
Click Configuration.
Select msedgewebview2.exe in the Wine configuration options and change the Windows version from 8.1 to 7.
Step 5: Install the Intrepid Launcher
Download the Intrepid Launcher from the official Ashes of Creation website.
During installation, ensure you only select to install Easy Anti-Cheat (EAC) alongside the launcher.
Important: After installation, do not launch the launcher immediately. Instead, click Finish and uncheck the option to launch the launcher.
Step 6: Fix for Black Screen in Wayland (If Applicable)
If you're running a Wayland session, you might encounter a black screen when launching the game. Here's a fix:
Add the following environment variable to configure DXVK (for better DirectX handling on Linux):
DXVK_CONFIG_FILE=/home/path/to/dxvk.conf
Create the dxvk.conf file with the following content:
[IntrepidStudiosLauncher.exe] d3d9.shaderModel=1
Important: If you are using Bottles as a Flatpak, ensure that the dxvk.conf file is placed in a location where Bottles has access. It's recommended to put it directly inside the Ashes of Creation bottle, as noted by @Guillemets.
After configuring the dxvk.conf file, restart Bottles and try launching the game again.
Step 7: Launch the Game
Once you've set everything up, it’s time to launch Ashes of Creation.
Start the launcher in Bottles and wait for it to load.
Log in to your account and let the game update as needed.
Important: Keep the launcher open in Bottles.
Step 8: Set Up Steam for Launching
Open Steam and click on Add a Non-Steam Game.
Find and select AOCClient.exe from your bottle’s installation folder.
In the Steam Launch Options, add the following code:
eval $(%command% LauncherTetherPort=$(netstat -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0)
or if not work
eval $(%command% LauncherTetherPort=$(lsof -i4UDP | grep wineserve | awk '{print $NF}' | sed 's/\*://g') -NOSPLASH -USEEOS=0)
or for arch/steam deck
eval $(%command% LauncherTetherPort=$(ss -ulpn | grep wineserv | awk '{split($4, a , ":"); print a[2]}' ) -NOSPLASH -USEEOS=0)
This will allow Steam to launch the game alongside the running launcher.
Step 9: Play the Game
Now, with the launcher open in Bottles and Steam configured, simply click Play in Steam. Ashes of Creation should launch successfully, and you can start playing!
Good luck, and enjoy playing Ashes of Creation on Linux!
Credits to all who worked hard for this fix: Special thanks to @icedown for the final fix!
Silence is freedom...
5
Comments
Because of Discord message limit I where to able to fit following:
The Edge WebView2 problem comes from Microsoft forcing hardware acceleration.on and Wine unable to use the hardware acceleration. I remember seeing this hardware acceleration problem on Chrome on Windows over a decade ago on some GPUs and that webpages could be interacted with, both with keyboards and mouse even if Chrome window where black, which gave me the idea that I that I maybe where able to interact with the WebView window.
From my test with the launcher the only thing that does not work under Linux are the launch game button. When running the launcher though Wine in a CLI I got zero error messages when clicking the button and the launcher made zero logs, which is wired when you consider this is an alpha test.
When I tried running the launcher and game client in a Windows 11 VM I where able to see that the launcher where launching the client with some parameter with Taskmanager. The parameters where "AOC LauncherTetherPort=52534 -NOSPLASH -USEEOS=0" doing the prealpha2 stress test.
Based on the LauncherTetherPort parameter my guess would be that when the launch game button works, the launcher opens a network port then starts the client with the parameter, and the client uses the port to request and receive the data needed to connect to the correct Intrepid servers.
If you are using native wine then just run winecfg and set the dll override in there
Once this is done, you are ready to install the launcher. If you installed via flatpak, then Bottle will need permission to access outside filesystems through flatpak so install Flatseal and in here you can give access to the app to access the folders where the launcher is.
Next install the launcher. It should install without any issues. When the client loads, and you press login you will get the black login screen. Click on the screen and press tab. Enter your username. Press tab again and enter your password then hit enter. This should make the window disappear and it will log you in.
While the servers are down, this is not going to install the game. So as of today - 1 days after the DDOS attack with the cloudflare load balance queue on there I can confirm this works. Before, what was happening was that the webform would remove the password when you press enter but now this setting appears to get around that.
Obviously I will keep an eye on things as the installer progresses.
You might also get a cloudflare verification to see if you are a bot just click and wait it out or simply close it and re-open it.
Just remember if you use flatpak, and you update the system - flatpak uses its own repos, so you will need to manually update flatpak when you have updated your system. The only reason why I use flatpak is that I want my debian sources to contain apps i only want on the core system. Anything else such as video editing, audio, media stuff I push through flatpak because of the containerisation of it and so it doesnt interfere with the kali system. It works for me but may not work for you, either way, when you update your GPU drivers, just double check that everything works OK after.
I think I fixed the webview2 on linux.
What I am using?
- Fedora 40
- I´am on wayland (if your launcher starts with a black screen look @ https://forums.ashesofcreation.com/discussion/comment/480679#Comment_480679 )
- Bottles
What steps to reproduce this?
- Install Bottles
- Create a gaming bottle for Ashes
- Go to dependencies and install vcredist2022 and webview2
- Then go to legacy wine tools and click on configuration
- Select msedgewebview2.exe and change Windows Version 8.1 to 7
- Now select the librarys tab and add a ddl override for urlmon (Not needed for me, but some folks may need it) // Credits to @Funkychicken
- Then install the Intrepid Launcher with only select EAC
- After selecting the Alpha Two Enviroment the authentication window takes like 3-4 seconds to wait
- Now see Cloudflare captcha and the login afterwards
- Profit
PS: I logged in and nothing happens, maybe because server is off or we need to investigate further. Nice to see the progress in the linux world. Together we can play soon
You have three choices:
- Switch from Wayland session to Xorg session
- Disable DXVK
- or you try to set shadermodel to 1 on the dxvk config file
Wayland (Hyprland)
Bottles, native install
AMD GPU
I just confirmed the launcher works on Wayland with shaderModel set to 1. Thanks @Azalroth
In your prefix at: drive_c/Program Files/Intrepid Studios/Launcher
make a dxvk.conf if it's not there. I didn't have one. and add to it.
Beware, that if you use bottles as flatpak you need to put the dxvk.conf file where your bottles have rights to access. If you put it in the Ashes Bottle its the best like @Guillemets said.
For now the endboss is those two:
This comes when you start the game. I tried to use DXVK_NVAPI_DRIVER_VERSION=99999, but no luck. You can skip it if you press no.
Then we have this error:
If you click Okay then we have the Connecting... boss.
I guess this is the same issue since beginning. If you press play on the launcher the launcher can´t start the AOC.exe. If you start it manually you get the Connection... boss of doom
https://github.com/doitsujin/dxvk/blob/master/dxvk.conf
Everything else I was seeing was Proton specific so not helpful here.
I also wish they had a list of what all of the error codes mean. 10 is not helpful at all.
0150:err:combase:RoGetActivationFactory Failed to find library for L"Windows.Storage.AccessCache.StorageApplicationPermissions"
warn: D3D11Texture2D::QueryInterface: Unknown interface query
warn: f8fb5c27-c6b3-4f75-a4c8-439af2ef564c
Since the launcher updates yesterday I get this red bar underneath the login menu (i think it's hiding an error) even after setting up a new bottle.
I have been playing on windows as I don't know how to start trying to fix these things.
I can still confirm, that login and updating works fine on Linux if you follow the steps closely. They added a new cloudflare captcha under the password field. On my side this solves itself to green and can login for now. Maybe login with your machine with a browser on the Ashes site could help to skip the captcha.
But the issue still remains, that the AOClauncher can´t properly launch the AOC.exe with the information needed. I guess there is some weird native windows call which is not implemented in Wine, or they use an unusual way to call the AOC.exe.
Maybe it could be solved with a protonfix, but reporting this issue to Valves protonfixes Github could be lead to zero interest, because it is an Alpha where the launcher and the game could change on weekly basis.
Tried it today. This sadly not works, but it is not needed for now because you can skip this issue by clicking no. But could be possible that Code 10 is the error for false graphics driver. This is only speculation for now because this issue appears if you start AOCClient.exe seperatly while the launcher is running, because the AOCLauncher can´t start the exe anyways.
The weird part is, that if you start the AOCClient.exe via the AOCLauncher not even logs appear. So this makes debugging nearly impossible. So I don´t know if this is bad code on the Launcher side or it is a proton issue. I guess bad code on the Launcher side, because the issue remains if you change the runners to soda, proton, wine-ge and so on.
Thanks for all your wizardry @Azalroth
Thanks @Azalroth for the info.
I have a windows machine but sadly it only has 8GB of ram (which isn't enough to run the client).
https://github.com/ValveSoftware/Proton/issues/8212
I ask you to document and report qualified issues and universal problems under the Issue Report so that Valve can focus their efforts as easily as possible.
Thank you, friends, and let’s hope everything works out.
My ideal scenario would be for Valve to communicate with Intrepid and for Intrepid to issue a statement saying that they may not actively develop for Linux, but they won’t stand in the way of Wine/Proton, meaning they could configure things like EAC to work with Wine.
We’ll figure out the rest!
Let me/everyone know if you find a fix
If people are still having the webview2 error that bounces your password it could be a previously installed wine dependency outside of bottles so make sure you check them
My initial theory was that there's something wrong with the DLL's or some are missing.
Checking the wine configuration -> libraries, I saw that 'atiadlxx' (related to AMD graphics) had question marks, which I overrode it to be native and then built in (nvcuda as an example).
The change did not do anything except provide me with a UE5 crash window
Tried to find the logs but with no avail (does anyone know the log locations)
Fixed it back to the previous 'error code: 10' stage by adding a few new libraries:
d2d1.dll; dwrite.dll and dxdi.dll
The issue might still be coming from the libraries but maybe it has something to do with permissions. Maybe the AOCClient is unable to access something like the computer device files.
Whoop - hyped for this!