Newbyte *gurka.se
Published
Works excellently.
Once crashed when tabbing in and out, however during my time playing the game it only occurred once.
Every time the game is launched it runs the script for installing .NET framework
Works well, once it launches.
No audio in cutscenes whatsoever. This can sort of be remedied by enabling captions. Audio in menus and in-game dialogue play just fine though.
Game often crashes on startup, but once you're in it seems good to go.
D9VK works well, read it fixes some graphical glitches and I can only assume gives better performance so I didn't even bother trying WineD3D
I had to add the -forcestereo flag to the launch options or no cutscene audio would play. Might have to do with that I'm using a 5.1 sound system.
As previously noted I had to add a launch option to get cutscene audio working.
Frequent crashes on startup, however once the game is running it never crashed on me.
I added WINEDLLOVERRIDES="xaudio2_7=b,n" %command% to the launch options of the game. Works around issue where audio only sometimes is present when launching the game.
By default, the game's audio only occasionally works properly. Usually you either get cutscene audio or in-game audio. A workaround that makes audio work consistently is adding WINEDLLOVERRIDES="xaudio2_7=b,n" %command% to the game's launch options. After inserting that the game works perfectly.
It was unable to determine USB support and thus couldn't verify whether the headset's camera would work.
By default it'll tell you that your OS is too old (Windows 7), but it shouldn't really make a difference as this check is only done by querying this information from an API. Changing the reported Windows version via winecfg to Windows 10 makes this go green.
Symptoms
Game defaulted to exclusive fullscreen which crashes the game on launch.
The game opened up on my right monitor and did not want to be moved.
Solutions
I didn't attempt to manually set it to use fullscreen while in-game, however windowed mode (both borderless and borderful) works okay.
In order to make it run in a borderless window I had to edit the file <steamapps>/compatdata/208650/pfx/drive_c/users/steamuser/My Documents/WB Games/Batman Arkham Knight/GFXSettings.BatmanArkhamKnight.xml
In it, I changed Display_Mode from 2 to 1. 2 means exclusive fullscreen, 1 means borderless window.
Regarding moving the window, I was able to make it show on my main monitor by making it run in a borderful window, move it to my main monitor, and then go back to borderless fullscreen.
Performance is mediocre compared to Windows 10. I didn't test very thoroughly, but initial results showed a definite degradation. Make sure to use esync (on by default), as without it performance is atrocious.
Crashes if game is started in exclusive fullscreen.
The game seems to think that it is pirated, so the grapple is disabled making the game impossible to play.
Symptoms
Game defaulted to exclusive fullscreen which crashes the game on launch. Note that this might be due to my Steam Cloud having settings from when I played this on Windows. The game also works fine in fullscreen once in game.
The game opened up on my right monitor and did not want to be moved.
Solutions
I didn't attempt to manually set it to use fullscreen while in-game, however windowed mode (both borderless and borderful) works okay.
In order to make it run in a borderless window I had to edit the file /compatdata/208650/pfx/drive_c/users/steamuser/My Documents/WB Games/Batman Arkham Knight/GFXSettings.BatmanArkhamKnight.xml
In it, I changed Display_Mode from 2 to 1. 2 means exclusive fullscreen, 1 means borderless window.
Regarding moving the window, I was able to make it show on my main monitor by making it run in a borderful window, move it to my main monitor, and then go back to borderless fullscreen.
See customisation section.
The frame-pacing is significantly worse than I remember it in Windows. I suspect this might be due to a lack of driver-level optimisations. Overall, it's playable, but while I could play it at 1080p mostly maxed out in Windows, in Linux I have to turn down the settings (which barely improves performance, but it makes it slightly more playable).
See customisation section.
Native version can't play co-op with people on Windows right now (hopefully this will get resolved), so I decided to give the Windows version a shot. I put some launch arguments and renamed the launcher as previous contributors suggested, and the game ran almost flawlessly -- save for some minor graphical glitches such as, but not limited to, the water lacking any form of texture. It also crashed one of the times that I tried to join a friend, but following that I didn't have any issues doing so.
Performance was slightly worse than Windows (though very much playable), and since BL2 only runs using DX9, it can't use DXVK unfortunately. I tried forcing D3D11 by editing WillowEngine.ini, but no dice. Seems to have made no difference whatsoever. Attempting to enable OpenGL in the same file made the game crash on startup.
Initially the game will crash upon opening. To work around this, rename BorderlandsGOTY.exe to Launcher.exe.
However, even with this, the game stutters throughout the intro films and froze once Claptrap walked up to me. Enabling D3D10 in WillowEngine.ini made the game freeze before getting to the main menu, in addition to great slowdown and stutter during the logos shown when starting up the game.
Game itself works seemingly perfectly, however if I play in "Maximized" (full-screen window) mode a small part of the bottom of the game's content is cut off. This seems to be an issue with the game itself, as it runs with a fixed aspect ratio, and resizing the window to fit your screen by yourself results in stretching that doesn't look all that great. I can imagine that the "Maximized" mode might work better on a desktop environment that allows you to put any window in full screen.
You can, however, run the game in a 1X, 2X, or 3X window (meaning times the amount of pixels on the Y- and X-axis as the game renders) where nothing is cut off, but this results in a fairly small window on even a 1080p monitor; I can only imagine how tiny it must be on something more high resolution.
Despite this, I'll still mark it as Platinum since these issues seem to be caused by the game itself rather than Proton.
Company logo appears on the right side of my main monitor, then the game crashes
As of Proton 4.11-2, this game now seems to be fully playable! There is one caveat, however: no music. Unfortunately this probably won't get resolved any time soon due to Microsoft's patents.
Runs almost perfectly
I seem to have noticeably higher input lag on Linux compared to Windows, but still definitely playable.
My Steam status is briefly set as playing "Defy Gravity", but soon reverts to "Online" and no window appears.
Game froze to a black screen after accepting terms
The game was maxing out all of my CPU cores while in the black screen, but even after waiting a few minutes I got nothing. Killing it required a sigkill; sigterm had no effect.
The description says something about "desktop pet", but the thing seems to be in a dark void. I've no clue if it works differently on Windows.
All graphics presets are labelled "ERROR", but you can still set the graphics settings indiviually. That aside, it works perfectly.
Upon starting the game you will see a tiny, black, window. To get some form of display you need to enter fullscreen via Alt + Enter, after which the game runs about perfectly. Be careful with hitting F5 though, as this changes the display mode and creates some pretty weird visual glitches on your desktop until you exit the game or get back into fullscreen. Another noteworthy issue is that you have to use your keyboard (tab, space, etc.) to navigate the settings as their popup window isn't focusable with the mouse.
I did the workaround detailed below
Game crashed once when respawing.
Gameloft logo appears and swiftly progresses to displaying the loading screen, but after that the game gets stuck at around 10% of the progress bar and crashes.
On startup an error message appears, and after closing it the game does too.
All right, this game can run almost perfectly without any .NET or other rubbish, there's just one quirk (at least in my case): you need to convert the WMA/WMV files to Vorbis and Theora. Thanks to the FNA creator flibitijibibo, there is a script that does this for you (as long as it is run in the right location, in the case of this game the game's "Content" directory). It can be found here: https://gist.github.com/flibitijibibo/c97bc14aab04b1277d8ef5e97fc9aeff
Note that this script assumes that you have ffmpeg compiled with WMA/WMV support (which it is on many distributions) and bash installed on your system.
Now, does it run flawlessly after this is done? Actually, mostly yes. I played the first two levels and challenge levels. The audio right at the start of each level sounds a bit off to my ears (that might just be how the game is set up however), but aside from that I noticed no audio nor video issues whatsoever. The fullscreen toggle seems to be inverted, that is, ticking the fullscreen box disables fullscreen and unticking it enables it, and for me there is a tiny black bar at the top of the screen when in fullscreen, but the issues end there.
Disabling Esync does get you a bit further (the launcher disappears and game actually goes fullscreen), but using Wine D3d11 seems to have done nothing. Same goes with disabling D3d11.
Plays more or less perfectly
According to someone on GitHub the pause menu keeps opening when his controller is connected and there's artefacting along the sides of the screen, but it was nothing I noticed. I do not own any controllers to test with so I cannot verify whether it happens for me.
Works great, with some issues that shouldn't bother
While the game does play really well, there are some issues. Enabling hardware acceleration makes the game go from a smooth, stable, 60 FPS to moving around between 10 and 20 FPS. This may very well be the case in Windows too however, I do not know.
Another issue is that the Try Peggle Deluxe button does nothing. Not a huge issue though.
5.6-ge-2-planet-zoo-1 GloriousEggroll
Game-specific build of Proton I uploaded for convenience here: https://github.com/Newbytee/Protonbuilds/releases
Clouds look funky when using my Vega 56 with Mesa 19.2.8, but are fine when using my GTX 970 with nvidia 440.82.
I have tested this very little. There may be crashes.
The music picker didn't work. It would open the Wine filepicker with what appeared to be a filter for images and mp3 files (FLAC audio did not appear), however I was unable to select anything as doing so made it open in Wine's default program for said filetype.
5.6-GE-2 GloriousEggroll
Using this release of Proton GE, intro films and music play! https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.6-GE-2
You need to tab in and out in order to be able to skip intro films and raise building above land (via shift) if you're using DXVK.
There is some stutter in menus and in-game, but the latter might be due to shaders compiling. I did not play very long.
Many of the game's issues, such as not being very willing to run in widescreen, are present on Windows too.
Game does not launch. Status on Steam briefly says that I'm playing the game, but then within a second reverts back to online and no game appears.
Sometimes, seemingly after tabbing out, the mouse and escape button stop working in-game. Restart fixes it, and only rarely occurs when tabbing out/in.
I played the first two levels, singleplayer and multiplayer. No issues whatsoever (aside from that multiplayer didn't work via the Steam overlay, but I think that issue is in Windows too).
It seems that with Proton 4.2-3 a window opens containing some form of crash report. It closes very swiftly, though, however Steam still thinks that the game is open and you have to close it yourself (via htop or similar).
I had Geralt's torso go transparent when wearing a certain armour and Vivaldi's arms do the same
On rare occasions the game would start up to a black screen or not start at all. Restarting Steam solved this those times. It would also very occasionally get stuck in a loading screen and load forever.
Runs like native
I noticed that someone here noted that performance is bad and blamed this on Proton. A few years ago I played this on Windows, and I can assure you that performance is just as bad there. As long as you're using DVXK the performance degradation will be minimal.
As of Proton 4.11-4, this game seems to work great even with D9VK (in previous versions it would have severe graphical glitches)! Can very much recommend using it as it increases my FPS significantly over WineD3D.
Runs well
Game froze once when building a house. This might have been a game bug though.
Online features, like downloading custom skins, did not work. Achievements worked, however the ones that were things like "die 100 times" or "run 100 000 metres" did not show any progress in Steam's Achievement view. Not sure whether that's an issue with the game or Proton.
On first launch I got some DLL error when upgrading Uplay. This might just be an issue with how old the version of Uplay this installs by default is though, but I'm not sure. It worked fine on the second launch though.
Initially Steam would get stuck on setting up .NET after switching to Windows XP via winecfg and installing xact_64, but a restart of Steam did the trick. After that, I was able to launch the game. Performance seemed all right at first, but after a bit of running around it plummeted from 25-60 FPS to around 10 FPS. Not entirely sure what caused this, as it would, on occasion, raise back up to its former levels when standing in specific spots and looking at specific angles, but regardless I ended up turning almost everything down to the lowest settings (except resolution, anti-aliasing and level of detail, 1080p, temporal SMAA (I think) and highest, respectively). At these settings the game performed well however. Getting it to display in fullscreen on my main monitor was a bit tricky though as it kept wanting to place itself on my rightmost monitor rather than my leftmost one. I ended up having to turn the game off, disable the rightmost monitor, and then re-launch it as otherwise it would somehow re-active my rightmost monitor and disable my leftmost one if I changed the monitor settings while still in-game. When it did this it would also produce very weird graphical glitches in GNOME (note that this last part occurred when I used registry tweaks to achieve exclusive fullscreen which Proton disables by default).
