R6FIX faq

R6FIX How-to

This website is a tool that allows the community to report and aid us in prioritizing in-game issues. When you encounter an issue while playing the game, visit this site and file an issue report. If enough players agree that the issue is reproducable and worth fixing, it becomes Confirmed. Each issue needs 20 players to reproduce it within the first 14 days of the issue being reported in the Live game, or it will expire.

The issue report is then triaged. Players can prioritize issues by up-voting and down-voting. Developpers will put more focus on examining the highest-ranked issues.

Can everyone contribute to R6FIX?

No, at this point you must login with your Ubisoft account to contribute on the platform.

What does it mean when a report is “Confirmed”?

A report becomes “Confirmed” once at least twenty (20) users report that they have been able to replicate it when playing the Live game. This saves the issue from expiration and keeps it in the system until it is either fixed or overturned by a Moderator, Developer, or Admin. Users vote on Confirmed issues so that they can have a better chance at being recognized by the Rainbow6 developers.

What does it mean when a report is “Acknowledged”?

The “Acknowledged” status means that the issue has been imported into Rainbow6’s internal JIRA issue tracking application as a ticket.

Do the Rainbow6 developers really look at the tickets that are created?

The reports that are Acknowledged are tracked in the same flow as the issues that are being reported internally. Some tickets take longer than other to reproduce and to fix.

What are these Computer/PS4/Xbox Specs? How do I change it?

The Computer Specs contains information about your computer and may explain why you encountered an issue that another user is unable to replicate. The simplified form could indicate if an issue is performance-based but, by uploading a DXDiag file, you can help developers pinpoint issues more easily.

I use more than one computer to play Rainbow6. Can I save more than one Computer Specs?

At this stage of the R6FIX, we are still examining how users interact with the system which means keeping some features simple.

What are some tips for creating the best issue reports?

The best issue reports contain:

  • Every step, in detail, needed to experience the issue. Even steps that do not seem relevant are sometimes important to the overall issue.
  • Attempt to replicate the issue a few times yourself before entering it in the system. Make sure you have a clear understanding of the process it takes to experience it.
  • As much information about the computer setup as possible. Were you playing on two monitors? Did you have video-capturing software running?
  • A clear “Expected Result” which details clearly how it differs from the “Actual Result”.
  • Media, whenever possible.
  • Don’t be afraid to open up your screenshots in an image editing software and draw some red rectangles and arrows around the areas that show the issue. A picture is worth a thousand words!

Most important, when reporting an issue, be patient and detail oriented!

My issue is similar to another report but not quite the same. How can I be sure whether it’s a duplicate or not?

If you cannot decide whether an issue is a duplicate or not, ask yourself “If this other issue is fixed, what are the chances it will fix my issue as well?”. If you’re still not sure, submit it anyways and let the community figure it out!

I created a valid report but no-one has reproduced it. This issue significantly hinders my gameplay experience. What can I do to boost awareness?

The R6FIX was conceived so that all valid reports would have a fair chance to be recognized and eventually examined by Rainbow6 developers. That being said, you can always ask your peers to pitch in or post a link to your issue in the forums to encourage others to take a look at your report.