Call of Juarez: Bound in Blood (21980)

[matou68]

Compatibility Report

call of juarez bound in blood

System Information

• GPU: RX480
• Driver/LLVM version: Mesa 18.2.2/7.0.0
• Kernel version: 4.18 (Ubuntu 18.10)
• Link to full system information report as Gist:
• Proton version: 3.16-3

I confirm:

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

steam-21980.log

Symptoms

start the game , you see black screen, press space, press space again, sound is playing, press windows key so you see the game in the window where the game is running.

on first chapter :
this is what i see on Nvidia GTX 750 Ti (396.54.09)

this ist what i see on AMD RX480 LLVM 7/Mesa 18.2.2

Reproduction

[AwesamLinux]

Distro: Linux Mint 19.1 Tessa (64 bit)
GPU: Vega 56
Driver/LLVM version: Mesa 19.1.0-devel/9.0.0
Kernel version: 5.1.0-050100-lowlatency
Proton version: 4.2-3

I'm seeing the same graphical issue, and also cut-scene videos are not played.

media_info.txt
steam-21980.log
system_info.txt

In the log I see:
227528.026:0027:0028:fixme:wmvcore:WMReader_Open (0x35ef1d0)

#1464 Another game using wmvcore and the codecs are: WMV, VC-1 + WMA

[VoodaGod]

installing WMP9 to add wmv playback support fixes missing cutscenes. instructions: #366 (comment)

[kisak-valve]

Call of Juarez: Bound in Blood (21980)

Issue transferred from #3751.
@FanderWasTaken posted on 2020-04-10T05:39:24:

Compatibility Report

• Name of the game with compatibility issues: Call of Juarez: Bound in Blood
• Steam AppID of the game: 21980

System Information

• GPU: Radeon RX 570
• Driver/LLVM version: 4.5 Mesa 19.2.8
• Kernel version: 5.5.15-200.fc31.x86_64
• Link to full system information report as Gist: https://gist.github.com/FanderWasTaken/d67c65b9a0ce2ed507bdb31c91d9c9eb
• Proton version: 5.0-5

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-21980.log

Symptoms

• All of the audio is fine except for the voices - they are all very low quality.
• There is no intro video and no background videos in main menu.

Reproduction

Just boot up the game, load into singleplayer.

Notes

This issue with audio is also present on Windows. I know this game is from 2009, but I don't think that such low res voice lines were intentional. This issue on linux can be fixed by running this version of proton.

---

@FanderWasTaken commented on 2020-04-10T05:46:06:

Btw, there's also this issue #1831 but I didn't come across that.

[ranplayer]

Games runs fine on my end with Proton 8.0-2 and Experimental (2023/05/31). The only issue I come across is that if you enable vsync externally (through DXVK or another layer) or limit its frame rate, the intro video audio stutters (in game there is no vsync or frame limit option). I'm attaching the log file:
steam-21980.tar.gz

Specs:

• O.S: Arch
• Kernel: 6.1.30
• GPU: RX 6700 XT (Mesa 23.1.1)

[ranplayer]

I've found out a regression with Proton 9.0 (Beta-11). The game crashes on launch. The funny fact is that if you enable the logs with PROTON_LOG=1 it doesn't. Perhaps a race condition ?

Logs (no crash):
steam-21980.tar.gz

Specs:

• OS: Arch
• Kernel: 6.6.18
• GPU: RX 6700 XT (Mesa 24.0.1)
• CPU: Ryzen 7 5700G

[kisak-valve]

Hello @ranplayer, 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.

[ranplayer]

Hi @kisak-valve I'm attaching both here as a tar file. Thank you for the quick response.

[simifor]

@ranplayer the game should now work in proton experimental bleeding edge

[btd1337]

Black screen in game startup: The game doesn't launch properly on any Proton version (even the Proton GE)

PS: CoJ 1 and 3 works fine...

OS: Garuda Linux
GPU: NVIDIA GeForce MX350

[simifor]

@btd1337 I haven't been able to reproduce the issue. Proton stable and proton experimental bleeding-edge were both tested and they started fine. I'd recommend verifying game files, and deleting the game's prefix if that doesn't work. If the problem persists then attach the log generated by adding PROTON_LOG=1 %command% to launch parameters, it'll be in your home folder as steam-21980.log

[btd1337]

@simifor the error persists

I attached the log in steam-21980.log