You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/README.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,21 @@ Linux runners install `libudev-dev` so `hidapi` can compile.
22
22
23
23
It builds:
24
24
25
-
- Unsigned Windows MSI.
25
+
- Unsigned Windows Standard MSI.
26
+
- Unsigned Windows Bridge MSI.
27
+
- Unsigned Windows Bridge framework-dependent MSI.
26
28
- Windows raw binary zip.
27
29
- Linux beta archive with bundled web UI.
28
30
- SHA256 checksum files.
29
31
32
+
Windows installer intent is deliberately explicit:
33
+
34
+
| Artifact | Default audience |
35
+
| --- | --- |
36
+
|`standard`| Most users. Controller tuning, profiles, haptics, telemetry, diagnostics, and Steam Input support without the non-Steam bridge broker payload. |
37
+
|`bridge`| Users testing DSCC Input Bridge for non-Steam games. Bundles the self-contained HIDMaestro broker. |
38
+
|`bridge-framework-dependent`| Advanced bridge users with the matching x64 .NET runtime already installed. |
39
+
30
40
The release workflow publishes the GitHub Release and uploads artifacts. Windows
31
41
artifacts are unsigned unless signing is added later.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+60Lines changed: 60 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,63 @@
1
+
# DualSense Command Center 0.3.1
2
+
3
+
Latest release notes are listed first. For install steps, start with the
4
+
[README](README.md).
5
+
6
+
Release date: 2026-05-26
7
+
8
+
0.3.1 splits Windows installers into clear, named choices so the normal user
9
+
path stays slim while non-Steam bridge testing remains available.
10
+
11
+
## Windows Installers
12
+
13
+
Pick one installer. Do not install Bridge unless you need non-Steam DSCC Input
14
+
Bridge testing.
15
+
16
+
| Installer | Intended user | Why it exists |
17
+
| --- | --- | --- |
18
+
|**DSCC Standard**| Most users | Smallest normal install. Includes profiles, haptics, telemetry, diagnostics, controller tuning, and Steam Input support. Does not bundle the HIDMaestro broker. |
19
+
|**DSCC Bridge**| Non-Steam bridge testers | Bundles the self-contained HIDMaestro broker so DSCC Input Bridge can create a virtual Xbox 360 controller for local non-Steam app profiles. |
20
+
|**DSCC Bridge Framework-Dependent**| Advanced bridge testers | Bundles the smaller framework-dependent broker and requires the matching x64 .NET runtime to already be installed. |
21
+
22
+
## Packaging
23
+
24
+
- Added explicit `Standard`, `Bridge`, and `BridgeFrameworkDependent` MSI
25
+
flavors to `packaging/package-msi.ps1`.
26
+
- Standard packaging no longer requires or stages any `hidmaestro` broker
27
+
payload.
28
+
- Bridge packaging still validates that the broker output shape matches the
29
+
selected flavor, so a framework-dependent build cannot accidentally package a
30
+
self-contained runtime shape.
31
+
- The tag release workflow now builds and uploads all three Windows MSI
32
+
variants with flavor names in the artifact filenames.
33
+
- Release notes now tell users to choose Standard first and use Bridge only for
34
+
compatibility beyond Steam.
35
+
36
+
## UI
37
+
38
+
- Moved the Controllers page tuning bar to the top of the page so Controllers,
39
+
Adaptive Triggers & Haptics, and Button Mapping use the same command layout.
40
+
- Kept Profiles focused on game/profile scope selection, with controller
The MSI is unsigned, so Windows SmartScreen may warn you. DSCC stores profiles
18
18
and settings in your user folder and preserves them during upgrades. Continue
19
19
past SmartScreen only if you downloaded the MSI from the official release page
20
20
and checked it against the published checksum when needed.
21
21
22
+
## Which Windows Installer Should I Use?
23
+
24
+
Pick one. Most people should not install the larger bridge build.
25
+
26
+
| Installer | Use this when | Includes non-Steam DSCC Input Bridge broker? | Notes |
27
+
| --- | --- | --- | --- |
28
+
|**DSCC Standard**| You want controller tuning, profiles, haptics, telemetry, diagnostics, Steam Input support, and the smallest normal install. | No |**Recommended for most users.** Non-Steam bridge screens stay available but show the provider as not installed. |
29
+
|**DSCC Bridge**| You want to test DSCC Input Bridge with local non-Steam games and you do not want to install a separate .NET runtime. | Yes, self-contained | Larger installer. Best plug-and-play bridge option. |
30
+
|**DSCC Bridge Framework-Dependent**| You want bridge support and already have the matching x64 .NET runtime installed. | Yes, framework-dependent | Smaller than Bridge, but it has a prerequisite. Advanced users only. |
31
+
32
+
Steam games and normal controller tuning do not need the Bridge installers.
33
+
Use Bridge only to expand compatibility beyond Steam.
34
+
22
35
## Quick Start
23
36
24
-
1. Download and run the Windows MSI.
37
+
1. Download and run the **DSCC Standard** Windows MSI unless you specifically
38
+
need non-Steam DSCC Input Bridge testing.
25
39
2. Launch **DualSense Command Center** from the Start menu.
26
40
3. Connect a DualSense or DualSense Edge controller over USB or Bluetooth.
27
41
4. Open DSCC from the tray icon, or visit `http://127.0.0.1:43473/`.
0 commit comments