How R6 Console Mouse and Keyboard Changes Matchmaking Pools in Y11S2.2

Rainbow Six Siege Y11S2.2 introduces native mouse and keyboard support on consoles on July 14, 2026. The important technical detail is that the input device and matchmaking pool are connected. Connecting a keyboard does not silently move every controller player into mixed-input matchmaking, and console-only pools remain controller-only.

The update adds a clear configuration choice. Players who select the PC & Consoles setting can use native mouse and keyboard and enter the PC crossplay pool. Players who stay in console crossplay or a platform-specific console pool continue with controllers. ALVIRAN's setup model separates device detection, pool selection and squad behavior so each change is predictable.

What changes in Y11S2.2

The new system supports native mouse and keyboard in menus and matches when the account is configured for the PC & Consoles pool. Console text chat also arrives with the update. A connected keyboard can be used for chat, while controller users can use the console's on-screen keyboard.

The pool rules can be summarized as follows:

• PC & Consoles: mouse and keyboard or controller; PC players and opted-in console players share the PC crossplay pool.
• Console crossplay: controller only; console players can match across supported console families.
• Platform-specific console pool: controller only; matchmaking stays on the selected console platform.
• Squads containing a PC player: the squad uses the PC & Consoles configuration.
• Local Custom Games: the lobby host controls the allowed input-device setting separately.

This is a configuration boundary, not a promise that every lobby has an equal input mix. The selected pool determines which device rules and matchmaking population apply.

How to set up native mouse and keyboard

After the Y11S2.2 update is available, use a controlled setup sequence:

1. Install the game and console system updates normally.
2. Connect the mouse and keyboard directly to supported console ports.
3. Open Siege settings and find Crossplay & Input Devices.
4. Select PC & Consoles before expecting mouse and keyboard input in matches.
5. Confirm the pool notice in the squad panel before queuing.
6. Configure sensitivity and key bindings in the Controls section.
7. Test movement, aiming and text chat in a training mode before entering a live match.

If the device is detected while a console-only pool is selected, the game should prompt for the compatible setting. Do not troubleshoot sensitivity or bindings until the selected pool actually permits the device.

How squad leadership affects the setup

In a squad, the leader's Crossplay & Input Devices setting determines the matchmaking pool and permitted devices. Squad members should see the selected rule in the squad panel and through a notification before the match.

This matters for mixed groups. A console player joining a PC friend should expect the PC crossplay pool. A console-only group that wants controller-only matchmaking should verify the leader's setting before queuing. If the composition changes, check the squad panel again instead of assuming the previous pool remains active.

What stays controller-only

Console crossplay and platform-specific console matchmaking remain controller-only choices. A connected mouse and keyboard does not become usable there. This separation gives controller players a path that avoids the PC crossplay pool while still allowing others to opt into native mouse and keyboard support.

Training and offline playlists follow the crossplay/input-device setting for native mouse and keyboard. Local Custom Games are the exception because the host can define allowed input devices in the lobby configuration.

Technical troubleshooting checklist

If native input does not work after launch, verify the system in layers:

• confirm that Y11S2.2 is installed and the game has restarted
• confirm that the console recognizes both devices
• verify that PC & Consoles is the active pool
• check the squad leader's setting when grouped
• test another supported console port without an unverified adapter
• reset only the affected key binding or sensitivity option
• test in training before changing several settings together

Avoid unsupported adapters or tools that translate input for a controller-only pool. Native support is designed around the visible PC & Consoles configuration, and bypassing that boundary is not the same feature.

FAQ

Does Y11S2.2 force controller players to face mouse and keyboard?

No. Console-only matchmaking options remain controller-only. Native mouse and keyboard requires the PC & Consoles pool.

Where can I compare every pool and setup step?

The ALVIRAN R6 Y11S2.2 console mouse and keyboard guide explains pool selection, squad-leader behavior, text chat, training modes and day-one troubleshooting in one reference.