Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 6 additions & 17 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,26 +1,15 @@
# Changelog

## Unreleased
## v0.7.0 - 2026-08-08

### Added
- **Automatic update checks and one-click updates.** FanaBridge now checks GitHub for new releases and offers to install them, with a restart of SimHub to finish. Can be turned off in About. ([#96](https://github.com/kelchm/FanaBridge/pull/96), closes [#95](https://github.com/kelchm/FanaBridge/issues/95))
- **A wheel's segment display can now be left to another application.** Display Mode "None" stops FanaBridge writing to it, so Fanatec's own software can drive the display while FanaBridge keeps the LEDs. The option previously existed only for the legacy page of ITM wheels. ([#97](https://github.com/kelchm/FanaBridge/pull/97))
- **Automatic update checks and one-click updates.** FanaBridge checks GitHub for new releases at startup and can install an update from its settings page, ready for a SimHub restart. Update checks can be turned off in About, and installations that cannot be completed automatically fall back to the release download page. ([#96](https://github.com/kelchm/FanaBridge/pull/96), closes [#95](https://github.com/kelchm/FanaBridge/issues/95))
- **Basic segment displays can now be left to another application.** Display Mode "None" hands off the display while FanaBridge continues driving the LEDs; it was previously available only for the legacy page of ITM wheels. ([#97](https://github.com/kelchm/FanaBridge/pull/97))

### Fixed
- **Device settings are no longer erased while FanaBridge is disabled.** SimHub rewrites each device's settings file whenever it saves, and it does so whether or not the plugin is running. FanaBridge only built its LED editor once the plugin was up, so a save taken before that — most obviously with the plugin disabled — wrote a settings file with no LED data over one that had it, replacing hand-built profiles with a stub. The editor and everything a device stores are now built with the device itself, so a device can always describe its settings. If it ever cannot, it declines to save and SimHub keeps the existing file.
- **Settings written by another version are no longer dropped.** A device only wrote back the settings it recognised, so anything stored by a newer build was lost on the next save. Unrecognised settings are now kept as-is. (Settings nested inside the LED module's own data are the exception — the module rewrites those wholesale.)
- **LED data for channels the current wheel cannot drive is no longer deleted.** Saving reported those channels as empty, which erased their stored profiles.
- **The Screen and Tuning tabs no longer disappear when FanaBridge is disabled.** They stay in place, greyed out along with the rest of the device's settings — the same treatment SimHub gives a device you have switched off. A device that could not describe what it had stored was how those settings got erased in the first place.
- A profile override that changes a wheel's LED layout is now applied when devices are registered, so restarting SimHub gives the LED editor the right number of slots. A display-only wheel given LEDs by an override previously had no LED editor at all.
- Pulling the plugin out from under a running device no longer risks an error from the LED output path, and a device idle while the plugin was down now resumes output when it returns.
- **Switching a device off in SimHub now actually stops it.** The toggle had no effect: SimHub asks every device for an update whatever its switch says, and reads the switch only afterwards, to decide what state to display — so FanaBridge kept driving the LEDs and display of a device the user had turned off. Switching one off now stops its output and darkens its LEDs, rather than leaving them lit on the last frame drawn.
- **A device now shows as not enabled while FanaBridge is disabled, instead of looking live.** SimHub greys out a device's settings while it has nothing to drive it, and the header says so. The user's own on/off choice is untouched — a device switched on stays switched on, and comes back when the plugin does.
- The device list keeps up with the plugin being enabled or disabled. Previously the tiles and their toggles held whatever they showed when they were drawn, and an open settings page only caught up once another device was selected and the first re-opened.
- **FanaBridge no longer floods the SimHub log while it is disabled.** A device with nothing driving it reported a state SimHub immediately overrode, so the two disagreed on every frame and each disagreement was logged — 127,145 lines in one user's session.
- **Disabling FanaBridge now darkens the wheel**, the same as switching the device off. Only the 7-segment display was blanked on the way out, so the LEDs stayed lit on the last frame drawn until the wheel was power-cycled.
- **A device's on/off switch is no longer changed by a click it cannot honour.** While nothing can drive a device its switch reads off whatever you chose, so clicking it wrote "on" into the stored setting — quietly switching on a device you had deliberately switched off, and making it impossible to switch one off at all. The click is now declined and the switch springs back.
- The LEDs tab no longer reports the wheel as connected after FanaBridge has stopped driving it.
- The Tuning tab now says FanaBridge is not running, instead of pointing at a plugin settings page that isn't there to enable something already enabled.
- **Devices now behave correctly while FanaBridge is unavailable.** Settings are preserved, disabled devices stop output and darken, status stays in sync without log spam, and devices recover when the plugin returns. Profile overrides also produce the correct LED editor after restart. ([#89](https://github.com/kelchm/FanaBridge/pull/89), [#90](https://github.com/kelchm/FanaBridge/pull/90); fixes [#91](https://github.com/kelchm/FanaBridge/issues/91), [#92](https://github.com/kelchm/FanaBridge/issues/92), and [#94](https://github.com/kelchm/FanaBridge/issues/94))
- RevStripe colors now work correctly on the CSL Elite P1 (Xbox and PlayStation) and CSL Elite WRC wheels. Legacy LED mode switching, color encoding, and channel clearing were corrected along with the affected profiles. ([#84](https://github.com/kelchm/FanaBridge/pull/84), closes [#76](https://github.com/kelchm/FanaBridge/issues/76), [#78](https://github.com/kelchm/FanaBridge/issues/78), and [#82](https://github.com/kelchm/FanaBridge/issues/82))
- GT DD Pro rev LEDs are now driven as fixed-color on/off LEDs instead of unsupported per-LED colors. ([#93](https://github.com/kelchm/FanaBridge/pull/93), closes [#77](https://github.com/kelchm/FanaBridge/issues/77))

## v0.6.0 - 2026-07-14

Expand Down
2 changes: 1 addition & 1 deletion Directory.Build.props
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
<LangVersion>latest</LangVersion>

<!-- Single source of truth for product versioning. -->
<VersionPrefix>0.6.0</VersionPrefix>
<VersionPrefix>0.7.0</VersionPrefix>
<Version Condition="'$(VersionSuffix)' == ''">$(VersionPrefix)</Version>
<Version Condition="'$(VersionSuffix)' != ''">$(VersionPrefix)-$(VersionSuffix)</Version>

Expand Down
Loading