🛈 Announcement
Greetings! The Rainbow Six Siege forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #191
    I can confirm it works on 6000 series
     1 people found this helpful
    Share this post

  2. #192
    Fix on xeon x5450
     1 people found this helpful
    Share this post

  3. #193
    what i said. we didnt get anything for 26 days... but check now... full server down for a few hours, and everybody will get 3 day booster... just watch it
     1 people found this helpful
    Share this post

  4. #194
    Still..Ubisoft service is currently unavailable. You can try again later.
    Im from Helsinki Finland.. Reinstalled Ubi x 2..
    Share this post

  5. #195
    imeem's Avatar Junior Member
    Join Date
    Jul 2016
    Posts
    27
    seems to be fixed on Q8400
    Share this post

  6. #196
    UbiShikallum's Avatar Community Manager
    Join Date
    Jul 2017
    Posts
    3,809
    Hey,

    Thanks for sharing how everything is on your end
    Share this post

  7. #197
    Q9550 seems to be fixed for now. Thx for that..Lets see after next update what happens?
    Share this post

  8. #198
    what i said... all players get 1 day boost for nothing...

    and what we get for this glitch? Nothing.... Thank you loosersoft
    Share this post

  9. #199

    find a solution ?

    i have been waiting for 1 week for a support.
    # 10078555

    Intel Core i5-4210H 2,9 GHz 3MB
    GPU: NVIDIA GeForce GTX 860M 2GB
    RAM: 8 GB DDR3L SDRAM
    HDD: 128 SSD
    Windows 10
    Share this post

  10. #200
    Ubi-Woofer's Avatar Ubisoft Support Staff
    Join Date
    Aug 2019
    Location
    United Kingdom
    Posts
    2,882
    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...

    Originally Posted by basto.- Go to original post
    i have the same problem after the new update , this is my pc detials .. i just want to know if its gonna work on my pc anymore or sell my account !?

    Processor: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz (8 CPUs), ~2.8GHz
    Memory: 9216MB RAM
    DirectX Version: DirectX 12
    Operating System: Windows 10 Pro 64-bit
    Card name: AMD Radeon HD 7700 Series
    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 this

    Originally Posted by cliff527 Go to original post
    The communication could've been better in 2-3 weeks since this came up, but whatever. Everyone's busy, I guess.
    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
    [...] apparently you have support people still telling people their system doesn't meet minimum spec, which is not accurate. That's really shameful, to just blame it on a problem that isn't the problem - especially from within the company. Plenty of source out here have identified what the actual problem is, and the support people need to stop being lazy.
    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
    Second - and more serious than the support issue: Our developers were *never* allowed to put fixes into patches without it being documented. This was a 'hangin' offense if they were caught (and it did happen). Not putting fixes like this in release notes simply serves to obscure the issues that do occur, and there is no reason to sneak stuff in without documenting it. Yet, this specific fix/bug isn't mentioned at all in the release notes over on the News page. Why is that?
    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.

    Sincerely, please accept my apologies for any inconvenience or confusion this caused. I'll raise this with our Rainbow Six Siege team.

    Originally Posted by xXJokunenXx Go to original post
    Still..Ubisoft service is currently unavailable. You can try again later.
    Im from Helsinki Finland.. Reinstalled Ubi x 2..
    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.

    That said, we do have some steps that I'd recommend trying here in the meantime.

    Originally Posted by iiaykut Go to original post
    i have been waiting for 1 week for a support.
    # 10078555

    Intel Core i5-4210H 2,9 GHz 3MB
    GPU: NVIDIA GeForce GTX 860M 2GB
    RAM: 8 GB DDR3L SDRAM
    HDD: 128 SSD
    Windows 10
    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.
    Share this post