Forum Discussion

shoxspidey95's avatar
3 years ago

Control scheme editing leaves shared inputs unbound

Product: STAR WARS Jedi: Survivor
Platform:PlayStation 5
Summarize your bug Remapping Force Pull (L2) will remove the Ascension Cable (L2) button as they share an input. Remapping Force Focus (R1) doesn't change the HUD indicator
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Change the button map for Force Pull (L2). I chose R2.
What happens when the bug occurs? Ascension Cable becomes unbound, attempting to re-bind it to the same button chosen for the force pull re-bind will switch the mapped button to Ascension cable leaving force pull unbound.
What do you expect to see? Ascension Cable and Force Pull able to share the same button if remapped.

I tried remapping my control scheme to the following:

Force Pull (L2) -> (R2)

Force Push (R2) -> (R1)

Force Focus (R1) -> (L2)

Force Pull (L2) shares an input with Ascension Cable (L2). When I changed Force Pull to R2, Ascension Cable became unbound. When I try to re-map Ascension Cable to R2, it unbinds the input for Force Pull. While they both share an input by default, you can't re-map them both to the same input after changing them.

Force Focus (R1) shows the R1 input on the HUD. When I re-mapped Force Focus to L2, the HUD indicator still says R1. 

1 Reply

  • @shoxspidey95 I'm having the exact same issue. I want to remap my Pull/Push to LB & RB instead, and my Block/Focus to LT & RT. But when I do that, it unbinds the Ascension Cable. Attempting to remap the Ascension Cable to LB, to realign it with Pull, unbinds the Pull input again. Super frustrating.

About STAR WARS Jedi: Survivor™

Join the community forums and talk with us about your experiences in STAR WARS Jedi: Survivor™.2,522 PostsLatest Activity: 6 hours ago