https://bugs.winehq.org/show_bug.cgi?id=56014
Grigory Vasilyev h0tc0d3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |h0tc0d3@gmail.com
--- Comment #3 from Grigory Vasilyev h0tc0d3@gmail.com --- Everything works. And there are no such problems, although I had to compile lsteamclient, transfer patches from valve wine to load lsteamclient.dll, rewrite proton python script, proton manifest. Without the lsteamclient, your games will not be authorized by steam.
The problem you are talking about is caused by the default proton manifest in the toolmanifest.vdf file witch start wine in the steam linux runtime virtual container, container the complete isolated with your main system, and it loads only its own vulkan files, and there is support limited to X11.
To disable running the container before starting wine, you need to change the manifest to this form and remove all other json parameters.
``` "manifest" { "version" "2" "commandline" "/proton %verb%" } ```
You must also copy your dxvk files into the system and manual edit dlloverrides, unset DISPLAY, add fsync and stagging patches, edit registry with commands:
cd ${HOME}/.steam/root/compatibilitytools.d/GE-Proton9-1 export STEAM_COMPAT_DATA_PATH=${HOME}/.local/share/Steam/steamapps/compatdata/1100990 export STEAM_COMPAT_INSTALL_PATH=${HOME}/.local/share/Steam/steamapps/common/Aimbeast export STEAM_COMPAT_LIBRARY_PATHS=${HOME}/.local/share/Steam/steamapps export STEAM_COMPAT_CLIENT_INSTALL_PATH=${HOME}/.local/share/Steam
./proton runinprefix regedit
This example for Aimbeast game.
Thus, I recommend closing this bug report and it has nothing to do with CEF. And it is related to the specifics of how steam and proton work.