Product: STAR WARS Jedi: Survivor
Platform:Xbox Series X
Summarize your bug The blaster is only usable if you have the base key bind on 👍 but if you use any other like (LT) it doesn’t shoot
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Switch the key bind in settings to anything other then 👍 it uses the special attack button
What happens when the bug occurs? Cant shoot or use the blaster
What do you expect to see? Being able to use the blaster with whatever button is set in settings
I use the Left trigger for my special attack and it won’t for everything So far but if I use the blaster stance I can only use the lightsaber no matter how I try pressing the button holding it or whatever it does NOT shoot which makes it impossible to use one of the key game features. And if I have it set to Y the default it works fine so it just means the blaster ignores the settings and just gone with its default unless in settings you have the special attack set to something other then default it just won’t shoot at all because Y is used for something else so you are unable to use the blaster.
The game seems to have problems with rebinding controls in general. The same sort of thing happens on PC with mouse and keyboard.
In addition to the blaster not working; if you rebind the relevant control you also can't jump while wall running/ wall jumping which makes lot's of terrain traversal sections impassible.
Some controls can't be rebound, and if you want to bind something to a mouse button, the game only detects them being pressed in the keybindings if you double click the button you want to bind before pressing and holding it.
The UI is also full of inconsistencies. Most screens only work with keyboard commands, clicking on buttons with the Mouse doesn't do anything, but then you get a couple of screens like the Customize Cal screen which is only accessible if you lick the button with the mouse. Using the usual keyboard commands do nothing.
It is a bit of a mess at the moment. But it's also very consistent and reproducible across all platforms so hopefully it'll be fixed fairly quickly.
