[GH-ISSUE #3343] [GAME BUG]: CUSA01113 Gravity rush remastered multiple input bug in menu and comic book cut scenes was fixed in one version but cameback for every other version

kerem commented

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

Owner

Originally created by @Mry3zof on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3343

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

So in the menu is you use like the downward button in your controller the game just respone as you have pressed the button a million times , same thing with the cutscene if you press X button to go next the game just skips half of the cut scene as if you was like pressing the button in an inhumanly speed I use logtic F310 controller (even tho I've seen alot of people with very diffrent controllers have the same issue) this old issue provides some more explantion and vidoes for the problem #1434 , the new thing here is that the only version of shad ps4 I could find to fix this issue was rainmaker's 0.5.0 version of the emu (it should be [kalaposfos13] branch with the remapped input but I got confussed and didn't know where to download that) anyways but this version of the emu has very poor optimization and don't work like the later version of the 0.10 at least on my pc. I always download every single update for the emu hoping to fix this issue but yeah it's still there.

Reproduction Steps

just play the game on any version excpet rainmaker's 0.5.0 with either a controller or a keyboard it doesn't matter.

Specify OS Version

Windows 10 pro

CPU

ryzen 5 3600

GPU

GTX 1650 super

Amount of RAM in GB

16

Amount of VRAM in GB

4

Log File

shad_log.txt

Originally created by @Mry3zof on GitHub (Jul 28, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3343 ### 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/wiki/I.-Quick-start-%5BUsers%5D#4-adding-modules) installed. ### Describe the Bug So in the menu is you use like the downward button in your controller the game just respone as you have pressed the button a million times , same thing with the cutscene if you press X button to go next the game just skips half of the cut scene as if you was like pressing the button in an inhumanly speed I use logtic F310 controller (even tho I've seen alot of people with very diffrent controllers have the same issue) this old issue provides some more explantion and vidoes for the problem #1434 , the new thing here is that the only version of shad ps4 I could find to fix this issue was rainmaker's 0.5.0 version of the emu (it should be [kalaposfos13] branch with the remapped input but I got confussed and didn't know where to download that) anyways but this version of the emu has very poor optimization and don't work like the later version of the 0.10 at least on my pc. I always download every single update for the emu hoping to fix this issue but yeah it's still there. ### Reproduction Steps just play the game on any version excpet rainmaker's 0.5.0 with either a controller or a keyboard it doesn't matter. ### Specify OS Version Windows 10 pro ### CPU ryzen 5 3600 ### GPU GTX 1650 super ### Amount of RAM in GB 16 ### Amount of VRAM in GB 4 ### Log File [shad_log.txt](https://github.com/user-attachments/files/21457997/shad_log.txt)

kerem closed this issue

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

kerem commented

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

Author

Owner

@rainmakerv3 commented on GitHub (Jul 28, 2025):

The version of mine the post is referring to was a build with an older version of @kalaposfos13 's input stuff that fixed this issue on GRR.

I can confirm that the issue is somehow back, but I can't say what regressed it

@rainmakerv3 commented on GitHub (Jul 28, 2025): The version of mine the post is referring to was a build with an older version of @kalaposfos13 's input stuff that fixed this issue on GRR. I can confirm that the issue is somehow back, but I can't say what regressed it

kerem commented

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

Author

Owner

@kaiwolft commented on GitHub (Sep 10, 2025):

i have this problem, and with the more recent version, you found a solution?

@kaiwolft commented on GitHub (Sep 10, 2025): i have this problem, and with the more recent version, you found a solution?

kerem commented

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

Author

Owner

@Korpyz commented on GitHub (Sep 21, 2025):

seems to have had a regression, gravity rush continues to receive multiple inputs and skips all cutscenes.

@Korpyz commented on GitHub (Sep 21, 2025): seems to have had a regression, gravity rush continues to receive multiple inputs and skips all cutscenes.

kerem commented

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

Author

Owner

@notthefoxx commented on GitHub (Sep 21, 2025):

can confirm, it's still the issue on 0.11.0

@notthefoxx commented on GitHub (Sep 21, 2025): can confirm, it's still the issue on 0.11.0

kerem commented

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

Author

Owner

@GHU7924 commented on GitHub (Sep 23, 2025):

If I'm not mistaken, last time this commit fixed this problem.

@kalaposfos13 wrote the following: The touchpad's button state was correctly handled, so games that use that were fine, but the touchDown flag was always set to true, so games that use this flag had problems, like Gravity Rush.
Perhaps this will help you understand what changed and brought back the problem.

@GHU7924 commented on GitHub (Sep 23, 2025): If I'm not mistaken, last time [this commit](https://github.com/shadps4-emu/shadPS4/pull/1356/commits/bc187bfe81165bfb2636f602bb2e78da4d7e72d7) fixed this problem. @kalaposfos13 wrote the following: `The touchpad's button state was correctly handled, so games that use that were fine, but the touchDown flag was always set to true, so games that use this flag had problems, like Gravity Rush`. Perhaps this will help you understand what changed and brought back the problem.

kerem commented

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

Author

Owner

@Kozzlick commented on GitHub (Oct 1, 2025):

"comic dialogues when you press to advance, usually it skip the entire dialogue, like if it presses it many times" - I just tested the game today on shadps4 11.0 and I still have this issue. is there any workaround? I get this behavior with gamepad, keyboard and mouse. Everything works just fine, but comic dialogues advances by several pages all the time. I had a theory that it has to do something with frames and input detection so I tried different presentation methods (v-sync/no v-sync), tried to connect the controller via bluetooth instead of wired, tried to limit fps, and still face this issue. any fix besides using old version?

@Kozzlick commented on GitHub (Oct 1, 2025): "comic dialogues when you press to advance, usually it skip the entire dialogue, like if it presses it many times" - I just tested the game today on shadps4 11.0 and I still have this issue. is there any workaround? I get this behavior with gamepad, keyboard and mouse. Everything works just fine, but comic dialogues advances by several pages all the time. I had a theory that it has to do something with frames and input detection so I tried different presentation methods (v-sync/no v-sync), tried to connect the controller via bluetooth instead of wired, tried to limit fps, and still face this issue. any fix besides using old version?

kerem commented

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

Author

Owner

@RawToast225 commented on GitHub (Oct 21, 2025):

If I'm not mistaken, last time this commit fixed this problem.

@kalaposfos13 wrote the following: The touchpad's button state was correctly handled, so games that use that were fine, but the touchDown flag was always set to true, so games that use this flag had problems, like Gravity Rush. Perhaps this will help you understand what changed and brought back the problem.

i see that that commit has been merged, but has it been released? if it has, then that commit did not, in fact, fix the issue. if it hasn't then it may have fixed it. i can't get the project to build on my system, so i can't confirm

@RawToast225 commented on GitHub (Oct 21, 2025): > If I'm not mistaken, last time [this commit](https://github.com/shadps4-emu/shadPS4/pull/1356/commits/bc187bfe81165bfb2636f602bb2e78da4d7e72d7) fixed this problem. > > [@kalaposfos13](https://github.com/kalaposfos13) wrote the following: `The touchpad's button state was correctly handled, so games that use that were fine, but the touchDown flag was always set to true, so games that use this flag had problems, like Gravity Rush`. Perhaps this will help you understand what changed and brought back the problem. i see that that commit has been merged, but has it been released? if it has, then that commit did not, in fact, fix the issue. if it hasn't then it may have fixed it. i can't get the project to build on my system, so i can't confirm

kerem commented

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

Author

Owner

@Emogop commented on GitHub (Oct 31, 2025):

0.12.0
Still an issue.

@Emogop commented on GitHub (Oct 31, 2025): 0.12.0 Still an issue.

kerem commented

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

Author

Owner

@gigablackpilled commented on GitHub (Nov 17, 2025):

The issue is caused by having motion controls disabled.
I tested with and without motion controls enabled in the game-specific settings multiple times and can say with fair certainty that's what causes it.

@gigablackpilled commented on GitHub (Nov 17, 2025): The issue is caused by having motion controls disabled. I tested with and without motion controls enabled in the game-specific settings multiple times and can say with fair certainty that's what causes it.

kerem commented

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

Author

Owner

@Mry3zof commented on GitHub (Nov 17, 2025):

Can you tell us the exact settings because I had that I enabled the motion controls in the game-specific settings and still the same issue. Also what version did test this on ? @gigablackpilled

@Mry3zof commented on GitHub (Nov 17, 2025): Can you tell us the exact settings because I had that I enabled the motion controls in the game-specific settings and still the same issue. Also what version did test this on ? @gigablackpilled

kerem commented

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

Author

Owner

@gigablackpilled commented on GitHub (Nov 18, 2025):

Latest main 0.12.6 WIP 5b69909. I have a friend that didn't experience the problem either upon starting a new game with motion controls enabled.
If it has something to do with our rigs, we both have AMD CPUs ( 5600 and 9800X3D) and Nvidia GPUs (4070 and 4080).

@gigablackpilled commented on GitHub (Nov 18, 2025): Latest main 0.12.6 WIP 5b69909. I have a friend that didn't experience the problem either upon starting a new game with motion controls enabled. If it has something to do with our rigs, we both have AMD CPUs ( 5600 and 9800X3D) and Nvidia GPUs (4070 and 4080).

kerem commented

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

Author

Owner

@Mry3zof commented on GitHub (Nov 18, 2025):

Well, yeah I tried enabling motion controls on that version and still the same problem. but what're your controllers like does they support motion control ? mine dosen't (logitic f310) @gigablackpilled

@Mry3zof commented on GitHub (Nov 18, 2025): Well, yeah I tried enabling motion controls on that version and still the same problem. but what're your controllers like does they support motion control ? mine dosen't (logitic f310) @gigablackpilled

kerem commented

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

Author

Owner

@gigablackpilled commented on GitHub (Nov 18, 2025):

Yup, that's what the issue is. My buddy and I have dualsense controllers which have gyro support and when I tried with my Xbox One controller, the issue comes back.

@gigablackpilled commented on GitHub (Nov 18, 2025): Yup, that's what the issue is. My buddy and I have dualsense controllers which have gyro support and when I tried with my Xbox One controller, the issue comes back.

kerem commented

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

Author

Owner

@Mry3zof commented on GitHub (Nov 18, 2025):

this's a very good lead to solve this issue

@Mry3zof commented on GitHub (Nov 18, 2025): this's a very good lead to solve this issue

kerem commented

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

Author

Owner

@UNI3468 commented on GitHub (Dec 24, 2025):

That’s great. Using a Switch Pro Controller fixed the issue, but now the left stick is drifting, so I can’t run.

@UNI3468 commented on GitHub (Dec 24, 2025): That’s great. Using a Switch Pro Controller fixed the issue, but now the left stick is drifting, so I can’t run.

kerem commented

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

Author

Owner

@RawToast225 commented on GitHub (Dec 24, 2025):

and for those that don't have a switch pro controller?

@RawToast225 commented on GitHub (Dec 24, 2025): and for those that don't have a switch pro controller?

kerem commented

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

Author

Owner

@GHU7924 commented on GitHub (Feb 11, 2026):

Please test PR #4022 (https://github.com/shadps4-emu/shadPS4/actions/runs/21904870881)
Does this solve your problem?

@GHU7924 commented on GitHub (Feb 11, 2026): Please test PR #4022 (https://github.com/shadps4-emu/shadPS4/actions/runs/21904870881) Does this solve your problem?

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Feb 12, 2026):

There have been multiple reports saying this is fixed, so I'll close it for now.
If this issue still occurs, send a log here and I can reopen this if the log seems reasonable.

@StevenMiller123 commented on GitHub (Feb 12, 2026): There have been multiple reports saying this is fixed, so I'll close it for now. If this issue still occurs, send a log here and I can reopen this if the log seems reasonable.

kerem commented

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

Author

Owner

@Linear524 commented on GitHub (Feb 13, 2026):

Yup ! PR #4022 fixed this issue !
But caused another issue - it seems that emulated motion controls are always sending tilted input if using XBox Series controllers :P
For example - Journey now has always rotating camera ))

@Linear524 commented on GitHub (Feb 13, 2026): Yup ! PR #4022 fixed this issue ! But caused another issue - it seems that emulated motion controls are always sending tilted input if using XBox Series controllers :P For example - Journey now has always rotating camera ))

kerem commented

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

Author

Owner

@Linear524 commented on GitHub (Feb 14, 2026):

Thanks !!!
Now everything works fine in Journey and Flower :)

@Linear524 commented on GitHub (Feb 14, 2026): Thanks !!! Now everything works fine in Journey and Flower :)

kerem referenced this issue

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

[PR #1028] [MERGED] Add nullptr check in scePthreadSetprio function #1887

Rows
Columns

[GH-ISSUE #3343] [GAME BUG]: CUSA01113 Gravity rush remastered multiple input bug in menu and comic book cut scenes was fixed in one version but cameback for every other version #1028

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

Describe the Bug

Reproduction Steps

Specify OS Version

CPU

GPU

Amount of RAM in GB

Amount of VRAM in GB

Log File