The issue I am having after the most recent update is identical to the issue that was previously resolved for a short period of time before returning now. The game audio cuts out when there are a lot of things going on and making in-game noise all at the same time; this happens for about 20-30 seconds during which you can still run around and play as normal but with no audio for that 20-30 seconds before the game freezes and forces you to reset your game.
I can confirm this issue is still present. During the loading screen or just while playing, the game crashes without showing any error message whatsoever. Restarting it once doesn't always help.
For me, this issue started occuring after the mid season patch for Xox (just before the Halloween event came out).
Ill set the scene.... ranked on coastline, the game is 4-4 and we go defence in kitchen... the round starts and I move forward to go and reinforce, vigil throws an impact grenade to make a rotation and then boom! My game audio cuts out and after 20 seconds of me moving around and finishing reinforcing/putting my gadgets down I freeze and am forced to reset my game. Then I load my game back up to be welcomed by an abandon sanction message and have to wait half an hour to join my squad back and play. Please Ubi can you fix this it once and for all, as your game in this current state with this audio bug is unplayable for me.
This is sadly a regular thing happening for me this season... usually I rank myself in high gold and try my best to grind up to plat, but maybe 6 out of my 10 ranked games my audio would cut out and shortly after my game would freeze. Not only that, but this is happening multiple times in multiple games; it doesn't matter if it's Ranked, Quick Play, Custom Games, or the Sugar-Hunt-Thingy... I submitted a case for it and in there I stated that I've tried virtually everything I could do and even payed for a new digital version of the game in hopes that it was something wrong with my disc (though unlikely, I thought might as well since the game was on sale for 10 dollars).
Hi everyone, thanks for getting back in touch about this.
This reported fixed after a hotfix patch on the 14/10/2020.
If you are still experiencing this now, could you please make sure to follow the troubleshooting guide for your platform to see if this can resolve the issue for you -
XB1: http://support.ubi.com/faqs/000026628
PS4: https://support.ubi.com/faqs/000025633
PC: https://support.ubi.com/faqs/000025947
If the above troubleshooting does not work for you, please let us know the following -
- Your Ubisoft ID
- Platform you play on
- If console, do you have the game installed on an internal hard drive or external one?
- When this last affected you?
- What were you doing in the game when the audio cut off then crashed?
If you are still receiving these crashes where the audio will cut out for 30 seconds, please can you answer the above questions and we will happily reopen the investigation with the game team, thank you!
Ubisoft ID - Geekzs
Platform - Xbox
Xbox Gamertag - Teq
I have had the game installed on both my internal and the external hard drive and have experienced the problem on both but all my other games run smoothly and with no issues. I have also played on a different Xbox Console and experienced the same issue.
I was last affected by this issue on Saturday November 7th 2020.
My game can have the audio cut out and crash at random unpredictable times throughout a game of Rainbow Six Siege; it mostly cuts out and crashes however after a sequence of loud audio noises happen all at once in game e.g. multiple walls being reinforced at the same time as someone making a rotation on another wall with an impact grenade. This needs to be looked into in more depth by Ubisoft and fixed ASAP as its making the game unplayable for me and other players.
I've still got this problem. Had it since Shadow Legacy started and basically stopped playing a month ago because I was getting frustrated crashing out every game. I've tried all the troubleshooting steps and no luck fixing the problem. Stumbled onto this thread and now I'm hopeful because at least the devs know about the problem.