Movement speed on revive
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number AMD RX 580
Enter RAM memory size in GB 32
What is your gamertag/PSN ID/EA Account name? NawwDidums
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)? Wraith
Which Legends were your squad mates using (if applicable)? Pathfinder
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Slums, top left of the map
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Fighting
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? 1
When did this happen? (dd.mm.yy hh:mm) 13/02/2019 17:00
How often does the bug occur? Rarely (0% - 9%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? I was downed after a fight, after using my knockdown shield to stay alive, my teammate revived me, however the sound of the shield was still playing. When I eventually got revived, I could no longer run, or sprint. it seemed that I was locked into crawl speed, after downing my self to try and fix it, it still persisted, also tried to drop my knockdown shield, with no avail.
What should be happening instead? Moving at the correct pace
Steps: How can we find the bug ourselves? not 100%, get downed, toggle knockdown shield when necessary, crawl to teammates, get revived. Try move.
I was downed after a fight, after using my knockdown shield to stay alive, my teammate revived me, however the sound of the shield was still playing. When I eventually got revived, I could no longer run, or sprint. it seemed that I was locked into crawl speed, after downing my self to try and fix it, it still persisted, also tried to drop my knockdown shield, with no avail.
This issue should now be resolved, please confirm either way, thanks.
Here are the most recent patch notes: LINK