protonscr

KINGDOM HEARTS -HD 1.5+2.5 ReMIX

protonopen appid 2552430Game compatibility - Unofficial
ValveSoftware/Proton#7847 · opened 2024-06-20 by DarkenedSoul124 · updated 2025-01-27 · 16 comments · github · game page · search this game
DDarkenedSoul124 2024-06-20 github

Compatibility Report

  • Name of the game with compatibility issues: KINGDOM HEARTS -HD 1.5+2.5 ReMIX-

  • Steam AppID of the game: 2552430

System Information

Device: Steam Deck OLED

  • Proton version: Any

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.

Symptoms

Upon opening this game on a steam deck, It plays a really loud audio crackling noise which cannot be removed regardless of what happens. It is most noticable in the game select screen where the song "Dearly Beloved" plays. It is constantly playing in the background at high volumes and does not happen on a windows pc.

Reproduction

  • Able to reproduce every time the game is opened and it goes to the game selection screen whether after a reboot or shut down
  • Happens with every game in the collection
  • Can be reproduced in the future Kingdom Hearts game, "KINGDOM HEARTS HD 2.8 Final Chapter Prologue" App ID: 2552440
RReonu 2024-06-24 github

This game is crashing randomly for me. It crashes with a DXVK error.

My system is:
RTX 3070
Ryzen 5800X
32 GB RAM
EndeavourOS (up to date)
Nvidia 555 beta driver
Wayland

Also, the cutscenes only work if you launch the game with the SteamDeck=1 env var.

Vvaparetia 2024-06-28 github

This game including all KH's games crash on me. Not able to get a specific error for diag.

Game Title Numbers
2552430
2552440
2552450

OS: Fedora Linux 40
KERNEL: 6.9.5-200.fc40.x86_64
CPU: AMD Ryzen 7 7700X 8-Core
GPU: AMD Radeon RX 7900 XT
DISPLAY: Wayland
RAM: 32 GB

Seems to be a weird AMD RDNA3 issue
https://steamcommunity.com/app/2552430/discussions/0/6364229748851733833/

MMondrethos 2024-07-04 github

Issues with RDNA3 cards confirmed here as well. This is very unfortunate.

BBitwolfies 2024-07-05 github

The newest Bleeding edge Patch fixes FMV playback without the Steamdeck=1 variable.

Aaarron-lee 2024-07-15 github

I'm also seeing crashing on RDNA3. Crashing on both gamescope-session and KDE desktop.

AMD 8840u
OS: Bazzite
kernel: 6.9.8-201.fsync.fc40.x86_64
RAM: 32GB

RReonu 2024-07-15 github

The RDNA3 crashing issue happens on Windows too, it's not a Proton issue. It'll be adressed in a game patch.

MMondrethos 2024-07-15 github

The RDNA3 crashing issue happens on Windows too, it's not a Proton issue. It'll be adressed in a game patch.

It's not out of the realm of possibility that it gets fixed in Proton or Mesa Drivers before the game addresses it themselves.

Rratsock 2024-08-20 github

This was resolved on Windows with the latest AMD GPU drivers. Comments on the Steam forums indicate that the driver did resolve the crashes.

https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-10-37-01.html

SSirius902 2024-11-09 github

Two things I've noticed with KINGDOM HEARTS II FINAL MIX:

  • After an update of Proton Experimental it seems FMV cutscene playback no longer works even with SteamDeck=1, I recall it working on a prior version of Proton Experimental and Proton 9.0 but neither do anymore. Using GE-Proton-9-15 works though. On versions it doesn't work this is displayed instead of the FMV.

brokeded

  • Not sure if this is a Proton, NVIDIA, or Wayland issue or some combination of the three but after playing the game for a while rendering will deadlock causing the entire game to become unresponsive minus game music as it's processed in a separate thread. This does not seem to happen on X11.

Game Title Number
2552430

OS: NixOS Unstable 24.11 (Vicuna)
KERNEL: Linux 6.10.14
CPU: 12th Gen Intel® Core™ i9-12900KS × 24
GPU: NVIDIA GeForce RTX™ 3090 Ti
NVIDIA Driver: 565.57.01
DISPLAY: Wayland
RAM: 32 GB

EDIT: While playing around with the second one I did manage to get an error popup instead of just deadlocking. Looks like this.
image

AAJuujarvi 2024-11-12 github

@Sirius902 Please make sure shader caching is turned on. That is required for videos that have SMPTE bars. It's not a guarantee it will work, but is one of the requirements. For me currently, the videos do work on my test machines with new installs and an old install of the game. This was with an Nvidia setup and a Steam Deck OLED. If you already had shader caching turned on, please let me know.

SSirius902 2024-11-13 github

@Sirius902 Please make sure shader caching is turned on. That is required for videos that have SMPTE bars. It's not a guarantee it will work, but is one of the requirements. For me currently, the videos do work on my test machines with new installs and an old install of the game. This was with an Nvidia setup and a Steam Deck OLED. If you already had shader caching turned on, please let me know.

Is this the setting you're referring to? Looks to be on to me.

image

AAJuujarvi 2024-11-13 github

@Sirius902 It should be yes. Before we go further delving into a potential transcoded video issue, I'd like you to try something for me first. Can you open a terminal and run the command steam steam://unlockh264/ please? I realize now that the game uses h264 for video processing, and that I see SMPTE bars once I disable it locally on my machine. Please let me know if that works.

SSirius902 2024-11-14 github

@Sirius902 It should be yes. Before we go further delving into a potential transcoded video issue, I'd like you to try something for me first. Can you open a terminal and run the command steam steam://unlockh264/ please? I realize now that the game uses h264 for video processing, and that I see SMPTE bars once I disable it locally on my machine. Please let me know if that works.

@AJuujarvi That did actually seem to fix the issue, thanks. For whatever reason this did work in the past without that command so I'm a bit confused as to why I need to do this now. It may be related to a Steam client update or how Steam is packaged on nixpkgs, not sure.

Regardless the only issue I have remaining is the render deadlocking one but as that may be an NVIDIA driver, Wayland, or vkd3d-proton issue I'm not sure if it can be addressed on this end.

FFlax4 2024-12-04 github

Also having issues with the game using either proton (official or 3rd party)

kherror

Operating System: EndeavourOS
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.12.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × Intel® Core™ i9-10900K CPU @ 3.70GHz
Memory: 31.2 Gibyte of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: ASUS

Ssal-dev 2025-01-27 github

Not sure how thoroughly I should be reporting this, since the problem appears to be fixed on Experimental, but I may have encountered a regression for this title on 9.0-4.

On 9.0-4, the game fails to launch. No errors from Steam or the game appear. This did not happen on 9.0-3, and does not happen on Experimental.

Other games launch properly on 9.0-4 so far. Tried verifying the file integrity of both the game and Proton 9, which didn't work. All software is up to date.

Proton log for failed launch:
steam-2552430.log

My system:

  • OS: Fedora 40
  • Desktop: KDE Plasma 6.2.5
  • Kernel: 6.12.10-100.fc40.x86_64
  • CPU: Intel Core i5-8365U
  • GPU: Intel UHD Graphics 620
  • GPU Driver: Mesa 24.1.7
  • RAM: 16 GB
Kkisak-valve maintainer 2025-01-27 github

Hello @sal-dev, https://github.com/HansKristian-Work/vkd3d-proton/pull/2262 is what fixed your regression.

Proton versions

Upstream links