starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 00:05:58 +03:00

[GH-ISSUE #2957] [GAME BUG]: CUSA00462 - Far Cry® 4 BlendOp and BlendFactor issues #937

New issue

Closed

opened 2026-02-27 21:09:00 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 21:09:00 +03:00

Owner

Originally created by @Missake212 on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2957

Checklist (we expect you to perform these steps before opening the issue)

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.
I have re-dumped the game and performed a clean install without mods and the issue is still present.
I have disabled all patches and cheats and the issue is still present.
I have all the required system modules installed.

Describe the Bug

Far Cry 4 has been crashing on the following Unreachable for a while now:

[Debug] liverpool_to_vk.cpp:BlendOp:219: Unreachable code!

I've asked about it in the development channel of the shadPS4 Discord server and it seems to be garbage data that the game sends. Changing the unreachable in liverpool_to_vk.cpp to default to any of the previous BlendOp makes the game crash on:

[Debug] <Critical> liverpool.h:113 SearchBinaryInfo: Unreachable code! Shader binary info not found.

Using a hack made by Kalaposfos to skip this then leads to a BlendFactor unreachable:

[Debug] <Critical> liverpool_to_vk.cpp:213 BlendFactor: Unreachable code!

Again this time returning any of the BlendFactor (yes I've tested them all) finally gets you in game (with what seems to me like the same visual issues for all of them). I did get this error a few times when changing which of them it returns though:

That's about all the information I can give, if I can help debug this in any other way please let me know I'd be glad to help.

Reproduction Steps

Launch the game and wait for the crash to occur.

Specify OS Version

Windows 11

CPU

Intel Core I9-13900K

GPU

Nvidia RTX 4090

Amount of RAM in GB

32 GB

Amount of VRAM in GB

24 GB

Log File

CUSA00462.log

Originally created by @Missake212 on GitHub (May 20, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2957 ### Checklist (we expect you to perform these steps before opening the issue) - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. - [x] I have re-dumped the game and performed a clean install without mods and the issue is still present. - [x] I have disabled all patches and cheats and the issue is still present. - [x] I have all the required [system modules](https://github.com/shadps4-emu/shadps4-game-compatibility?tab=readme-ov-file#informations) installed. ### Describe the Bug Far Cry 4 has been crashing on the following Unreachable for a while now: ``[Debug] liverpool_to_vk.cpp:BlendOp:219: Unreachable code!`` I've asked about it in the development channel of the shadPS4 Discord server and it seems to be garbage data that the game sends. Changing the unreachable in liverpool_to_vk.cpp to default to any of the previous BlendOp makes the game crash on: ``[Debug] <Critical> liverpool.h:113 SearchBinaryInfo: Unreachable code! Shader binary info not found.`` Using a hack made by Kalaposfos to skip this then leads to a BlendFactor unreachable: ``[Debug] <Critical> liverpool_to_vk.cpp:213 BlendFactor: Unreachable code!`` Again this time returning any of the BlendFactor (yes I've tested them all) finally gets you in game (with what seems to me like the same visual issues for all of them). I did get this error a few times when changing which of them it returns though: ![Image](https://github.com/user-attachments/assets/8fee4540-8e1c-432b-b750-53721de1501c) That's about all the information I can give, if I can help debug this in any other way please let me know I'd be glad to help. ### Reproduction Steps Launch the game and wait for the crash to occur. ### Specify OS Version Windows 11 ### CPU Intel Core I9-13900K ### GPU Nvidia RTX 4090 ### Amount of RAM in GB 32 GB ### Amount of VRAM in GB 24 GB ### Log File [CUSA00462.log](https://github.com/user-attachments/files/20319807/CUSA00462.log)

kerem closed this issue

2026-02-27 21:09:00 +03:00

kerem commented

2026-02-27 21:09:01 +03:00

Author

Owner

@Missake212 commented on GitHub (Jul 24, 2025):

Dropping that here in case it's useful (I doubt it).

Far Cry 4 always hits the BlendOp unless I skip the last two fs shaders on this screenshot (the ones at the bottom of it) when skipped I get a "shader binary info not found" I'm not sure if that just means those shaders are too important to be skipped or if they're the one that have the issue with the BlendOp and skipping them allows me to get further into the next issue the game has (all of the other shaders still crash on BlendOp when skipped).

@Missake212 commented on GitHub (Jul 24, 2025): Dropping that here in case it's useful (I doubt it). Far Cry 4 always hits the BlendOp unless I skip the last two fs shaders on this screenshot (the ones at the bottom of it) when skipped I get a "shader binary info not found" I'm not sure if that just means those shaders are too important to be skipped or if they're the one that have the issue with the BlendOp and skipping them allows me to get further into the next issue the game has (all of the other shaders still crash on BlendOp when skipped). <img width="635" height="243" alt="Image" src="https://github.com/user-attachments/assets/9cbd5555-f8ad-4f97-99ec-654eaa1f59e9" />

kerem commented

2026-02-27 21:09:01 +03:00

Author

Owner

@squidbus commented on GitHub (Aug 30, 2025):

Blend op/factor issue should be fixed, shader binary info issue remains.

@squidbus commented on GitHub (Aug 30, 2025): Blend op/factor issue should be fixed, shader binary info issue remains.

kerem commented

2026-02-27 21:09:01 +03:00

Author

Owner

@Missake212 commented on GitHub (Aug 30, 2025):

If you want me to I can reopen this one, I thought I'd close any game related issue the other day to debloat a bit since I've reported them all on the compatibility list already.

@Missake212 commented on GitHub (Aug 30, 2025): If you want me to I can reopen this one, I thought I'd close any game related issue the other day to debloat a bit since I've reported them all on the compatibility list already.

kerem commented

2026-02-27 21:09:01 +03:00

Author

Owner

@squidbus commented on GitHub (Aug 30, 2025):

It’s fine, we can track in compatibility yeah.

@squidbus commented on GitHub (Aug 30, 2025): It’s fine, we can track in compatibility yeah.

kerem referenced this issue

2026-02-27 21:14:10 +03:00

[PR #937] [CLOSED] Typos #1841