DSCC is a free local Windows app for tuning DualSense and DualSense Edge adaptive triggers, haptics, lights, and profiles. Everyday setup needs no scripts or command line. Linux remains beta.
Install 0.5.1 — Windows Standard MSI Unsigned: Windows may show trust prompts. Release notes and checksums.
- Verify the MSI's SHA256 checksum and signing status using Release Trust.
- Quit any running DSCC from its tray menu, then run the MSI to install or update. Profiles/settings stay in your user folder. Leave Start with Windows unchecked until its validation caveat is resolved.
- Open DSCC from Start or the tray; connect the controller by USB or Bluetooth.
- Follow Guide and tune the Global Profile. Start a supported game for automatic Game Profile selection and telemetry effects.
Controller/transport coverage, installer lifecycle, Bridge validation and signing have remaining validation gaps. Check the hardware matrix for actual evidence.
| Workflow | Controls / setup |
|---|---|
| Controller tuning | L2/R2 resistance, clicks, feedback curves, rumble, lightbar, battery and connection status. |
| Profiles | Save, import, export, rename and switch tuning. |
| Forza Horizon 5 / Horizon 6 / Motorsport | Enable Data Out / UDP Race Telemetry at 127.0.0.1:5300; brake, ABS, throttle, shifts, limiter, texture, slip and RPM effects. |
| Assetto Corsa Rally | Windows shared memory; enter a driving session and select the detected profile. No port setup. |
| Steam Input | Mirror supported mappings and apply the Edge paddle-shift preset; edits create backups. |
| Edge slots / optional Input Bridge | Follow the hardware matrix / installer guide. Live telemetry effects require DSCC running. |
The API defaults to 127.0.0.1:43473; Forza UDP defaults to
127.0.0.1:5300. LAN exposure requires opt-in. Validated output frames guard
controller writes; no raw HID-write routes exist. Game trigger/rumble effects
require an active Game Profile and fresh telemetry; manual tests expire.
- Setup or connection trouble: Troubleshooting.
- Bugs: export a sanitized bundle from Support, then file an issue. Tuning questions: Discussions.
- Development: Contributing covers safe runs and
npm.cmd run check; docs index maps source owners and workflows.
DSCC follows a clean-room provenance policy.
Code uses Apache-2.0; bundled assets/dependencies retain their
third-party terms. Bridge distributions include the
HIDMaestro MIT notice in hidmaestro\THIRD_PARTY_NOTICES.txt.