While the crashes are resolved in 1.5+2.5, I believe the same cannot be said for Kingdom Hearts HD 2.8 Final Chapter Prologue.
I am running into the similar GPU time out crashes with this title still.
Can we please push for a fix similar to 1.5+2.5 for 2.8?
Solved! Go to Solution.
https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-10-37-01.html
Combined with the new upsate they dropped for the game this morning seems to have resolved this.
Closing for now unless I see a crash.
Is this on 24.7.1 driver?
See here:
There is a mention for a fix for Kingdom Hearts 1.5 + 2.5
No its on the driver that dropped yesterday. The one prior to 24.8.1
Unless 24.8.1 has the fully implemented fix, I do not know because 1.5+2.5 stopped crashing, but 2.8 crashes a lot still.
Can you provide a link for the driver with a fix please?
Thanks!
It seems 2.8 is very finnicky.
Sometimes it doesn't crash, other times its very prone to it.
This will definitely need to be looked at like 1.5+2.5 was.
And now its not crashing, which issssssssss it....... Either work or don't work, its weird!
Sorry to ping you, but can you pass this onto the driver team that KINGDOM HEARTS HD 2.8 FINAL CHAPTER PROLOGUE has the same GPU timeouts KINGDOM HEARTS HD1.5+2.5 Remix has and still requires the same kind of fix rolled out please?
The issues span the XT & XT/XTX 7000 GPUs much like with KH1.5+2.5.
The games that have issues are KINGDOM HEARTS DREAM DROP DISTANCE HD and KINGDOM HEARTS BACK COVER (The movie). They both crash due to the same GPU issues.
Perhaps you can inform them if you can?
Bumping for getting recognition!
And to keep the dream alive.
The home stretch, fix Kingdom Hearts HD 2.8 Final Chapter Prologue and every KH game will be functionable both on desktops and portably!
I will keep bumping this until it gets recognition.
Now I could be wrong, but I think the hotfix they released on the 23rd August just might've fixed the crashing in DDD, but cannot confirm or deny it right now, needs more testing.
Edit: Crashed on Chill Clawbster.
This will need addressing. Please fix like you did with 1.5+2.5.
https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-10-37-01.html
Combined with the new upsate they dropped for the game this morning seems to have resolved this.
Closing for now unless I see a crash.