New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ready or Not (1144200) #5985
Comments
Is there a way to get the mod.io integration for this game working via Proton? I just get a "mod.io SDK was not initialized" message. |
I too get the same message when playing this game. |
Can confirm. Had it happen around the Adam update. The strange thing, was that it had worked for a while in the supporter branch.
And such, even if we manually change the RootLocalStoragePath for that folder manually, nor create the mod.io folder ourselves. Could it be just an issue with the path ? |
Ready or Not Vram Leak Issue transferred from #6639. Compatibility Report
System Information
I confirm:
Symptomswhen loading into the main menu from startup the game takes up about 4.1GiB of vram. then when loading into the pre-game lobby it goes up to about 6.1GiB. then when loading into a game it will take up 7.8/8 GiB or for larger maps it will outright crash saying it ram out of video memory. the way it fills the Vram is similar to a ram leak however occuring on the video memory. this issue/behaviour does not happen on windows Reproduction
Final notesThis was also tested in the ProtonGE discord on an amd card. same behaviour occurs where their Vram gets filled, however they had more Vram and did not crash. The game's minimum spec requirements denote a gpu with 2GB of Vram. 8GiB should be more than enough on a 3060ti however it is still filled. The recommenced spec state 6GB Vram which is still below the 8GiB of my card |
This method I posted for Garry's Mod, also works for mods in Ready or Not (Will fix the Mod IO SDK initialization issue) You can use any recent version of Proton (I'm on Experimental) and you do not need to opt into a Beta for this game. Simply follow the "outside of steam" symlink instructions and apply it to this game, and its compatdata prefix instead. |
You're living legend, works perfectly for me. Also, Lutris always install games on wine's drive c, it's strange that Valve's proton install games outside of wine directory. |
As someone else pointed out below my original fix, it can be made even easier with "PROTON_SET_GAME_DRIVE=1 %command%" in the launch parameters, and Valve can easily fix it by applying to the fixes they run per game. When I originally found that fix I was not aware of the "PROTON_SET_GAME_DRIVE" usefulness or a valid reason to even use it because a lack of documentation. |
Ready or Not (1144200) Issue transferred from #7345. Compatibility Report
System Information
I confirm:
Symptoms: Under DX12 the game will experience EXTREME freezing and stuttering with-in a few minutes of playing; I do use shader pre-caching, unfortunately it does not seem to help. Reproduction: Always Play the game for a few minutes on DX12, Extreme stutter and freezing. |
Ready or Not 1144200 Issue transferred from #7347. Compatibility Report
System Information
I confirm:
SymptomsThe game is incredibly slow. And for some reason, Steam didn't pre-process the shaders ReproductionLaunch the game in commander mode. Low and unstable framerate |
Compatibility Report
System Information
I confirm:
Symptoms
Random long stutters on GNOME 42.3 using Xorg, making the game very choppy and nearly unplayable. They seem to happen much more frequently when focused directly on the game window, so I imagine this is likely something related to X or GNOME.
This issue is completely absent on Wayland.
Reproduction
Launch the game using either DX11 or DX12 on Xorg, enter a single player session, observe a lot of choppiness and stutters.
steam-1144200.log
The text was updated successfully, but these errors were encountered: