DS5 (and Keyboard?) Werehog Constantly Active Run Button Issue

[LuigiSpeed7]

Validation

• [x] I have checked the Issues page to see if my problem has already been reported
• [x] I have confirmed that this bug does not occur in the original game running on original Xbox 360 hardware

Describe the Bug

The run button is acting like its being constantly held down for my PS5 controller specifically. My Xbox Series Controller is perfectly fine under all circumstances. On occasion, the PS5 controller won't undergo this issue at certain points of stages like the 2D Pole Section at the end of Apotos and throughout most of Mazuri (still playing through the game on a fresh file, so more situations have yet to be encountered)

The Keyboard also inhibits these issues, but they fix themselves once I connect my Xbox Controller. The PS5 controller doesn't fix itself after though.

Steps to Reproduce

Reproducing has been inconsistent, currently this is happening every single time I load into a Hub World as the Werehog. The point in the story I'm at is where you unlock Holoska, aka after the first temple of gaia.

Expected Behavior

The PS5 controller would function like console and not at specific moments act as if I'm holding R2.

Footage

Heres footage I recorded on my phone of the bug: https://youtu.be/tder6Vc86Zc

Specifications

Fill out the following details:

• CPU: (Intel(R) Core(TM) i9-14900K
• GPU: (NVIDIA GeForce 4080 SUPER)
• GPU Driver: (I forgot how to check)
• OS: (Windows 11)
• Version: (1.0.0)

Additional Context

This issue showed up immediately when I gained control over the Werehog for the first time in Apotos, and only fixed itself for the first time near the end of the First Night Stage.

After the bug fixed itself at the end of Apotos Night, I played through all of the next part in the game leading up to the end of Mazuri Night where it triggered itself again. Switching to my XBOX Controller actually fixed the PS5 controller somehow, and control functioned normally again until Holoska. This was the only time switching to my XBOX controller fixed my PS5 controller outright for a bit.

[hyperbx]

Does this occur with just the DualSense connected and no other input device?

[LuigiSpeed7]

Yes, this occurs with just DualSense connected. I just started playing the game again this morning with only it plugged in, no issues whatsoever (even went into holoska night like my last video, worked perfectly)

That is until I beat Dragon Road Night and went back to Chun-Nan at night, the issue came back but in the form of seemingly randomly enabling running on and off.

Heres another video documenting this occurence: https://youtu.be/1YleMWVmkow?si=ab1wg8MduFOtKZBP

Last night after I made this whole post I figured out that lowing FPS back to 60 causes the issue to fix itself, was waiting this morning the whole time for it to happen again just so I could test that again and sure enough it fixed once again on the video too.

[LuigiSpeed7]

Actually, in news I just discovered right this second the Xbox Controller is inhibiting the issue above on uncapped FPS as well in Holoska Night. Keyboard too. I even tried changing my FPS back down to 60 just now and the issue is prevelant across all control types.

Edit: and after writing this comment, it's fixed across all pad types again... this is so weird

Edit 2: Completely unfixable now, under any scene with the werehog and no matter what controller or FPS i set it too I am constantly getting this state where the werehog randomly starts running every few seconds

[Ricktcher]

I have been also encountering this problem since I started playing as the Werehog. I'm using a bootleg controller based on the 360 one, and I haven't seen any changes by changing the FPS. I have a vague feeling it starts after using the Run at least once, but I honestly can't be sure.

[possqueen]

I've encountered this issue as well, using a wired xbox one controller. Didn't happen at all in early game that I recall but seemed to happen fairly consistently once I hit Empire City.

[PTKay]

Let's try debugging the controller first, as at first sight this sounds like a controller issue. It's possible that the trigger is getting registered when it shouldn't be, due to either being overly sensitive or getting stuck in an active position.

Here's how you can do this:

1. Open the game with the controller connected.
2. Open a controller tester (I recommend this webpage) on the side, and leave it open in a way you can see both the tester app and the game.
   • TIP: Open the game in windowed mode and have both windows side by side if you don't have a second monitor.
3. When the Werehog starts running when it shouldn't, check if the controller trigger is marked as active in the tester app.

If you follow the above steps and you're able to see the trigger getting pressed even when you're not pressing it, then it's an issue with your controller, not the game.

Please update us when you have more information, thanks!

[Ricktcher]

I had tried to do this using a windows Controller Tester, and it seemed to be a problem of the game, but using now the webpage you provided it seems it is my controller. My right trigger usually flutters between 0.01 and 0.07, but after being touched at all it goes to the 0.30s, and the game recognizes that as input

Sorry for the misinformed ask, I'll go fix my controller

[possqueen]

I'm positive it isn't my controller since this is the only game that has this issue.

EDIT: used the controller tester and i can confirm it's not my controller. closest result i got was the left trigger registering 0.01 for an extremely split second when pressing one of my grip buttons that's mapped to LB, but nothing that would be registered as holding it down.

[LuigiSpeed7]

I too have tested the Controller Tester and confirmed it is not my controller. I will mention however that I have since beaten the whole game and played a lot more Werehog and this issue occured only 3 other times since my last post I put up on this issue. This being the 3rd time.

Video showing my testing: https://www.youtube.com/watch?v=8kOp2pRdtpY

[DeaTh-G]

@LuigiSpeed7 the linked video is set to private and as such is inaccessible.

[LuigiSpeed7]

@DeaTh-G oops, my mistake. fixed now.

[DeaTh-G]

The video is still very much so private.

[LuigiSpeed7]

Youtube sucks or something cause it is stated as unlisted for me, I even gave the video to my friend who says he can watch it just fine. It's ok though, heres a direct download to the video I put on MEGA: https://mega.nz/file/QtNGiKSL#FChzt1noJ26Q_KEN3TxIRn93HRxOD0OxAgzd6kwKfTY

Should be no issue seeing the video now.