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
Notably, this proves that the "Error Code: 10" popup is a separate issue, and not necessarily a GPU thing. I'll keep digging through the logs to see what I can find.
Some bumps but the bottle stuff is awesome - would like to replace that with Steam as a Launcher in the end.
# Setup
Arch Linux with AMD GPU
* install bottles via yay
* create new bottle for games named AOC
* install vcredist (latest version)
* install webview2
* set webview2 to Windows7 in Legacy Wine-tools
* override urlmon lib in legacy wine-tools
* Change Bottles-Runtime and Steam Runtimeenv to On in bottle settings
* change Rendere in advanced view settings ( damn german gui thing) to Vulkan
* create dxvk.conf in /$HOME/.local/share/bottles/bottles/AoC/drive_c/Program Files/Intrepid Studios/
```
[IntrepidStudiosLauncher.exe]
d3d9.shaderModel = 1
```
* cd ~
* ln -s "/$HOME/.local/share/bottles/bottles/AoC/drive_c/Program Files/Intrepid Studios/AshesOfCreation" AshesOfCreation
* add $HOME/AshesOfCreation/AOCClient.exe as shortcut
* Start the Launcher and Login
* Run the AOCClient
* select not to GPU driver update
Now I see Error: 10 - whatever that means now. Did I miss this somewhere?
I've been digging through the logs a little bit to see if there's any info there on why the game might fail to start from the launcher. TL;DR is that my current working hypothesis is that the launcher never actually tries to run AOCClient.exe. Two reasons for this suspicion:
1. Starting the game from the launcher creates no log files in the game's log folder in local appdata. Starting AOCClient.exe directly creates an EXTREMELY verbose log file instantly, so if the launcher did start AOCClient.exe and it just crashed, I'd expect to see that in the logs.
2. The Launcher's logs seem to only check if AOCClient.exe is executable (which returns true), but then it only outputs two more lines with user info and nothing else.
Regarding point 2, I'm most likely going to find some time this weekend to get Windows running on another SSD I have lying around. I'd like to check what the Launcher logs say on Windows.
I've also taken a cursory glance at the log file of the game itself (I just used cat AOC.log | grep -i "error" > errors to filter it). I found some errors, two of which relate to anticheat, but I can't really gain any useful insight from any of them.
Launcher logs when starting the game from there:
Error lines from AOC logs:
No, that's pretty much the current state of affairs. I spent the afternoon trying to figure out why, but no luck. People smarter than me will have to sort this one out.
Maybe I will log into that other OS and install, start and see what those logs say
And then work from there - I will have more time on the weekend to play around with this.
"ClientIntegrityViolated" is not very encouraging.
Edit: Nevermind, those are just API functions for removing callbacks. Looking at the EOS SDK docs, neither of those errors are EAC intentionally blocking the client from running.
Everything else looks to be an issue with the Streamline API. From what I can see, WINE does not yet support it, and can not until Nvidia open sources more of their code. There might be a hacky workaround, so I'll try it out today and let y'all know how it goes.
R.I.P.
You might have to enable full crash logs in the launcher settings. Top right corner, hit the cog, then under "Game", there's a checkbox.
You add the installer for the launcher to steam, run it in compatibility mode, then add the installed launcher to steam and run via compatibility mode and the launcher should work & download updates. It still works for the wuwa launcher, even if the game fails to run. I use EndeavourOS and Proton Experimental in steam for it.
I'm working atm, so I can't look up the steps again, but I think you can add the game client to steam and run it manually as well.
@inajacket I'm not sure what streamline API does, could this be related?
Anyway, the game ended up crashing for me even on Windows because of a supposedly missing .dll. Here is the launcher log from the point where the Linux logs cut off:
If this was a fresh install and it is saying it cannot find xinput1_3.dll you need to install DirectX runtimes from June 2010. You can get it below
https://www.microsoft.com/en-us/download/details.aspx?id=8109
I'm getting the same issue with the red line and a "hidden" Cloudflare captcha. There's a cloudflare verification that displays _before_ the login page, and that seems to work fine. But the new(?) captcha underneath the password field is just a sliver of a bar that turns red when trying to log in. I can't interact with it at all. Not sure how to get around this.
I doubt that would do anything as you'd get that error trying to run AOCClient.exe directly if it was an issue under linux.
The actual game client is located in /Intrepid Studios/AshesOfCreation/PROD/AOC/Binaries/Win64/AOCClient-Win64-Shipping.exe
I don't know what to do with this information, but I think it's likely the source of the issues.
Edit: After fishing around around a while I found an open udp port when the launch game was clicked. This was port 40397. If I launched with that as the LauncherTetherPort, i get the same error, but with Code:32 this time.
Edit: Made it in game with 5 minutes to spare before the shutdown.
First, my system. This is just for reference, it may help others refine the process.
Graphics Card: NVIDIA Geforce RTX 4070
OS: Arch Linux + Wayland + KDE + Bottles + Steam
After installing the game and running the launcher via Azalroth excellent post I was able to start the launcher and update the game.
https://forums.ashesofcreation.com/discussion/comment/480141#Comment_480141
I also went into the setting in Bottles and activated both Bottles Runtime and Steam Runtime. I have not tested whether this makes any difference yet.
Once the launcher is running and updated, add the AOCClient.exe to steam via Games->Add a non-steam game.
Next enter this command in a terminal.
This will result in output similar to this
55882 will be your LauncherTetherPort. This number will change every time you start the launcher.
Edit the AOCClient.exe shortcut in steam, changing launch options to: I was also using Proton Experimental for compatibility. Others may work better, I did not have time to test.
Every time you restart the launcher, you will have to change the LauncherTetherPort in the launch options to the launcher's current port.
Run the AOCClient.exe from steam and it should connect. Even though the servers are down, if done correctly you should get a "No available Realms. Code:23" to show that it is communicating with the launcher and servers correctly.
I don't know if there is any way to stop the launcher from changing ports every time you restart it so It will be a bit of a pain until a work around for this is found. I also was not able to successfully launch the AOCClient from bottles. I would still get the "Service Connection Timeout. Code:32" when I tried.
I think this should be a working solution. I think you solved the launcher talking to the client problem.
Thank you for your wizardry!
With that said after following your process on a fresh bottle, I launch AOCClient.exe and get this popup I think must be related to EAC. Happens no matter the method I use to launch it so it must have something to do with my system I guess.
I would get this before too and wasn't sure what to do about it but seeing as we installed the same dependencies and everything now I am even more confused about it.
Any chance your messing around with the VM might have revealed what I am missing here?
I am not savvy enough to know where to start there other than basic VM setup