Skip to content
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

Open
2 tasks done
domve opened this issue Jul 12, 2022 · 9 comments
Open
2 tasks done

Ready or Not (1144200) #5985

domve opened this issue Jul 12, 2022 · 9 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem

Comments

@domve
Copy link

domve commented Jul 12, 2022

Compatibility Report

  • Name of the game with compatibility issues: Ready or Not
  • Steam AppID of the game: 1144200

System Information

I confirm:

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

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

@kisak-valve kisak-valve added Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem labels Jul 12, 2022
@DomiStyle
Copy link

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.

@rKsanu2MMYvypWePtQWM
Copy link

I too get the same message when playing this game.

@PoorPocketsMcNewHold
Copy link

Can confirm. Had it happen around the Adam update. The strange thing, was that it had worked for a while in the supporter branch.
From the mod.io integration log, and as reported too by I Love China#6722 on Discord :

[TIMESTAMP][Info][File] Overriding RootLocalStoragePath to Z:\mnt\sda1\SteamLibrary\steamapps\common\Ready Or Not\ReadyOrNot\Content\Paks\mod.io\
[TIMESTAMP][Warning][File] Failed to create directory: Z:\mnt\sda1\SteamLibrary\steamapps\common\Ready Or Not\ReadyOrNot\Content\Paks\mod.io\, with code: 50 and message Request not supported.
[TIMESTAMP][Warning][Core] SDK is not initialized. Cannot Enable Mod Management.

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 ?

@kisak-valve
Copy link
Member

Ready or Not Vram Leak

Issue transferred from #6639.
@Agreeable-f posted on 2023-03-23T15:09:25:

Compatibility Report

  • Name of the game with compatibility issues: Ready or Not
  • Steam AppID of the game: 1144200

System Information

  • GPU: RTX 3060ti OC 8GB
  • Driver/LLVM version: nvidia 535.89.02
  • Kernel version: 6.2.7-zen1-1-zen
  • DE: KDE Plasma 5.27.3
  • WM: KWin (X11)
  • Link to full system information report as Gist: System Info Report
  • Proton version: 7.0-6, Proton Experimental, GE-Proton7-51

I confirm:

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

Symptoms

when 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

  1. Start the game in either DX12 or DX11.
  2. observe vram usage (i'm using KDE's plasma system monitor with vram usage shown on the gpu's history)
  3. load into a pre-game lobby. (i joined a friend's private pre-game lobby as we were playing the game. not sure it matters but noting it for consistency)
  4. observe Vram usage
  5. load into a map. (the maps that crashed for me that were tested so far were neon clubhouse and valley of the dolls. 4u gas station was a case that used 7.8GiB of ram without crashing)
  6. Observe Vram usage
  7. if loaded into a map that crashes, observe the error message.

Final notes

This 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

@Sora012
Copy link

Sora012 commented May 5, 2023

This method I posted for Garry's Mod, also works for mods in Ready or Not (Will fix the Mod IO SDK initialization issue)

#2848 (comment)

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.

@pspirichev
Copy link

This method I posted for Garry's Mod, also works for mods in Ready or Not (Will fix the Mod IO SDK initialization issue)

#2848 (comment)

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.

@Sora012
Copy link

Sora012 commented Oct 4, 2023

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.

@kisak-valve
Copy link
Member

Ready or Not (1144200)

Issue transferred from #7345.
@Doomguy1364 posted on 2023-12-14T04:54:59:

Compatibility Report

  • Name of the game with compatibility issues: Ready or Not
  • Steam AppID of the game: 1144200

System Information

I confirm:

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

steam-1144200.log

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.
As of the 1.0 update for this game DX12 runs at roughly 60% higher FPS over DX11, however it is far from smooth at time of testing!

Reproduction: Always

Play the game for a few minutes on DX12, Extreme stutter and freezing.

@kisak-valve
Copy link
Member

Ready or Not 1144200

Issue transferred from #7347.
@fortunef posted on 2023-12-14T09:42:14:

Compatibility Report

  • Name of the game with compatibility issues: Ready or Not
  • Steam AppID of the game: 1144200

System Information

  • GPU: NVIDIA GTX 1650 Mobile
  • Video driver version: NVIDIA 545.29.06
  • Kernel version: 6.6.6-zen1-1-zen
  • Link to full system information report as Gist:
  • Proton version: Proton Experimental

I confirm:

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

Symptoms

The game is incredibly slow. And for some reason, Steam didn't pre-process the shaders

Reproduction

Launch the game in commander mode. Low and unstable framerate
steam-1144200.log

@kisak-valve kisak-valve mentioned this issue Dec 14, 2023
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem
Projects
None yet
Development

No branches or pull requests

7 participants