Blood: Fresh Supply (1010750)

[FurtadoPires]

Whitelist Request

• Blood: Fresh Supply
• Steam AppID: 1010750

I confirm:

• [x] that pressing the Play button in the Steam client is sufficient.

Issues

• [x] I haven't experienced any issues.
• [x] There are no issues left open for this game.

It just works, with multiplayer too.

[kisak-valve]

Hello @FurtadoPires, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[FurtadoPires]

@kisak-valve Sorry I've forgot to put.

https://gist.github.com/FurtadoPires/9e213b3ff12b9afbdbb2772732c65b33

Note: It also work with DRI_PRIME=1 %command% parameter, which activates my Rx 540 when I launch the game (that won't appear in the log)

[shoober420]

Compatibility Report

• Name of the game with compatibility issues: Blood: Fresh Supply
• Steam AppID of the game: https://steamdb.info/app/1010750/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.44
• Kernel version: 5.4.3
• https://gist.github.com/shoober420/1215c40214cf70e1fabb760b5bd2a341
• Proton version: 4.11-10

LOG: steam-1010750.zip

Symptoms

Game will freeze when moving the mouse, then jump to where you swiped ingame. Walking around using the keyboard there is no stuttering or freezing. It only happends when you start moving the mouse.

This occurs when both Vulkan or Direct3D renders are used. I tried both "PROTON_NO_FSYNC=1" and "PROTON_NO_ESYNC=1", and both still produce game freezes when mouse is moved.

Reproduction

Mouse the mouse around ingame.

This happens in DOOM 64 as well, since it uses the KEX Engine. https://github.com/ValveSoftware/Proton/issues/3663

[poperigby]

Looks to be a duplicate of #3316

[shoober420]

I must mention that this was happening with Proton 4.11-8 as well, way before the mouse issues with the new 4.11-10 build, although that can't completely rule out a correlation.

[kisak-valve]

Hello @shoober420, for the moment, you should be able to follow https://github.com/ValveSoftware/Proton/issues/3316#issuecomment-565734041 to roll back to Proton 4.11-9 and test without the regression as a potential factor.

[Galcian79]

This is not a mouse issue, it happens even with the Xbox one controller set in native configuration mode. So it is something related to the KEX engine, not a wine bug.

EDIT: yes i think my guess was right. Whenever using a controller set to native mode, the freeze happens both when you move around (left thumb) or look around (right thumb). If I set the controller to emulate the keyboard only (W, S, A, D, LTARRW, RTARRW, PGUP, PGDN) the issue goes away. So it's everything that polls which causes the issue.

[shoober420]

Definitely an input issue in general, yes.

[dandishonored]

I tried both games and to make mouse working, I must be looking around for a while and making big circles on my mouse pad. I'm also changing speed so it catches up here and there. I found this while I was trying to find some working settings in game console and was testing those. It suddenly started working flawlessly. It works for Doom 64 and Blood: Fresh Supply as well. From that point, I can play as long as I wish. Only what differs is that mouse will freeze in center of the screen in menu so I must navigate menu using keyboard.

I can't explain that behavior. I tried both oldest and default Proton on Steam and both worked the same way.

Wine-4.0 I have installed from distro is working out of the box without issue, but I'm not getting Achievements. I will use Proton with a bit of mouse training at start of game session.

[aboutafter]

Using a more modern SDL2.dll fixes the problem. I personally used the one that comes with the Quake remaster.

I saw the workaround on protondb.

[Kartoffelsaft]

For me the game randomly crashes 1-10 minutes in. It reports the following crash log: CRASHLOG.TXT

The ProtonDB seems to have one other person with a similar issue (seeing as they also get a crash log that reports a memory access violation), though they don't seem to have listed a fix. I've also noticed that it is much faster to crash in co-op multiplayer than any other mode.

things I have tried:

• proton 5.0-10 and 3.16-9 -- introduces the mouse issue you guys report
• replacing SDL2.dll (from their github releases, my install of quake doesn't seem to have this dll) -- immediately crashes on old proton versions, no effect on new ones
• switching to X (i3) over Wayland (hyprland) -- this appears to have no effect (occasionally fixes issues if it's an nvidia thing, but not here apparently)
• hosting instead of joining a game -- seemed to take longer to crash but still did. possibly random chance

As of now this game is effectively unplayable for me.

[kisak-valve]

Hello @Kartoffelsaft, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.