Steam Link

Steam Link

[BUG] Meta : flat mode : 'X' button not recognised on PS4 DS4 Gamepad
BUG REPORT

In Steam Link for Meta Quest, when using flat-screen / non-SteamVR mode, the Cross / X button on a Sony PlayStation 4 DualShock 4 controller is no longer recognised.

This appears to be a regression, as it used to work.

The controller is already connected to the Quest 2 via Bluetooth and working before launching the Steam Link app.

Expected behaviour

The DualShock 4 Cross / X button should be recognised in Steam Link flat-screen mode, as it previously was.

Actual behaviour

All other DualShock 4 buttons appear to work, but the Cross / X button input is not recognised in Steam Link flat-screen mode.

Where the controller still works correctly
  • Meta Quest 2 system UI and other Quest apps
  • Virtual Desktop
  • Steam Link when using normal SteamVR mode
So the controller itself, Quest Bluetooth pairing, and Steam input generally appear to be working. The issue seems specific to Steam Link’s flat-screen mode on Quest.

Configuration

Host PC
  • Windows 10
  • Intel i5-4460
  • 16 GB RAM
  • Nvidia RTX 3060 Ti 8 GB
  • Steam client tested on both normal and beta branches
  • Steam build: 1779155395

Client device
  • Meta Quest 2
  • OS version: v2.3.1034
  • Build: 5215047.3460.150
  • Steam Link app version: v2.0.22.2080

Controller
  • Sony PlayStation 4 DualShock 4
  • Version 2 / CUH-ZCT2
  • Connected via Bluetooth directly to the Quest 2 before launching Steam Link

Reproduction steps
  • Pair and connect a DualShock 4 V2 controller to the Meta Quest 2 via Bluetooth.
  • Confirm the controller works in the Quest UI or another Quest app.
  • Launch Steam Link on Quest.
  • Use Steam Link in flat-screen / non-SteamVR mode.
  • Attempt to use the Cross / X button.

Result

The Cross / X button is not recognised in Steam Link flat-screen mode.

Additional note

The same controller works correctly in Steam Link when using SteamVR mode, and also works correctly in Virtual Desktop, which suggests the problem is probably in Steam Link’s Quest flat-screen mode input handling rather than the controller or Quest Bluetooth pairing.
< >
Showing 1-2 of 2 comments
This is an issue with SDL3 on Android that was already fixed, where anything connected by Bluetooth (and thus handled by Android directly) would lose the first button in the mapping.

The fix for that particular issue made it into the 1.3.28 build for the normal Android client, but the Quest client is a special build... and unfortunately, the 2D part of it is still functionally the 1.3.27 build, so doesn't have the controller fixes in 1.3.28 and 1.3.29.

The next Quest build will pick up those fixes, and the issue with the DualShock controller should go away.

If you need an interim workaround in the meantime, you CAN connect the controller via USB-C to the headset, though I realize that's not particularly optimal. But if you do, Steam Link will use the controller in raw USB mode, meaning it's not a system controller, meaning the bug doesn't trigger that eats the first button mapping.
Originally posted by Packetdancer:
...

The next Quest build will pick up those fixes, and the issue with the DualShock controller should go away.

If you need an interim workaround in the meantime, you CAN connect the controller via USB-C to the headset, though I realize that's not particularly optimal. But if you do, Steam Link will use the controller in raw USB mode, meaning it's not a system controller, meaning the bug doesn't trigger that eats the first button mapping.

Thanks so much for such a detailed and helpful reply!

(And I hadn't thought of trying wired. If needed I'll do that until it's fixed.)

As we say in the UK:

Nice one! 😊👍
< >
Showing 1-2 of 2 comments
Per page: 1530 50