Iv tried several cracks and updated Patch as well. 7 answers Last. Of the.exe choices? (there's one in Crytek Crysis Game Bin32 and Bin64). ![]() In my testing today. The Steam version of Crysis 1 runs really well with wine-staging 3.16 and DXVK 0.72 plus d3dcompiler_43 as native. Using the Nvidia beta driver 396.54.06 and a Geforce 970M (3Gb) card. So: winetricks dxvk72 d3dcompiler_43 Crysis is pretty playable in DX10 mode, at Very High settings, with this setup (testing with 2560x1440p). I've literally been waiting years for this game to run well under Wine! So thanks to Valve, and all the guys at Codeweavers! I haven't tested out Nvidia's env variables yet: __GL_SHADER_DISK_CACHE_PATH=. __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 Basically, because I wanted a before and after comparison. Hopefully Proton will get updated to the DX10 enabled DXVK builds - soonish? Crysis doesn't start with the current Proton release: 3.7-6. Just did a fresh install, got the license server issue the first time I tried to start it, after that the game launches to a black screen for like 1 second before crashing. I had the exact same result with crysis warhead. Oddly enough, when I tried to launch with a cracked exe file, the game would launch but hang instead of crash. I got the same exact behavior with crysis warhead, however when I tried launching 64 bit crysis the game launched if I disabled esync, and I could hear the audio, but there was no video lol. To run 64 bit crysis warhead, I replaced the bin32 diretory with the bin64 directory and renamed crysis64.exe to just crysis.exe for anyone who wants to try that. I heard that you can also execute the original crysis with the same binaries but I didn't try it. I got it working out of the box on proton on DX9 only (DX10/DXVK workaround below), performance is rather shoddy, getting 20-30fps on 980-Ti. But it works, and if you have decent hardware at the right resolution, works well. These are the launch options I needed. PROTON_NO_ESYNC=1%command% -dx9 Alternative launch options that also worked: PROTON_NO_D3D11=1 PROTON_NO_ESYNC=1%command% It works for both crysis and crysis warhead. (Update) to get around the license issue, there are two ways, the first one is to download a cracked exe file and run the game from that via steam once, you should then be able to replace it with the original exe without issue. The second solution; for anyone who has crysis warhead, is to replace the bin32 folder in the original crysis, with the bin64 folder from crysis warhead (possibly necessary: rename crysis64.exe to crysis.exe to launch from that), like with the crack solution, this only needs to be done once to work around the license issue, after which you can replace it with the original binaries again. As a workaround to run it with DXVK, using protontricks (alternatively can probably use winetricks) protontricks 17300 -q d3dcompiler_43 (Substitute 17300 with 17330 for crysis warhead) Winetricks alternative: WINEPREFIX=/path/to/steamapps/compatdata/17300/pfx winetricks d3dcompiler_43 It will still require PROTON_NO_ESYNC=1. For me, using DXVK gave me a 100% performance boost (from 20-30fps at high 4k to 50-60fps at high 4k) Tested on proton 3.16-1 beta. On DXVK, I can get 50-60fps at 4K/UHD with very high settings, if I set shaders to High. Setting Shaders to medium brings FPS up above 100 with an average of 120. ![]() There is however an issue with flickering shaders(?) on trees, extreme example: (it's usually not that bad, and only affects leaves normally, but here we can see it affecting a whle tree) The amount of flickering foliage can be reduced drastically by reducing object quality to high or lower, don't set it to very high or you will get flickering everywhere. I heard that there's a fix for this in the next nvidia driver update. Starboard fx-duo light sensor driver. How can I run the benchmarks? I want to impress people with my Linux pixel pushing power. E: DX9 performance is abysmal, how do I get DX10 working? I've even run winetricks d3dcompiler_43 on the prefix already, nothing. Are you sure you correctly installed d3dcompiler_43? Did you properly disable ESync? I only got a black screen before I installed the d3dcompiler_43 so you should always double check if you installed it correctly.
0 Comments
Leave a Reply. |