Compatibility Report

I seem to have the same problem:

System Information

• GPU: RTX 3060TI
• Driver/LLVM version: 470.63.01
• Kernel version: 5.14.5-1 (Manjaro Linux 21.1.4 [XFCE])
• Link to full system information report as Gist:
• Proton version: Proton Experimental (the same thing happens also with 6.3-6 / 5.13-8)

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

Game doesn't start and silently exits which was tested with Proton Experimental / 6.3-6 / 5.13-8.

Reproduction

Try and start the game from the steam launcher:
steam-1715130.log

sadly it also does not run for me
steam-1715130.log
someone posted a similar bug here i guess: https://github.com/doitsujin/dxvk/issues/1773

Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.10.66-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7600K CPU @ 3.80GHz
Memory: 23,4 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2
NVIDIA: 470.63.01

Needs winetricks vcrun2019 and d3dcompiler_43. Worked after adding them. Specifically these dlls:

mfc140u.dll
d3dcompiler_43.dll

Needs winetricks vcrun2019 and d3dcompiler_43. Worked after adding them. Specifically these dlls:

mfc140u.dll
d3dcompiler_43.dll

Nice find! It instantly started when I used winetricks vcrun2019.

I somehow had big problems getting protontricks to run but after multiple retries this is what worked for me:

# I switched in Steam to Proton 6.3 and deleted the old prefix and then let steam recreate it once
# --force was necessary because there was a SHA mismatch
$ PROTON_VERSION='Proton 6.3' protontricks --verbose 1715130 --force vcrun2019

The performance is sadly not on the same level as the original Crysis via Proton but it 100% runs without graphical or audio glitches (at least in my first 15 minutes of playing the campaign).

Thanks, I can confirm that installing vcrun2019 through protontricks worked for me too

Switched to proton 6.3, installed vcrun2019 d3dcompiler_43, worked. Closed game. After that it refuses to launch again.

thanks GE and AnonymerNiklasistanonym

"protontricks --verbose 1715130 --force vcrun2019"

did the trick now it runs :+1:

protontricks --verbose 1715130 --force vcrun2019 works but the game stutters like hell. Anyone else with this experience?

Edit: Seems to run a little better in Gnome with X.Org. I'm currently running Sway. I couldn't really test it in Gnome with Wayland (my screen kept flashing...)

protontricks --verbose 1715130 --force vcrun2019 works but the game stutters like hell. Anyone else with this experience?

Edit: Seems to run a little better in Gnome with X.Org. I'm currently running Sway. I couldn't really test it in Gnome with Wayland (my screen kept flashing...)

Runs great for me on my RTX 2080TI on Ubuntu 21.04.

it is fixed in the latest GE-Proton
https://github.com/GloriousEggroll/proton-ge-custom/releases

I tried all the solutions mentioned but the game won't launch. I used "protontricks --verbose 1715130 --force vcrun2019" and Proton-6.18-GE-2 but nothing changes.

Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.7-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2

Nvidia Driver version?

Nvidia Driver version?

Nvidia: 470.63.01

I tried all the solutions mentioned but the game won't launch. I used "protontricks --verbose 1715130 --force vcrun2019" and Proton-6.18-GE-2 but nothing changes.

Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.7-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2

Nobody will be able to help you if you don't post the steam log

Sorry, I didn't know how to do it.
steam-1715130.log

Sorry, I didn't know how to do it. steam-1715130.log
i think these are the problems in your log

50328.604:0108:010c:err:wldap32:DllMain No libldap support, expect problems
50333.013:0108:010c:err:module:import_dll Library mfc140u.dll (which is needed by L"Z:\home\aldo\.local\share\Steam\steamapps\common\Crysis Remastered\Bin64\CChromaEditorLibrary64.dll") not found

try installing libldap and lib32-libldap

and for the other error maybe this can help you
https://steamcommunity.com/app/221410/discussions/0/1629664607002719357/

try installing libldap and lib32-libldap

I had libldap and lib32-libldap already installed.

and for the other error maybe this can help you https://steamcommunity.com/app/221410/discussions/0/1629664607002719357/

Thanks for the link, I will try that later.

Pretty sure that this shouldn't be classified as a Proton issue. Some Windows users have this exact issue and installing the VC2019 runtimes fixes the problem.

https://steamcommunity.com/app/1715130/discussions/0/4943253385008747798/

The game doesn't check for or install the VC2019 runtimes on first run.

Is there any way to play this game with hardware Ray Tracing? The Experimental RT Boost slows the game. I use a RTX 2070.

Replying to https://github.com/ValveSoftware/Proton/issues/5165#issuecomment-1085871022

Sadly does not work. The game doesn't start. How does this go with the separate dxvk.conf?

Edit:

Here's the log:
steam-1715130.log

Replying to https://github.com/ValveSoftware/Proton/issues/5165#issuecomment-1085890451

Still doesn't start. :\ Also tested it with Valve's Proton 7.0 but it's the same.

steam-1715130.log

Can you also post a log without the commands and the conf file where you are able to launch the game?

Sure, here you are. :)
steam-1715130.log

Okay so these two lines stick out when you try to launch the game with the nvapiHack disabled.

err:   D3D11Device::CreateFence: Not implemented
err:   D3D11ImmediateContext::Signal: Not implemented

So i can see the game is Directx 11 but they have plucked some vulkan extensions and added them to the game for ray tracing if i understood that correctly? Not sure hehe. Is a bit confusing.

If you want to try and hunt this at bit you can try opening a issue at the dxvk repo and see if they can help with the crashing.
Tho again i dunno if it would work even if you got it running with nvapi.

All right, thank you anyway! :)

Vroom vroom!
I see the gamemode command has been included into GE, so maybe that helps your system if you didnt already use it (but had it installed ofc).

Perhaps the hardware raytracing will be possibly some time in the future.

A small more or less OT question: Is there any way to run the Benchmark.exe in this Proton?

Is it a seperate exe not launchable from within the game?
If it is i guess you can add it as a non steam game in proton compatability mode.

Is it a seperate exe not launchable from within the game? If it is i guess you can add it as a non steam game in proton compatability mode.

It is a standalone exe. But thanks for the tip with the "non steam game".

Guys with last Proton 8 not load GameObject inside of game

@AgostinoA Hi there. Could you be more specific of what the issue is? Is it a game error and does it happen with 8.0-3?

Sorry, I wrote superficially. The game does not load models or shaders properly.
This happens with both Proton 8.0-3 and Proton Experimental. Instead with Proton 7 and earlier everything is fine.
Also Proton 8.0-3 takes longer on startup times on all titles, sometimes hangs on some Wine processes and makes games appear to be running, when in fact they haven't started. You are forced to force all the Steam processes to restart any other game and attempt a subsequent start 3/10 open, this is very strange.
For the launch attempts of the titles, I tried to cancel all steam, but the problem is the same

My system:
CPU Brand: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Kernel Version: 6.2.14-nebula
Driver: NVIDIA Corporation NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 535.54.03

Ubuntu 24.04, NVIDIA GeForce 3080. Only a single monitor connected.

107542.069:0124:019c:err:x11drv:X11DRV_GetCurrentDisplaySettings Failed to get L"\\\\.\\DISPLAY2" current display settings.
107542.074:0124:019c:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2.
107542.074:0124:019c:err:x11drv:X11DRV_GetCurrentDisplaySettings Failed to get L"\\\\.\\DISPLAY2" current display settings.
107542.076:0124:019c:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2.
err:   DXGI: EnterFullscreenMode: Failed to change display mode

Refuses to start.