PLATON
Published
You need to use compatibility mode (Proton) to play this game without any problems. There is also a native Linux version, but you should know that on the native verison there is a problem with achievments (they just not working AT ALL) and on playground level (where you need to use a tire to open a chest) there is no tire on the tree! There was a glitch: you can see the rope, but you can't see the tire on it. So, if you play this game on Linux (just as I did), then you need to run it with compatibility tool (Proton) and everything will be great. With that option you can get all the achievments and complete the game with no problems
PROTON_USE_WINED3D11=1 %command%
When using any current version of Proton without specifying launch parameters, it was possible to launch only the game launcher and go into the settings, but when starting the game itself, it immediately crashed without specifying any reason and the launcher appeared again. In the end, I just added launch parameters (PROTON_USE_WINED3D11=1 %command%) and everything worked as it should - the game runs smoothly and I didn’t notice any bugs. I used GE-Proton9-2
In some cases, you may need to enable the "Above 4G Decoding" option in the BIOS (see text below)
Guys! If you (just like me today) tried to launch this game and received errors like this one:
"Wine C++ Runtime Library
Assertion failed!
File ../dlls/winevulkan/loader_thunks.c"
Line: ____
Expression: "!status && "vkCreateGraphicsPipelines""
...then keep the following in mind - after many hours of torment with launching with different versions of Proton and a bunch of parameters, I solved my problem this way:
- If possible, update your version of Linux.
- Restart your computer and go into UEFI BIOS.
- Find and enable the option called "Above 4G Decoding", save BIOS settings and reboot PC again.
- You can launch Steam, and then the game itself - now this error should not appear.
And now (if you are interested) I will explain a little what was the matter. Errors like "vkCreateGraphicsPipelines" indicate that the problem occurs during the compilation of shaders via Vulkan. And it is not so important whether you have the preliminary cache enabled in the Steam settings or not. The problem arose after updating rolling-release distros (I have EndeavourOS) in mid-May 2024. If you have Linux kernel version = 6.8.8 and earlier, then the game (like other games on Unreal Engine, such as Street Fighter, etc.) will launch without this error. But on kernel version 6.8.9 and newer, many people experience this error at startup. Most likely, this will be fixed soon, but in order not to wait for this moment, one of the users found a solution to enable this option ("Above 4G Decoding") in the BIOS - it is harmless for the average user, I think. I turned it on and the game started without any problems. And without it, I spent the whole day fruitlessly trying to launch the game somehow. Nothing else helped (believe me, I tried a LOT of options...) But now the game works.
PROTON_USE_WINED3D11=1 %command%
I don’t know how the game works on other versions of Proton (since I immediately launched it on Proton GE 9-2). But without the specified launch parameters, the game did not start for me, but immediately crashed without specifying any reason. As soon as I specified the launch parameters, everything immediately worked as it should.
Just use Proton 7.0-6 and a couple of launch parameters in this game and everything will be OK
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 DXVK_ASYNC=1 gamemoderun PROTON_USE_D9VK=1 %command%
When using any new version of Proton (including Proton GE 9), I had constant graphic artifacts. When the game name appeared before the main menu, the graphic effects were distorted (glitches and artifacts) and there were lighting distortions in the game itself. No options or launch parameters helped. In the end, the problem was solved simply: I launched the game with the specified launch parameters and with the old version of Proton (7.0-6). After that, everything returned to normal and all the artifacts disappeared.
There were stutters in the first chapter, then performance improved
The solution to the problems is simple: Proton 7.0-6 and these launch parameters:
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 DXVK_ASYNC=1 gamemoderun PROTON_USE_D9VK=1 %command%
There will probably be stutters in the first chapter, but after a while there will be much less of them and you will be able to play without any problems. I did not install any unofficial fixes, mods or anything like that. Just the "vanilla" version from Steam.
Newer Proton versions did not work as expected for me. Proton GE 9.2 did not allow me to enter the game (there was a total freeze on startup with a black screen). Proton 8.0-5 allowed me to enter the game menu, but when I tried to start a new game, the app closed by itself. The same thing happened with Proton Experimental. In the end, I just chose the Proton 6.3-8 option and everything worked as it should: the game runs without any problems (all FMVs also play correctly). Totally playable without any problems now.
WINEDLLOVERRIDES="d3d9=n,b" %command%
The game works fine on the latest versions of Proton, but by default the game only has a 4:3 screen mode. To get the 16:9 mode, you need to download "ThirteeenAG's Widescreen Fix" for GUN (https://github.com/ThirteenAG/WidescreenFixesPack/releases/tag/gun). To install it, you need to copy the contents of the archive to the game folder, and then in the game launch parameters in Steam you need to specify the following: "WINEDLLOVERRIDES="d3d9=n,b" %command%" (without quotes).
Another important point (it concerns both Linux and Windows) - in the game graphics settings, set the "Advanced Graphics" parameter to "low" and everything else to high. Yes, it sounds strange, but the textures in the game are so amazingly made that it is precisely at the low settings of this option that the game looks best (and as intended). If you set this parameter higher, the character textures become "soap mush". Just compare both modes in the game, and you will understand everything yourself. Well, in general, it's up to you.
If the native version of the game does not launch, then simply launch it from the Steam (Runtime) instead of Steam (Native)
If you, like me, could not launch the native Linux version of the game when trying to launch it (the game just immediately closed without indicating errors), then just do the following. Check which version of Steam you are using: Steam (Native) or Steam (Runtime). When you install Steam on Linux, you always get both of these versions of the application. I usually use the Steam (Native) option everywhere, but the game did not launch in this form. Then I just launched Steam (Runtime) and the game worked right away without any problems. Everything turned out to be simpler than I thought.
Everything works great right out of the box. Even though I didn't make any changes to the config files
PROTON_USE_WINED3D %command%
Terrible stutters during the cutscenes. No. Not just "stutters". "STUTTERS!!!!!!"
Periodically, the game just stupidly closed without any indication of an error. Because of this stuff, I had to go through certain levels again. The game itself was closed at the end of the episodes, before the launch of cutscenes. And this is terrible, because there is simply no normal save system in the game - the game is saved only AFTER those cutscenes, i.e. exactly when the game crashes. I had to go through some levels because of this...
Many Resident Evil games are made on the old MT Framework engine, and therefore they have the same problems - terrible stutters when running on Linux via DXVK. The worst is Resident Evil 6, where stutters in cutscenes are simply incredibly annoying and break the game. And it doesn't matter which Proton you use - there are problems everywhere. But in the case of GE Proton, at least you don't have to install wmp11 codecs manually, because in GE Proton, the video in the game works by default. Nevertheless, there are terrible stutters everywhere. But there is still a solution.
You need to force the game to launch using (outdated) OpenGL instead of DXVK. That is, you need to do the following: 1) use GE Proton 2) specify the launch parameter: "PROTON_USE_WINED3D %command%" - this way the game will launch using regular Wine's OpenGL instead of DXVK. If you use SteamTinkerLaunch, you can enable the same option by checking the box next to "Proton use WINED3D" in the "GAME MENU" in STL (I also recommend checking the boxes next to "Dxvk async" and "Game mode"). In my case, using OpenGL in games on this engine helped to get rid of ~ 90% of stutters and glitches in the game. It's a shame I discovered this option so late.
PROTON_USE_WINED3D %command%
Constant stutters that made the game unplayable. See below for how to fix this.
Many Resident Evil games are made on the old MT Framework engine, and therefore they have the same problems - terrible stutters when running on Linux via DXVK. The worst is Resident Evil 6, where stutters in cutscenes are simply incredibly annoying and break the game. In RE Revelations 2, the problems are similar. And it doesn't matter which Proton you use - there are problems everywhere. But in the case of GE Proton, at least you don't have to install wmp11 codecs manually, because in GE Proton, the video in the game works by default. Nevertheless, there are terrible stutters everywhere. But there is still a solution.
You need to force the game to launch using (outdated) OpenGL instead of DXVK. That is, you need to do the following: 1) use GE Proton 2) specify the launch parameter: "PROTON_USE_WINED3D %command%" - this way the game will launch using regular Wine's OpenGL instead of DXVK. If you use SteamTinkerLaunch, you can enable the same option by checking the box next to "Proton use WINED3D" in the "GAME MENU" in STL (I also recommend checking the boxes next to "Dxvk async" and "Game mode"). In my case, using OpenGL in games on this engine helped to get rid of 90-95% of stutters and glitches in the game.
On the latest versions of Proton (I first used GE-9.2), the game starts and you can navigate the menu, but when you try to start any match or connect to the server, the game immediately closes. The only version of Proton with which this problem completely disappeared is the standard Proton 4.11-13. After I selected it, it became possible to play without any problems. I don't have any problems with full-screen mode or stutters or anti-aliasing, like some others have.
