This comes up often enough in Rainbow Six Siege that it deserves a straight answer rather than a thread to scroll through.

Short answer

Do the simple thing first. It is correct more often than the complicated thing people recommend instead.

  • Note the exception cases — they are specific rather than vague.
  • Try the straightforward approach before the elaborate one.
  • Keep a save or backup from before you start — it costs nothing and occasionally saves an evening.

Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. The accepted community answer is broadly right and wrong in a specific way that matters here. Edge cases are genuinely rare, which is why the simple answer is usually the correct one.

Why it works this way

The community wisdom on this is roughly half right, and the half that is wrong costs the most time. The mechanic behind it is simpler than the discussion around it suggests. Testing this yourself takes a few minutes and settles it definitively. There is no hidden trick here that the game is keeping from you.

Most of the disagreement online comes from people describing different versions of Rainbow Six Siege. It is worth separating what the game does from what players have concluded it does. Nothing here assumes a particular playstyle beyond wanting the thing to work.

Worth knowing alongside this

Nothing here depends on a setting you are unlikely to have. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing.

  • Check which version any conflicting advice was written for.
  • Test it yourself where testing is cheap.
  • Give a method one honest attempt before deciding it does not work.
  • Revisit after a major patch if the behaviour changes.
  • Do not build a routine around an edge case.

What to do instead

If you are coming to this after a long break, the terminology has probably moved on. Most of the disagreement you will find online is two people describing different builds. The awkward part is rarely the step itself, it is knowing which step comes first. Where something depends on your platform or region, that is called out rather than glossed over.

Everything below is framed around the current state of Rainbow Six Siege rather than a launch-week impression. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Rainbow Six Siege is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

When the usual advice fails

What follows assumes you are on a current install and have not modified it. If your result differs from what is described here, note what is different first rather than starting over. Do the cheap check before the expensive one — that ordering alone saves most of the frustration.

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. A single check up front replaces a lot of guessing later. Treat anything stated without a version number as provisional.

The practical answer

The developers have changed their mind about this at least once, which explains the older advice. Where two approaches both work, the one with fewer moving parts is the one to keep. If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about.

Where people go wrong

  • Grinding a method that was patched months ago because a thread still ranks well.
  • Downloading a helper tool for something the game already does in its own menu.
  • Trusting a video thumbnail that promises a result the video never actually shows.

Siege FAQ

Is this still accurate after the latest Rainbow Six Siege update?

The method is; individual numbers may not be. If a value on your screen differs, trust the screen and keep the sequence.

Does this work the same on console and PC?

The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.

Does this change between platforms?

The behaviour does not. Where menu paths or prompts differ, that is noted above.

Is there a faster method?

Sometimes, at the cost of reliability. Where that trade exists it is described rather than recommended blindly.

Bookmark it if you like, but honestly, once you have done it once you will not need to come back.