Lucho
Published
Completed the game, nothing blocking, but the experience was far from perfect.
On some parts of the game, experienced significant frame drops. It was solved by changing video settings (in particular, I changed shadows, either up or down...) and 60fps was restored.
Origin related annoying issues:
- Sometimes, like 50% of the time, Steam overlay does not start, so controller does not work. Had to restart the game a few times.
- I could invite a friend playing on Windows, inside the game, but had issues when trying the other way round (accepting an invitation), so you should invite.
Runs very smooth, feels like native. 60fps on 1080p, max settings.
On my AMD, I got a significant performance boost using RADV_PERFTEST=aco %command% as game launcher parameters.
Lot of tinkering needed, otherwise black screen and crash. After that, the game runs very smooth (1080p High, including cut-scene videos).
Proton-5.11-GE-1-MF
This was really difficult to make it work (it took me many hours). Here is the recipe.
- Gather 64 bit binaries from here: https://community.pcgamingwiki.com/files/file/257-crysis-64-bit-binaries/
- As stated there, delete (or rename to something else) the original Bin32 folder and rename the new Bin64 folder (extracted from the downloaded binaries) to Bin32.
- This will still make the game crash after a black screen. From my research, due to SecuROM protection. To fix this, download cracked rar package from here: https://www.playground.ru/files/crysis_origin_and_steam_64bit_fix-174316/
- From the downloaded rar file, extract just the file Crysis.exe (ignore everything else) and replace the Crysis.exe file located in the Bin32 folder.
On my setup, when V-sync was enabled the game would stuck at 24fps. This is also reported on Windows. To fix this, I added "%command% -dx9" as Launch Parameters, as suggested here: https://www.pcgamingwiki.com/wiki/Crysis#Game_uses_incorrect_refresh_rate Unfortunately, this means running the game in DX9 mode, which graphics are not as good.
This was really difficult to make it work (it took me many hours). Here is the recipe.
- Gather 64 bit binaries from here: https://community.pcgamingwiki.com/files/file/257-crysis-64-bit-binaries/
- As stated there, delete (or rename to something else) the original Bin32 folder and rename the new Bin64 folder (extracted from the downloaded binaries) to Bin32.
- This will still make the game crash after a black screen. From my research, due to SecuROM protection. To fix this, download cracked rar package from here: https://www.playground.ru/files/crysis_origin_and_steam_64bit_fix-174316/
- From the downloaded rar file, extract just the file Crysis.exe (ignore everything else) and rename it to something else like the CrysisSecuROM.exe file. Move it with the other binaries located in the Bin32 folder.
- Run the cracked binary with the following command "WINEPREFIX=~/.steam/steam/steamapps/compatdata/17300/pfx ~/.steam/steam/steamapps/common/Proton\ 5.0/dist/bin/wine64 CrysisSecuROM.exe". It will fail with an error, but don't worry. This exe will generate the securom ID you need to run the game everytime.
- Run "WINEPREFIX=~/.steam/steam/steamapps/compatdata/17300/pfx ~/.steam/steam/steamapps/common/Proton\ 5.0/dist/bin/wine64 regedit" to open the windows registry editor.
- Export the key [HKEY_CURRENT_USER\Software\SecuROM\basic64]. It should have an entry with a long id.
Now the game will run. However, it will delete that exported registry key every time you run the game. So you should re-import the .reg file you exported in step 7 every time before running the game. You can do that manually by opening the registry editor like in step 6.
Works flawlessly with recent update, except controller
With latest Steam Beta Client and Proton Experimental, game now finally works. Hope controller issue get sorted out (maybe just my setup?)
Feels like native (running 32-bit version)
Selecting 32-bit version on launcher solves the audio issue
To fix DS4 controllers (two) detection I had to fully disable Origin overlay. When its enabled, Steam overlay does not work neither Steam Input so no controllers are detected.
To disable Origin overlay, you need to open Origin using Proton, without running the game. This can be achieved with the following command:
STAGING_SHARED_MEMORY=0 WINEPREFIX=/home/luciano/Juegos/Steam/steamapps/compatdata/1426210/pfx /home/luciano/Juegos/Steam/steamapps/common/Proton\ 6.3/dist/bin/wine /home/luciano/Juegos/Steam/steamapps/compatdata/1426210/pfx/drive_c/Program\ Files\ (x86)/Origin/Origin.exe
Just replace with your Steam path were appropriate.
Completed the game without any major issues
In a few parts (over 20 hrs played) I experienced some notable frame drops. Lowering settings in those parts made it playable again.
As with all Origin games, Steam overlay sometimes does not work, so controllers does not work. Like 50% of the time. Should restart the game a few times until it works.
60fps on Ultra, at 1080p. Flawless experience.
Got through the hospital mission without any issues. DS4 worked perfectly on bluetooth (even hot-plugging after the game already started worked!).
Played co-op for almost 9 hours without any big issue, 95% of the time at 60fps
Sometimes, FPS drops to around 20 fps for around 5-20 seconds, then goes back to 60 ftps. Its happens occasionally, so not a big deal
As stated, character creation is broken (you cannot see the player on the menu), but I just selected the default options and started playing
Had to install MF from here https://github.com/z0z0z/mf-installcab in order to get it pass the intro video
After starting the game for the first time, it looked awful. This settings made it work perfectly, at 60fps, with max settings (except shadows):
- Shadow quality = High (Very High drops fps a lot)
- Render method = Normal (Interlaced looked awful)
- Refresh rate = 60 hz (default was 24hz)
- Scale resolution = 1.2 (or 1, if you experience frame drops)
Platinum experience, if texture and shadows are set to Medium.
Some settings made FPS suddenly drop a lot making the game unplayable, but not sure if it's my hardware, a game issue (in some forums, Windows players experienced similar behavior) or Proton. To achieve stable 60 FPS at 1080p on my hardware, I set everything at max, except for:
- Texture Quality = Medium
- Shadow Quality = Medium
- Shadow Cache = Off
- Ambient Occlusion = SSAO (variable)
- Subsurface Scattering = Off
Finally, make sure to set Render method = Normal, otherwise Interlaced looks awful.
Unfortunately, performance problems, specially after resuming from pause menu makes the experience frustrating :(
DS4 not detected over Bluetooth. Via USB it worked fine. Hot-plugging in-game also not working. As my controllers over USB would sometimes disconnect due to cable issues, no hot-plugging + no Bluetooth is a deal breaker for me.
FPS drops a lot, in particular after resuming from pause menu
It's playable, but performance problems are frequent, so the experience is not the same as on Windows unfortunately (yet).
Proton-5.21-GE-1 GloriousEggroll
Entering new zones drops FPS a lot for around 30 seconds or more. Pause menu also drops performance. In general, FPS were lower than on Windows on the same machine.
- GloriousEggroll is needed for intro videos (and probably in-game views in the skills tree).
- Strangely, for DS4 to work over Bluetooth I had to FORCE Steam Input enabled on game-specific settings. Otherwise, it would not be detected.
- Upgrading from Ubuntu's default Mesa to latest stable Mesa (20.3.2) made the game performance increase enough to make the game playable on my AMD GPU.
Worked perfectly out of the box, with 2 controllers and max settings.
Running Config shows some windows error, but you can continue and it works as expected. Didn't need to install dotnet. Also, I did not experience any crash with v-sync on as other had reported.
Disabling Esync was needed to prevent important audio issues
Tested with 2 gamepads locally, controllers mapping bug make it very annoying to play. Single player/keyboard may be perfect.
When playing with 2 players with 2 gamepads, a third player (or even a 4th) would appear and one of the gamepads would control 2 players at the same time. Also, sometimes we experiences as if a gamepad was with a pressed button all the time, specially in the menu, which was very annoying.
Works perfectly, except a few crashes, not a big deal
2 crashes in about 3 hours of gameplay
Feels like native. Out of the box, flawless experience on 1080p (Max settings)
Just ~5 FPS less than on Windows (1080p, Max)
I tried adding "RADV_PERFTEST=aco mesa_glthread=true %command%" as launch parameters due to other reports recommendations, but couldn't notice any difference.
Completed the game without issues
Two things to take in mind:
- The game goes minimize itself on startup, but alt-tabbing into the game window maximize it again, so no problem.
- Sometimes Steam overlay does not start, so controller does not work. Like 50% of the time... Should try again a few times until it works... This happens to me in all Origin games, so not a Titanfall specific problem.
