Platform: PC
Operating System: Windows 10 Home
GPU: MSI RTX 2070 Armor
CPU: Intel i7-9700K
RAM: CORSAIR - Vengeance RGB PR DDR4 64 GB
Motherboard: ASUS Prime Z390-A
Predator - Auto Fire
Predator enters a state that automatically holds ‘Fire’ input when pressing ‘Fire’ + ‘Leap’ by mistake
Solution: Press ‘Fire’ input
Auto Fire [Technical]
‘Leap’ (Down Hold) --> ‘Leap’ (Up) --> ‘Fire’ (Down) --> ‘Fire’ (Up)
Auto Fire [Recreation Friendly]
‘Leap’ --> ‘Fire’
Auto Fire [Practical/Default input] [PC] [Mouse and Keyboard]
Control --> LMB
Auto Fire [Practical/Default input] [PS4/PS5] [Gamepad/Controller]
R2/RT --> R1/RB
Comments
Predator - Auto Fire is distrusting to gameflow and commonly causes Predator to slam infront of Fireteam members or disrupt evasion
Notes
-
Easier to recreate on controller
-
Behaves as if ‘Fire’ is being held down
Additional Information
Can occur as host of Private Game and when connected to public server
Inputs that interact with ‘Fire’
-
‘Jump’, ‘Jump/Interact’, ‘Jump/Leap/Interact’, ‘Jump/Branch Switch’, ‘Stealth Dismount’ (When Predator lands also causes Predator to ‘Fire’ --> ‘Crouch’ (Sit) --> ‘Crouch’ (Stand)
-
‘Leap’, ‘Jump/Leap/Interact’, (Causes Predator to Slam, when energy is depleted, Predator will inherit its interaction with ‘Jump’)
-
‘Sprint’, ‘Sprint/Interact’, ‘Sprint Toggle’, ‘Select Weapon (1-4)’, ‘Weapon Wheel’ (Causes Predator to ‘Fire’, holding these inputs also causes Predator to ‘Fire’ 3 times in a row)
Summery
Seemingly the underlying issue is that holding down ‘Fire’ and having it interact with other inputs is the root source of the problem and is separate from the input chain of ‘Fire’ --> ‘Leap’ causing ‘Fire’ to be stuck
Also did some more testing afterwards that wasn’t included in the video
Estimated Activity
2020-04-25T07:00:00Z (Patch 1.0) - 2022-11-27T08:00:00Z (Patch 2.44)
Discord
Input Dictionary
Community backed bug reports