Repository navigation
v0.2.1
Snappier sticks on the Switch 2, and two ways back to dongle mode for a puck whose controller can no longer send the chord.
Lower latency
- Reports go out as input arrives. As a Switch 2 Pro Controller or the Joy-Con pair, the puck sends a report as soon as the Steam Controller's input reaches it, with a 4 ms fallback, the timing of a real Pro Controller 2. It was a fixed 8 ms.
Getting back to dongle mode
Pairing the Steam Controller to another puck in the same slot takes it away from this one, and then nothing can hold the chord that reaches dongle mode. Now there are two ways back without one (#3):
- Replug three times. Plug the puck in and pull it out twice, a second or two each time, then plug it in a third time and leave it. That power-up is the Steam dongle.
tools/bootsel.ps1 -Donglefrom a Windows PC, with the puck plugged in as a Switch 2 Pro Controller or the Joy-Con pair.
Either way it lasts one power-up, as the chord does. Pair the controller again from there, on its second slot if it is also paired to a Valve puck (see "Pair the Steam Controller" in the README).
Updating from v0.2.0
- In dongle mode, open the config page and press Update firmware. As a Switch 2 Pro Controller, run
powershell -ExecutionPolicy Bypass -File tools/bootsel.ps1instead. Then copyswitch2_ll.uf2onto theNICENANOdrive. Pairings and settings are kept. - The two ways back only exist once a puck runs v0.2.1. A puck already stuck on v0.2.0 can be reset to a bare board with
wipe.uf2, attached here: get theNICENANOdrive withtools/bootsel.ps1or by tapping RST to GND twice quickly, copywipe.uf2onto it, wait for the drive to come back, then copyswitch2_ll.uf2. It starts fresh in dongle mode, with nothing paired.