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
For the distro, I'm using Gentoo
as for drivers, every other game I've got runs as smooth as butter, both ones running in steam proton and ones running native. This is the only game where I really have framerate issues at all, so I don't think it makes sense for it to be a driver issue given that AoC is an isolated case. Unless theres something missing in bottles, or some setting somewhere that Im unaware of? I've been up and down this thread and can't find a solution.
I have not yet, I'll go do it as described in the OP and report back when I do. I might not get a chance to do so this evening though, so it may be that the results will have to wait until thursday given the usual downtime tuesday and wednesday.
Did you install a update for the Intrepid Studio Launcher before? If yes, it should be easy fixable.
What, why ever, happens during the launcher update is, in the registry the compatibility mode for webview gets changed from Windows 7 to Windows 8.1.
To revert this change, you can open up lutris, select the Ashes of Creation entry and then click in the bottom bar the arrow up, right of the wine glass. There you can open the registry and go to HKEY_CURRENT_USER\Software\Wine\AppDefaults\msedgewebview2.exe. Here you should find a entry named 'Version', which now most likely shows 'win81'. Simply change this to 'win7' and restart your PC. Then everything should be okay again.
I hope that helps you.
I ended up reinstalling the game but for sure I will keep this in mind if it will happen again. Reinstalling the game is quite time consuming. Thank!
When i had this problem under wayland, enabling a virtual desktop under graphics tab in winecfg fixed the whole black screen thing.
I recently stumbled across this post and tried to install everything according to the manual.
Everything works fine till the character selection screen, but If I choose my character and want to start the game, I only get a black screen and after a couple of minutes, steam is closed and the AOCClient.exe also closed.
Any hints?
EDIT:
Steam Deck & Bottles Config
I'll try the other way described in STEP 10 this week. Maybe it runs with the other config.
Will keep you updated
i encountered this by using the general lutris script for AoC, installing it and somehow it ends the launcher prematurely after the installer is supposed to start up.. when clicking finish, it just stops entirely.. how do i fix this?
In Flatseal add the following:
Now add AOCClient.exe to Steam, force compat to Proton Experimental, and adjust the launch options to the following:
I have the same error as melikootje.
Is there a solution for this?
Or is zopsi's post the solution?
These options are not available for me.
You guys followed the steps closely? I guess you guys didn´t set to GE-Proton or UMU in the runner options BEFORE the install.
It would be time-consuming but if necessary I'll try the flatpak.
However, at the moment, I have no possibility to adjust anything before the installation.
Ofc you can change before the installation.
I'm stupid or I don't play enough. I was looking in the wrong context menu.
It's installed now, but it quits after a few seconds.
I'll find that out though.
Thank you again for the information.
I tried that today, but the "Lauch Game" button still doesn't work for me. I have the latest laucher version and use Lutris with GE-Proton9-27 runner. Have you changed some settings and if so, which one exactly?
So, I'm running a latest Kubuntu, using Lutris. Decided to use GE-Proton instead of UMU-Proton, as I already had GE installed for a different game. Game installs fine, launcher launches perfectly fine, I didn't even have to launch AoC through Steam, the launcher's Play button worked just fine. I did notice some really bad stutters and heavy lag, but thought it was just the server being in the US, and me being in EU, no biggie.
Fast forward to today, I'm trying to launch the game launcher - instant crash, and Lutris shows this:
So I do what I always do - I reinstall, with the same settings as before. Now, though, it doesn't even let me install:
So I'm like, okay, whatever. I nuke the install from orbit, rm -rf the whole thing and start over. Same thing happens for like, 5 more installs, I re-nuke the install again and switch to UMU-Proton. Then...
A new challenger has entered the arena:
Traceback was useless, but what I gathered from the install logs was that the installer somehow managed to create a system32 file instead of a system32 folder, and was mightily confused by the whole thing, so it killed itself. Naturally, I nuke the install folder again, start over fresh, same thing for maybe three installs in a row. Then I read the logs more thoroughly, and I reset the permissions on the entire Steam folder, as it seems something went wrong there and Lutris couldn't access some files it needed. Alrighty, attempt number something. Nope, still same thing.
I start a new install, number 19. UMU-Proton, default runner settings, no tinkering, praying for the best.
Install goes through without a hitch, the launcher launches, I authenticate. Currently it's downloading the update, so I'll chime back later if it works or not.
EDIT: it worked, I've logged in, had to use Steam hook, no biggie.
Dogsh*t performance, stuttery 20-30 FPS on medium settings and native 1080p compared to smooth 60+ FPS on high in Windows (RTX 3060 Ti). Textures far too texturous, though that went away 5 mins later once they had a chance to load. Probably will delete the game and dualboot it in Windows, because this feels bad, really bad.
I managed to update the game on here which took a long time. Finally I tried to launch it and the launcher was OK. But using steam to load up AOCClient.exe seems to present me with an Error 31 message when trying to run ss or lsof. I think this is because the application hook from steam into the OS doesnt appear to be working now but if I put in the port number manually, it appears to work and show the realm OK.
After this, when I press play, the screen goes black and I now get a complete lock of the system. If I run this in a window, I may get a few pixels of mouse movement but after pressing play there is a massive system lock. Ill see if I have time to look at this, but i think it may be a debian config issue mainly or something else. .
And the only thing that changed was the game version and it seems that I changed the Proton version to the cutting edge Experimental of Steam. Normally I use Proton-GE9-27 but seems like I changed that at some point. Maybe you can try that as well. Atm I can't test if it also works with Proton-GE9-27 because the cloud service seems to be gone. When it's back online I will test it.
Just for the record: I use Nobara 42 and Lutris 0.5.19.
Same as mine
Bottles and steam via flatpak. vs just bottles.
Ok with steam the game loads, get to character screen and then crashes after 10 seconds (on a black screen). At this point I had a console open ready to kill the process which was hanging which I sent as soon as I saw the desktop lock up. So the system is still responsive but it is very very slow. You can issue one command on the console every 30 seconds and the mouse moves across one pixel at a time every 5-10 seconds.
Here are the processes when loading on steam:
Interesting here because I disabled the game overlay, it still wants to load it up. The process which is killed is the Win64=Shipping one so in the list it is process 3999 at the bottom.
The steam console logs dont show a lot:
Also, i was thinking because I always get error 31 when trying to load it from bottles, thinking that the application system hooks are not working to get the UDP port. So I ran it on there using purely bottles and no steam.
Now it looks like the UDP port is getting passed down and populated in the launch options, but there is still a timeout on the client that is not allowing it to connect. So this looks like that bottles is not providing something which can be used to connect but steam is providing something to allow it to connect but it still crashes.
Now this works OK on nobara but not on debian and this is what I have experienced on other distros too. So there is something definitively missing on an out of the box install that isnt nobara.
I dont really have time to look at this at the moment. but if I have a spare hour ill see if I can get some more logs out of the system.
The game crashing after 10 seconds reminds me of the bug I had, which was fixed by using -useeos=0.
Nowadays, I play on a Lutris and Steam combo without the two tags -NOSPLASH and -USEEOS=0.
Try it without those.
If that doesn't help, you can dig through the endless dependencies in Debian that might be causing the issue and update them. To avoid headaches in the future, it’s best to choose a distro that’s more suitable for gaming, one with a rolling release cycle or a semi-rolling release cycle. Arch, Fedora, and their derivatives are ideal for this purpose.
So it seems that the steam cpp code is using the default CPU scheduler which in the debian kernel is default with but it is using a spinlock system which the default scheduler of the kernel is not compatible with .
So I think a recompile with MuQSS is needed because the default one will not work. I guess this could also happen with other services because I think it is the game which is making the calls across the network.
It always comes back to the same issue: the kernel and the packages are simply too old. Why reinvent the wheel? For learning Linux is great, but for the average user here in the forum, it's better if they just use something that works without issues.
Anyone know how to fix this error? Direct X 12 not supported, I get it when trying to run the client exe.
I tried proton experimental an GE 9-4. I have a 7900XTX