Valkirie
Unresponsive controllers on Fortnite
Device manufacturer
- [X] VALVE
Device model Steam Deck LCD
Handheld Companion Version 0.21.5.4
Describe the bug Button inputs are either laggy or unresponsive when playing Fortnite. The joysticks and triggers feel like they get "stuck" and keep shooting, and moving the character or camera for 1sec after release. Other buttons sometimes do not count as pressed. It feels like if you're playing on cloud with bad internet. Swapping to desktop mode with Fortnite on background will also cause the mouse emulation to be laggy. Note that this only happens with Fortnite on latest HC version. I tried with both Persona 3 Reload (GP Version) and Minecraft for Windows and it worked fine on both of those games, no issues even after long session times. Rolling back to previous release (0.21.4.1) fixes all the issues.
To Reproduce Steps to reproduce the behavior:
- Use latest version of HC (0.21.5.4)
- Open Fortnite
- Nothing else. Even on the lobby the buttons are unresponsive and laggy.
Expected behavior Responsive button inputs like on the previous versions.
I'm using the steam deck and im emulating an Xbox controller
On Sat, Oct 26, 2024, 10:38 PM Lesueur Benjamin @.***> wrote:
Which type of controller are you emulating?
— Reply to this email directly, view it on GitHub https://github.com/Valkirie/HandheldCompanion/issues/1143#issuecomment-2439862787, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMOPUILGXR2LKCFNLB4FEZ3Z5RU2RAVCNFSM6AAAAABN5Y544GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZHA3DENZYG4 . You are receiving this because you commented.Message ID: @.***>
Xbox controller too, tho i think it was also kinda buggy on a playstation controller
I can confirm this issue still happens on latest release (0.21.7.0) while emulating a PS4 controller. I guess it also happens with Xbox emulation but I didn't tested. HC hotkeys also broke on latest release but that's a whole different issue.
EDIT: Ok the HC hotkeys was because it reimported all of my hotkeys for all the previous reinstalls, so it ran 5 times the same hotkey, that should also be looked at.
Other games are working fine? I'll have to download fornite to try and reproduce this.
Can you guys check CPU usage when the issue arise ? I'm starting to wonder if it's a bottleneck issue where CPU is so busy with the game there is not enough resources left for HC to compute controller inputs. I've been playing solo sessions and LEGO Fortnite with no issue on my 8840U.
I don't think it's that because it happens in the lobby for me aswell
On Thu, Dec 5, 2024, 12:28 AM Lesueur Benjamin @.***> wrote:
Can you guys check CPU usage when the issue arise ? I'm starting to wonder if it's a bottleneck issue where CPU is so busy with the game there is not enough resources left for HC to compute controller inputs. I've been playing solo sessions and LEGO Fortnite with no issue on my 8840U.
— Reply to this email directly, view it on GitHub https://github.com/Valkirie/HandheldCompanion/issues/1143#issuecomment-2519604833, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMOPUIMTLXDMUZ2DRPZHSXD2EAFBZAVCNFSM6AAAAABN5Y544GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJZGYYDIOBTGM . You are receiving this because you commented.Message ID: @.***>
I have the same issue as well in Halo Infinite on a Steam Deck LCD. Happens for me in the lobby too where CPU usage isn't heavy.
Got it. Seams to be Steam Deck specific. I'll try to replicate on my device.
Please give the following build a try: https://1drv.ms/u/s!AleMgLLgxwGJiJpXUw0xLlSC0hZ1bg?e=VdzRot. Please note you'll need NET9.
Please give the following build a try: https://1drv.ms/u/s!AleMgLLgxwGJiJpXUw0xLlSC0hZ1bg?e=VdzRot. Please note you'll need NET9.
I can confirm this build fixed the issue, works flawlessly on a BR match. It even fixed the gyro drift! I'll test it further tomorrow but so far seems the issue is gone for good. Tysm!
To be fair this should be positively impact the gaming experience across all games. Long story short, we've made the task responsible for reading inputs from the device a high priority. So when the device has to allocate ressources to a process and its tasks, this one will always come first.
Fixed with forthcoming release. A beta build is available higher in the comments.