Eternal Force Choke State as Vader
Product: Star Wars Battlefront II
Platform:PC
What is your issue related to? General
Summarize your bug After Force Choking someone, Vader enters in a bad state as if he was still Choking someone, but he isn't, and only a staggering effect releases him from such stance.
What is your gamertag/PSN ID/EA Account name? RogueZeroRendar
How often does the bug occur? Often (50% - 99%)
Can you tell us the date (MM/DD/YYYY) that you saw the bug? It was present in every patch (including 2.01, the latest as of this day)
What time did you see the bug? (HH:MM AM/PM)
In what game mode did the bug occur? Heroes vs. Villains
What is your time zone?
Steps: How can we find the bug ourselves? Now that isn't so easy, but sometimes when you use Force Choke it enters this state.
What happens when the bug occurs? Vader gets stuck in the Force Choking Stance, with a very reduced speed, and becomes unable to attack, to block, to jump, to sprint, to dash or to use his Saber Throw. He can use Focused Rage though, and I didn't test choking while in this state.
What do you expect to see? That it doesn't happen anymore, as this is clearly a BUG
Please select your region South America
AMD or Nvidia Model Number
Here is a compilation of the 5 times I got into this bad state as Vader in the same match:
I have one guess about it: LAG. In the video presented, I was suffering from some LAG which felt very different from normal LAG, as my character seemed to get dragged around while trying to move faster, and yesterday I saw another Vader get stuck in this state, and I had been seeing him lagging around the whole match (when you see characters more clipping then moving). That's the best I can offer for this matter, if other people have any info on this please share it here so DICE can fix this faster.
I know there are other topics here covering this, but I didn't find any that was only specific to this BUG, as Force Choke has several BUGs related to it.
It seems after the changes to Vader's Choke in 2020, this BUG has finally been fixed. I don't experience it since 2018, but I have seen many reports on it throughout the whole year of 2019.
I'll mark this one as solved. It took more then 2 years, but I guess we can finally label this as fixed.
