hauser
Published
5.9-GE-1-NR GloriousEggroll
If you alt-tab out of the game and return to the game, it is impossible to interact with the GUI anymore. While technically playable, for somebody like me it makes the game completely unplayable.
No amount of tinkering gets the game working
Installed DX9 from Anno 1404's folder using WINEPREFIX=/path/to/steam/steamapps/compatdata/33350/pfx/ wine /path/to/steam/steamapps/common/Anno\ 1404/DirectX/DXSETUP.exe and running the game with PROTON_USE_D9VK=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_NO_D3D11=1 %command%. None of it was successful. Tried all other possible combinations, including starting with Proton 4.11 and Glorious Eggroll's Proton 5.0. Removing and adding different launch options changed nothing.
The game is stuck at a black screen. Audio works, but no videos or menus are visible. Borked.
Use Wine D3D (OpenGL) instead of D9VK (Vulkan) to make it possible to minimize the game when it is fullscreen. D9VK also works, performance-wise likely better than with Wine D3D, but you won't be able to minimize the fullscreen game.
Use WINEPREFIX="/path/to/steamapps/compatdata/33350/pfx/" wine "/path/to/steamapps/common/Anno 1404/DirectX/DXSETUP.exe" to install DirectX 9.
Thereafter open the following file: /path/to/steamapps/common/Anno 1404/Engine.ini, and add the following line in between the <InitFile> tag: <DirectXVersion>9</DirectXVersion> in the file. Save changes and close the file.
The game runs slightly worse than on Windows, but not severely and is perfectly playable.
Proton-5.9-GE-1-NR
Forget the native port. It's outdated, and is most likely abandoned indefinitely. Download arma3-unix-launcher, it works with the Windows version even though it is not explicitly mentioned on its GitHub page. Launch the game through ArmA 3 Unix Launcher and enjoy your ArmA 3 experience.
Works exceedingly well with no tweaks required.
Scenario loading takes an unusual amount of time. Unknown if it's specific to Linux compatibility or if the same issue is present on Windows, but nevertheless scenarios and saves load a very long time.
5.9-GE-8-ST GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom
You have to use Glorious Eggroll's Proton. 5.9-GE-8-ST worked for me, but for instance 5.21-GE-1 did not. More versions might work, but these are the only two I tested.
You must disable DirectX 12 (PROTON_NO_D3D12=1 %command%) for the game to launch.
Proton-5.9-GE-8-ST
Fullscreen will stay on top until you exit the game
To make the game playable, make sure to follow the guides on how to disable mouse smoothing and increase the refresh rate from base 60 Hz: https://www.pcgamingwiki.com/wiki/Batman:_Arkham_City
Additionally, the game will not work at all with DirectX 11 features so you have to disable those in the settings (they are off by default).
Large Address Awareness was required to make the game load maps - otherwise it crashed to desktop. Disabling Esync prevented stuttering that was present in the game. After these changes, the game was completely playable, with no performance issues whatsoever.
Multiplayer was not tested.
Crashes at least half of the time whenever you start a game or even launch the game.
5.9-GE-6-ST
Looping. Go to game config files as reported below and reduce the number of audio channels to 16.
While the game does have a native port, it is completely worthless and meaningless, given that it doesn't support core feature of the game: multiplayer. Play the native Windows version instead using Proton, so you can actually play the game. Use the outlined tweaks and your game should work more or less fine.
Disabling Fsync significantly improves game performance.
In order to run the game, ROTON_USE_D9VK=1 %command% -width 1920 -height 1080 -nomemrestrict -norestrictions -percentvidmem 100 -availablevidmem 4096 -noprecache -novblank is requred as launch parameters. Even then, there are lot of skipped frames when moving quickly through Liberty City, which is somewhat irritating. Beyond that, the game works excellently.
In my previous report, I had noticeable issues with frame skipping, which detracted from gameplay to a small extent. That report was based on gameplay with GTX 1060, which I now replaced with an RT 5600 XT, and all the frame skipping is practically gone. It would seem like the game is inferior on NVIDIA's 440.xx drivers and performs better with a Navi 10 card running on Mesa drivers.
Same parameters as in my previous report make the game run properly: -width 1920 -height 1080 -nomemrestrict -norestrictions -percentvidmem 100 -availablevidmem 4096 -noprecache -novblank
In order to start the game, you need enable PROTON_USE_D9VK=1 and -h 1080 -w 1920 (or whatever the resolution of your main monitor is) to prevent stuttering and to have the game start visibly, instead of being a black screen. Subtitle and console fonts are slightly distorted, but legible. Beyond that, the game works exactly the same as on Windows.
It's difficult to escape from the window sometimes.
On Valve's Proton, it works abysmally (1-3 FPS) after the Iceborne expansion and its features have been launched. Requires Glorious Eggroll's latest fork of the latest Proton in order to work. Once that is done, it works at nearly perfect Windows native levels.
Nothing happens
Crashes immediately. Cannot see Nexon launcher.
The game would not start without enabling Large Address Awareness, and the game would not refresh correctly with Vulkan.
Proton-5.9-GE-5-ST
There are minor performance problems given my hardware, although it is unknown if that is a compatibility bug, or if it is that way natively on Windows too.
Works nearly perfectly
Fullscreen in the game produces strange behaviour. Softlocks every single time upon alt-tabbing when you alt-tab out of a menu or paused game. Use windowed mode instead, setting it to your screen's resolution, and use Alt + Enter to switch it to fullscreen: produces desired behaviour.
The game has a bit low performance, although it is unknown if it's particular to Proton compatibility or if the game is slow natively on Windows as well. Either way, other than the fullscreen issue (solved by running windowed mode), the game runs perfectly, both in singleplayer and multiplayer.
Plays as if it natively supported Linux
Steam overlay does not work exactly as it's supposed to, and that is the only issue I was able to notice about the game.
Possible to boot to menu, but gameplay won't start
Tried Proton-5.4-GE-3 and Proton-5.1-GE-2. Tried combinations of settings with both. Neither did anything.
Fails to launch. No options make it even boot up to the menu.
Does not work with Proton, and natively it doesn't work unless you use a command
LD_PRELOAD=/usr/lib32/libopenal.so.1 %command% must be used for the native version to work.
Virtually no difference between playing natively on Windows and running through Proton on Linux
Even on Windows, LAA helps with stability, especially with large cities. Not necessary in running on Linux per se otherwise.
-CustomResolution:enabled -r1920x1080x32 -intro:off are the launch parameters necessary with running the game at modern resolutions and disabling the intro. Additionally this article helps with improving the game regardless of which platform you are playing it on.
Other players also recommend enabling -CPUPriority:high -CPUCount:2, but for me it just made the game unplayable, so I left that out. In theory the game handles multi-threading poorly, and the aforementioned commands are meant to help with maximizing performance. Did not do anything for me, though.
Unable to download files
The launcher shows up successfully, and proceeds to perform some operations. However, despite extensive network activity and occasional disk I/O activity, the game never actually downloads any data, before eventually completely dying down. No processing, no I/O, no network activity; halts to a total standstill. Tried different Proton versions, but the result is always the same. No data is actually ever even loaded into RAM or disk.
Works nearly as well as natively on Windows
The game has <1 second freezes frequently, but I am unsure if that is particular to Steam Play experience, or if such a problem occurs natively on Windows as well. Outside of that, there are no outstanding bugs.
