Product: STAR WARS Jedi: Survivor
Platform:PC
Summarize your bug Blaster won't shot after I reassign special attack to a thumb button
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Reassign special attack to a thumb button on mouse and try blaster stance.
What happens when the bug occurs? Always.
What do you expect to see? The problem solved. Now I don't even play with blaster stance.
Other stances thumb button works fine. On blaster it doesn't do nothing. If I reset buttons the "F" works fine. I managed a workaround if I press F simultaneous with thumb button. From that moment on it works fine and only thumb button is needed, even tho F is replaced by thumb button. Weird.... Game is Origin and mouse is Razer Basilik Essential.
Also had this problem. On PC using an Xbox Series X controller. Blaster attack is bound to right trigger. It works usually right after I die or reload the game, but quickly locks up completely and remains unusable for long periods of time. Very disappointing.
Came here to report exactly this bug. Looks like it's a common one across all platforms. In addition to this thread:
Personally, I have Q bound to special attack and F bound to heal. (You know, like... basically every game does. Stop reinventing the wheel, please.)
This is the problem I'm experiencing too. My bug happens at the same spot every time, 100% of the time.
My problem occurs when I'm in the anchorite sanctuary on Jedha. Bode gives Cal a blaster and that launches a tutorial sequence where Cal is required to shoot a piece of stormtrooper armor with the blaster. No matter what I do, I can't get the blaster to fire. I've tried remapping it to different keys. I've mapped it to insert, I've mapped it to the center mouse button, I've mapped it to number pad 7. None of them make any difference. I've logged out of the game and back in repeatedly. I still can't get past the point where Bode gives Cal that wretched blaster and brings the game to a dead stop.
My system has an AMD Ryzen 7 2700X with 32 gb of RAM. My graphics card is a Radeon RX580 with 8 gb of VRAM.
@dkwebb13 Yeah, this is the issue being described here. (That's how mine started, too.) Two things you can try
If you're not using F for anything else, make that the primary keybind for the special attack, and then add your preferred input as the secondary bind, and that should permanently resolve it. (But I assume you're probably also using F for something else.)
I followed your advice and reassigned it to the F key. Since I have to keep using the F key to do that, it just makes the most sense. Still it's an annoying enough bug that it prevents me from using blaster as one of my stances. I've gone to using the cross-guard stance and the dual stance as my standard ones to use. Hopefully, that — and the other — bugs will be fixed soon.
I will say that all-in-all I think that EA has done themselves proud with this sequel to Fallen Order It's a very enjoyable game to play.
It's been fixed! I just download a gigantic game update — over 100 gigabytes! — and the problem has been fixed. It works perfectly now!
At least it does on my machine. You guys should download the update and see if it fixes the problem for you too!
This is not, in fact, fixed on latest patch. The above workaround still works, pressing the new + original keybind simultaneously will allow the new keybind to work until the next time game state is reloaded, but after a reload your new bind goes dead again until repeating the process.
