For a few days, the most recent installment within the Rainbow Six saga has been available under the title of ‘Extraction’. Its predecessor, Rainbow Six Siege, boasts a solid base of active players.

However, considering that the game has only been on the market for a short time, the first players are facing some issues that require a future fix to achieve the most optimal experience possible.

Here we have already covered some of the first problems related to the game (1, 2, 3, 4). Now, new reports point out that there is a bug with the ‘revive’ system that directly affects the gameplay (1, 2, 3, 4, 5, 6).

Rainbow Six Extraction ‘revive’ function is not working properly. So, many times, when a player wants to revive a teammate down, this will not be possible (1, 2, 3, 4, 5, 6, 7).

Rainbow Six Extraction ‘revive’ doesn’t work sometimes

According to multiple reports, there is a glitch that can appear randomly. This causes Rainbow Six Extraction players to not be able to revive another.

Bug:Careful with Reviving, it doesn’t work all the time.

It first happened to a player i was trying to revive and now it happened to me, it fills the bar but the player is still down. Rarely happens but it could take your whole team down trying to revive someone. also you could hold it a few more secs more but i would stop after the 3rd try

When the glitch occurs, the progress bar for reviving the teammate reportedly stops short, or even if it does fill up, the teammate does not revive.

I have been experiencing a revive bug sometimes where even though I hold F the revive will stop at the very end of the progress bar.

It does not seem to happen all the time and I cannot find a reliable way to replicate this bug. Just seems to happen sometimes.

It can happen multiple times in a row as well, so it is not limited to one messed up revive.

Ubisoft is aware, potential workaround

Currently, the Ubisoft team is aware of the bug (1, 2). The company is investigating this in order to develop a fix. However, there is no estimated arrival date for it yet.


In the meantime, there is a workaround that reportedly helps mitigate the issue. This basically consists of keeping the revive button pressed for an additional time than the interface indicates.

I ran into this a couple times, and the solution seemed to be to just hold down the revive button for an extra second or so. If I let off right after the indicator filled and disappeared, about half the time the player would go back down.

Could be a slight latency problem.

If new developments related to this matter emerge in the coming days, we will update this article. So, stay tuned with us.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.

Jean Leon
1613 Posts

A tech enthusiast since ever. I like to always be up to date on the latest news in the industry and write about it. Twitter: @jean_ERdC

Next article View Article

Google Drive not letting users play videos, throws 'allowed playbacks has been exceeded' error

Google Drive users have been dealing with an issue for years where they get an 'allowed playbacks has been exceeded' error when trying to play videos. And Google has still...
Feb 20, 2024 2 Min Read