March 2018 - last edited January
Product: Star Wars Battlefront II
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.
Thank you for your detailed report and the video (I admit, the music made me quite emotional, because I have a soft spot for Beethoven).
I will send it to our specialists now. I'll try to update this thread, once I get any reply from them.
That looks similar to the issue I got with the Heavy Trooper after using the explosive sentry. It felt like my trooper still thought it was firing the explosive sentry but wasn't. The only differences is that my FPS dropped to 3 and I couldn't get it to go away.
April 2018 - last edited April 2018
This BUG happened to a friend of mine today while we played together. Curiously we all noticed he started to lag in the beginning of a specific match, and only in this match he got this BUG several times. I think this gives even more proof that a laggy environment causes this BUG. I suggest the devs to recreate a laggy game to check this, as this is the third time I see someone lagging (including myself in the video provided) and facing this Eternal Choke State BUG. I hope this helps even further
April 2018 - last edited April 2018
Yet again it happened, now on Ewok Patch, so it isn't fixed as of current patch
Here is a video RogueOneKenobi sent me of his experience with the bug. He had some problems on recording it, so it came with no sound and one skip of some frames near the end, but the BUG can be seen with no problems:
The force choke is indeed still in need of a fix. It creates many times a shocking screen for the one being choked and there is nothing you can do about it.
I can confirm that this bug is still happening on PC (27-04-2018).
It seems to me that the bad state and the spasm out of the one being choked are related to when the enemy player is choked. So if that player has some velocity or jumps, then there is a higher chance that the bug occurs.
June 2018 - last edited June 2018
I've seen an enemy Vader dealing with this BUG 2 days ago, so it's still a thing as of May's Hotfix (or "Hotbreak" as the community kindly nicknamed it)