Few of obi wan bugs I’ve noticed
Product: Star Wars Battlefront II Platform:Sony Playstation 4 What is your issue related to? General Summarize your bug Bug 1. Force push Bug 2. Stops swinging What is your gamertag/PSN ID/EA Ac...
Forum Discussion
EA_Blueberry
Community Manager
Community ManagerWhen you say it charges for a long time. How long would you say it does it?
Well if you hold the L1 it charges the push up if you quickly press its suppose to do a small but quicker push..sometimes it charges for about 3 to 4 seconds even know you only pushed the L1 quickly for a small push in that time you get destroyed by the villains
Have you tried with another controller @claytonEC1V ? People who I know play Obi-Wan frequently never complained about this push issue.
Also, try to focus your report on a single BUG, or else it's common for them to pass unnoticed. I have no idea what you mean by trying to attack and the saber swing not happening, could you be more specific?
- Ok i’ll Keep that in mind for next time, if I press square once it swings once if press square twice it swings twice sometimes when I swing a third and I mean it’s not every single time infact it’s about 20% of the time, there are loads of bugs in starWars battle front 2 so I don’t want to keep posting posts..also my controller is brand new so it’s not the problem
Also, If you can, share a video of the BUG happening, it becomes far easier to understand a BUG. The saber attack on this game can be queued, however this isn't a subject I tested much. If you quickly press twice to attack, it'll queue the second attack to be done after the first one. If you dodge between them, it'll probably make you dodge after the first swing, and then it'll produce a new swing as you had one in queue. For more then 1 attack in queue I don't know what happens.
As this queuing mechanic is strange to me, I usually press the attack button as many times as I wish to attack, so I act accordingly.
There are also many ways to cancel an attack, so maybe that was your issue?
About the controller, a new controller only increases the chances it isn't malfunctioning, but it still can. Try with another controller, and if the same exact thing happens, then you know the issue isn't in your controller.
And well, there are indeed many BUGs with SWBFII2017, but you should keep posting posts IMO 😉
