![]() ![]() Please, nobody facepalm yet □ since for others it might be a different issue. Also, other games work fine, it's specifically Dishonored 2 that broke.Īs noticed as well, I saw Steam download an update for Dishonored, after which it stopped I managed to get Dishonored 2 working again by. I have a AMD GPU, so the drivers are mainlined. I have the exact same issue as (and as well). I don't think either of that is the case. ![]() It looks like you have broken Steam installation. Even still, if you are using the DKMS drivers (which you should )), they will be automatically linked against the new kernel when it updates. That only happens with out-of-tree Nvidia drivers. ![]() It happened to me when I got kernel update and didn't reinstalled drivers, some games stopped working. Minor changes in kernel can make GPU drivers works partially. ![]() I too had this sitting in my backlog hoping to play again if your kernel was updated and your GPU drivers were not recompiled for it, then there is possibility that something is not working. Proton-7.0rc2-GE-1: Unofficial non-Valve build, causes a WINE segfault, doesn't work.Ĭommand: /home/rob/.local/share/Steam/steamapps/common/Dishonored2/Dishonored2.exe DXVK_ASYNC=1 PROTON_NO_WRITE_WATCH=1 PROTON_NO_ESYNC=1 +com_showLoadingScreen 0 Proton-6.18/.20-GE-2: Unofficial non-Valve builds, but neither work. Also, it said "Validating" on the Library page. I noticed today that Dishonored 2 was downloading something, but there's no new patch/update or repo change. Proton 6.3-8 is what was working without issue for me before, not sure what could have changed. Steam_SetMinidumpSteamID: Caching Steam ID: Wine: RLIMIT_NICE is <= 20, unable to use setpriority safelyĮventually though, a few minutes later this will appear: GameAction : LaunchApp changed task to Completed with "" Pid 82714 != 82711, skipping destruction (fork without exec?) GameAction : LaunchApp changed task to WaitingGameWindow with "" Pressure-vessel-wrap: W: Binding directories that are located under "/usr/" is not supported! Proton 6.3-8: Loads, nothing happens though. Proton Experimental: Loads, nothing happens though. Proton 5.x : Instant crash, no segfault or other errors though I'm not sure how to generate a proton log but here's my findings: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |