Iron-Wolf
Published
Used this link to set-up multiplayer : https://www.reddit.com/r/aoe2/comments/dwuplr/how_to_run_age_of_empires_2_definitive_edition_on/
TLDR : Download the file : https://aka.ms/vs/16/release/vc_redist.x64.exe extract it : cabextract vc_redist.x64.exe extract this file : cabextract a10 replace the file "ucrtbase.dll" in the folder : /steamapps/compatdata/813780/pfx/drive_c/windows/system32/
Audio cracking due to incorrect sample rate with pulse.
Fix it with : sed -i -e 's/; default-sample-rate = 44100/default-sample-rate = 48000/g' /etc/pulse/daemon.conf.old
To revert the change : sed -i -e 's/default-sample-rate = 48000/; default-sample-rate = 44100/g' /etc/pulse/daemon.conf.old
The massive stuttering (given my hardware) is seriously limiting the "average" gamer to have an enjoyable experience
Stuttering when loading new assets (and the game has a lot). Also, The game take ages to start (literally 1 hour on first launch). Those are minor issues, but it's a serious drawback for me.
Excelent game overall, with no issues in single palyer
I hadn't touched the game for several months and now the multiplayer doesn't seem to work anymore (it's worked perfectly before ! ). I can't host a multiplayer lobby (possible workaround with "PROTON_NO_ESYNC=1 %command%" but I have massive FPS drop).
Game starts but loads endlessly on the first screen (does not reach the menu)
Tried different version of proton and GE-8.25
I have never played before the modding tool update, so i cannot tell if the game worked before that.
The log shows an unknow exception (not verry useful).
I even tried to uninstall/reinstall...
Run perfectly with no major issues. I have just two (extremely) minors problems :
- The game starts in full screen, but the Ubuntu taskbar remain visible. I had to turn the full screen off and on again to get a real full screen.
- The game have some micro-freeze the first time it displays spark effects (like when you collect some gems or gold coins).
Besides that, the game run smoothly and the audio crackling I had in previous proton version has been fixed.
Game start and quit immediately
The "configuration" menu doesn't work from steam. I had to launch it manually with Wine. Once done (and the config file created) I get rid of the "graphic configuration" error. But the game crashes instantly.
I tried to lauch it with proton 5.0-9 / Proton GE 5.9 but without success. I also tried disabling ESYNC and use D9VK.
Run perfectly only on 4.x version of proton
after an Alt-Tab : could not go back in game. I need to reboot the game
Game not working with latest proton version (5.0-9) or with a modified one (neither 5.9 GE or 5.11 GE)
after an Alt-Tab : could not go back in game. I need to reboot the game
Game not working with latest proton version (5.0-9) or with a modified one (neither 5.9 GE or 5.11 GE)
Proton-5.4-GE-3 GloriousEggroll
Sprint key doesn't work 100% of the time.
Slow start time when launching the game. Spawn under the map when on trucks (multiplayer). Can land on the map, but with slow fps.
Shooting range OK
No problem. I had to disable V-sync (grass look pixelated and game freeze a little). Also, I have some keyboard binding that doesn't bind. Whereas the key is detected elsewhere in the game (like in the chat).
Sound does not work from scratch. I needed to change audio device.
Found the solution here : https://www.pcgamingwiki.com/wiki/Transistor#OS_X.2FLinux_audio_missing
TLDR :
- for me, the text file was here : ~/.steam/steam/userdata//237930/local/FMODDriver.txt
- modify the file with a single digit (you should use the command
aplay --list-devicesbut this didn't work for me, so I tested all the digits until it worked)
gamemoderun PROTON_USE_WINED3D11=1 %command%
After MANY attempts, using "PROTON_USE_WINED3D11" allowed me to play this game in its full glory.
Game launch but crash instantly when starting any mission (during loading time)
Used this launch option : gamemoderun PROTON_USE_WINED3D11=1 %command%
My previous report said it work well, but I hadn't started a mission...
I just wanted to play it again before SM2 came out, but I spent to much time tinkering with it. I don't know how to make it working on my setup and I won't dwell on it any longer.
