Explanation of the Last Epoch Fury Leap on Controller Bug

Version 1.0 of Last Epoch is now out after almost five years in early access. Its rollout hasn't been without problems, however. This article explains the reasons for the improper operation of the Primalist's skill Fury Leap on a gamepad in Last Epoch and looks at potential workarounds.

Explanation of the Last Epoch Fury Leap on Controller Bug

Final Epoch Fury Leap Not Functioning Due to a Controller Error

Complete controller support is one of the numerous enhancements and quality-of-life adjustments included in the Last Epoch 1.0 update by the developers. This indicates the removal of controller targeting for certain skills. Fury Leap, Aerial Assault, and Transplant are examples of this. Additionally, Fury Leap is sadly presently broken with a controller, even though Transplant and Aerial Assault are operating as planned.

Specifically, the ability no longer tracks the adversaries that are highlighted, unlike what it did before to the patch. Rather, it just leaps to the direction your character is now facing from its greatest range. As you want to jump on the enemy nearest to you rather than some random point at the edge of the screen, this naturally renders the talent almost ineffective.

Attacks don't appear to follow adversaries as effectively as they did before the patch, according to a Steam user named OniGrin. "I just started running a new Primalist after the patch," the user stated. "Fury Leap just follows my direction until it reaches its maximum range, at which time it moves toward the nearest target in that direction. Was this intentional, or was there a problem with the controllers' targeting?

Is there a way to resolve this problem then? Regretfully, to the best of our understanding, there doesn't seem to be a workaround for the bug as of now. As a result, using a controller to play the Primalist becomes almost impossible. It is hoped that the developers are aware of the issue and are attempting to resolve it. That's all we have to say about the bug for now. Still, we'll make sure to update the piece as soon as we learn anything new.