Consuming input_trigger_device can trigger a locked Held state internally

Summary

Can’t be sure of how to repro but it seems like registering a player into a consuming input device while the player is holding the said input will keep that input held untill the player is unregistered again and releasing that input again, see video for more details

In the video I’m registering the player once they equip the weapon and unregister when they unequip it

See how I struggle with finding a repro, the issue starts at 0:20 (my mouse is not pressed but the gun keeps on firing and I can’t cancel it)

We don’t have any power over that since it’s keeping the input Held on the Epic’s end, the input_trigger_device.IsHeld method fails properly as it should while Fortnite thinks I’m still holding it

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Devices

Steps to Reproduce

Add a standard input consuming input device
Register the player while the input is being held
Release the input and notice that the game still thinks the input is being held

Expected Result

Input should stop being held

Observed Result

Input keeps being held

Platform(s)

PC

Re: gun keeps on firing and I can’t cancel it

I experience it very often recently in public matches. Not sure how, I did not even intend to fire. I think I was building and might have switched from building. If I switch to :pick: my character starts pickaxing nonstop. I think it can stop if you enter building mode again.

1 Like

Be sure to leave a vote so that Epic can see

As someone told me, it might not be seen as a bug to everyone since the input being released is not captured anymore after registering the player which could make sense (if the said bug was consistent)

That being said, there should be an option to cancel the currently held input upon registering

Also, the bug is not consistent

FORT-795174 incident has been created. Status is ‘Unconfirmed’.

1 Like