Forum Discussion
@dkwebb13 Yeah, this is the issue being described here. (That's how mine started, too.) Two things you can try
- Press F and whatever your current custom keybind is. If it works the first time, you should be able to continue using just your current keybind for the rest of the tutorial. (If it works for a while but then stops working, press F with your key again.)
- If that doesn't work at all, map the special attack back to F, complete the tutorial, and then change it back to whatever you're using.
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.
- ShotFromGuns2 years agoRising Vanguard@dkwebb13 Yeah, I'm not even trying to use it as an official stance until this hideous bug is fixed. But it also becomes your default stance when you're mounted, so it's impossible to completely avoid.
It's a real shame it's so utterly busted--and in a way there's no excuse for not catching during beta. I'd love to experiment with it, but there's no way I can as it stands now.
About STAR WARS Jedi: Survivor™
Recent Discussions
- 15 hours ago
- 2 days ago