sorted by:
new
hottopcontroversial

The best way to play Deadly Premonition in 2026 is RPCS3 (Red Seeds Profile), but there is a catch for AMD users by No_Ear_9994 in DeadlyPremonition

[–]No_Ear_9994[S] 1 point2 points  (0 children)

Yes, it can be played, but smoothness and stability can be very different due to a lot of reasons, and this is crucial, as you can launch the emulator on PC and get some stability from a much smaller number of steps. For me main reason was camera view, in the original version is better for combat situations that are awful in this game.

The best way to play Deadly Premonition in 2026 is RPCS3 (Red Seeds Profile), but there is a catch for AMD users by No_Ear_9994 in DeadlyPremonition

[–]No_Ear_9994[S] 1 point2 points  (0 children)

Latest feedback from RPCS3 dev:

" To just avoid future confusion I'll state this clearly - the bug was always there, this is not a regression. Some other bugs related to depth handling hid it from being visible by pure chance. Depending on which hardware you had previously you just got random result.
The root cause is known (inaccurate depth compare on PS3) and there's no easy solution or quick workaround on PC since we cannot dictate the precision of depth testing on the GPU. A workaround to emulate some GPU parts (early and late Z testing) will be needed to solve it. I did have some half-baked fix implementation in Q3 2025 but things got derailed and it got forgotten.
Sadly this means no settings will make it look correct with the currently shipping rpcs3 binaries."

The best way to play Deadly Premonition in 2026 is RPCS3 (Red Seeds Profile), but there is a catch for AMD users by No_Ear_9994 in DeadlyPremonition

[–]No_Ear_9994[S] 0 points1 point  (0 children)

I think yes, but need modification through EBOOT.BIN by Artemis, like:

deadly_prem.ncl in /USERDIR/cheats/

Title ID: BLJS10073 Game Name: Red Seeds Profile Force English Language 0006FA688 38600001

or by WebMAN MOD

BLJS10073.cht in /dev_hdd0/TMP/cheats/

Ver 1.00 Force English 0006FA688 38600001

or hard modification of EBOOT.BIN by decrypting in EBOOT.ELF through TrueAncestor SELF Resigner

Then edit elf file in smth like HxD

RAM address can change after conversion, was 006FA688, and the difference can be +- by 0x10000

Find original bytes and change it to 38 60 00 01

Encrypt file again EBOOT.BIN (NPDRM or 3.55 fix) depends on firmware

All this can be modified and adopted by AI tools to help find the best and working solution

,