Hello everyone,
I do apologise that we were unable to provide updates on this thread between my initial post on page three, and the first update from my colleague Baron on page 19. We were using the files in the cases you all raised to investigate the issue, and identify the specific CPUs impacted. As many of you have communicated, the issue should now be resolved, as we implemented a fix in the Y4S3.2 patch. Thank you all for your patience and understanding throughout the investigation period.
Just to answer / address a few posts in the thread that I noticed while catching up...
I'd just like to remind you that the purchase and sale of Ubisoft Accounts is against our terms of use / service, basto.-. I would recommend that you re-read them if having any questions about thisOriginally Posted by basto.- Go to original post![]()
As above, cliff527, I do appreciate that the lack of communication in this thread was less than ideal, and I do apologise for this. I've ensured to raise this with my colleagues and all of the relevant teams so that in future, we can try to get more public messages out there should a similarly widespread issue occur.Originally Posted by cliff527 Go to original post
Just to clarify matters slightly - while the CPUs that were affected by this issue were / are within the passmark boundaries, it is their architecture that (technically) makes them fail to meet the minimum requirements for Rainbow Six Siege. That said, they are - as this thread shows - capable of running the game on some players' systems, and we recognised this, and ensured to investigate to rectify the issue as quickly as we could.Originally Posted by cliff527 Go to original post
I do apologise that the resolution for this issue was not clearly communicated in the patch notes for Y4S3.2. We did mention in the Y4S3.1 patch notes that we had resolved crashes in PlayStation 4, and were still investigating those occurring on PC and Xbox One, but having reviewed the notes myself now for Y4S3.2, I do see that the resolutions for these platforms was missed from the notes in error.Originally Posted by cliff527 Go to original post
Sincerely, please accept my apologies for any inconvenience or confusion this caused. I'll raise this with our Rainbow Six Siege team.
Hey there xXJokunenXx - this issue is not related to the wider issue of this thread, and as such, I'd recommend posting on a more appropriate thread, or creating your own if one is not available.Originally Posted by xXJokunenXx Go to original post
That said, we do have some steps that I'd recommend trying here in the meantime.
Hello iiaykut - I do believe I've answered you regarding this issue on another thread, and as above, this issue is not the same as the one described in this thread. Please continue to post in a more appropriate thread, rather than in this one. Thank you.Originally Posted by iiaykut Go to original post![]()