Skip to content

Releases: logicallysynced/Chromatics

Chromatics 4.3.31

Choose a tag to compare

@logicallysynced logicallysynced released this 31 Jul 05:50
95e99f8

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience - the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • Added support for FFXIV patch 7.55.
  • Added a Black layer type, available as both a base layer and a dynamic layer.
  • Layers saved for a disabled or disconnected device can now be copied to another device.
  • New setting under Settings → General: lower the RGB refresh rate while FFXIV is not running.
  • Lighting no longer stops for the rest of the session when a single game-data read fails. Chromatics now retries, and reconnects to the game if the failures persist.
  • Fixed the update prompt showing the newest version's heading twice in its changelog.

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 4.3.24

Choose a tag to compare

@logicallysynced logicallysynced released this 07 Jul 08:28
03869a1

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience - the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • New: Nanoleaf smart-light support (Beta). Covers the panel family (Shapes, Canvas, Elements, Lines, Aurora) and other controllers that speak the Nanoleaf OpenAPI. Enable it from Settings → Device Providers and pair each controller with a one-time button press; effects render across the panels at their real physical positions. Layer assignments stay with their panels if you add or remove panels from the wall later. Essentials bulbs and strips are not supported.
  • Added new dynamic layers for Focus Target HP and Focus Target Castbar.
  • Added new effects for Status Inflicted and Casting Success.
  • Added new status effects category and items to Palette tab.
  • Chromatics now closes faster when several smart-light brands are enabled: LIFX, Hue, and Nanoleaf devices restore their original state in parallel instead of one brand at a time.
  • Fixed a startup crash on PCs where Windows App Control or Smart App Control blocks one of the bundled device libraries. Chromatics now starts with that provider disabled, logs which file was blocked, and explains how to allow it. This also covers the case where the core lighting library (RGB.NET) itself is blocked during settings load.
  • Fixed a crash when opening the Hue, LIFX, or Yeelight device picker with the same bulb saved twice in settings.
  • Fixed a bug which caused the Experience Tracker layer to not work with Reaper and Sage.
  • Fixed the Keybinds layer misreading hotbar actions with high action ids.
  • Updated Sharlayan to latest version
  • Various performance improvements and bug fixes

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 4.2.73

Choose a tag to compare

@logicallysynced logicallysynced released this 06 Jun 02:55
41b1e59

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience - the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • New: Windows Dynamic Lighting support (Beta).
  • New: Yeelight device support (Beta).
  • New: Alienware LightFX device support (Beta).
  • New: EVision keyboard support (Beta). Covers 13 keyboards that share the Sonix VS11K28A firmware - Glorious GMMK TKL, Redragon K550 / K552 / K552-2 / K556, Tecware Phantom Elite, Womier K66 / K87, Mars Gaming MKMini, Skillkorp K5, DEXP Blaze, Warrior Kane TC235, and Gamepower Ogre RGB.
  • New: Redragon mouse support (Beta). Covers 13 Redragon RGB mice that speak the OpenRGB HID protocol family - M711 Cobra, M715 Dagger, M716 Inquisitor, M602 Griffin, M801 Sniper, M808 Storm, M810 Taipan, M908 Impact, M987 Reaping, M719 Invader, M990 Legend, M709 Tiger, and M721-Pro Lonewolf 2.
  • New: QMK Raw HID keyboard support (Beta). Covers custom keyboards from NovelKeys, KBDFans, Drop, GMMK, Glorious, and any other brand running QMK firmware with Raw HID enabled. Enable it from Settings → Device Providers or pick it on the first-run device selector. Chromatics auto-detects compatible boards over USB and adopts them with no firmware flashing or extra software required. The provider drives per-key lighting through the OpenRGB-QMK plugin when the firmware has it installed; otherwise it controls the firmware's built-in RGB matrix base colour and effect mode via VIA. A pre-built key layout database covering 2650 QMK boards ships with Chromatics, so the Highlight and Keybind layers map to the correct physical keys without manual setup.
  • New: Layers can now be copied between devices. A new copy icon next to the device brightness button on the Mappings tab opens a dialog that duplicates every layer from one device onto another.
  • Hue, LIFX and Yeelight have been added to the first-run wizard, each with their own discovery flow.
  • PlayStation, Hue and LIFX devices are no longer classed as beta.
  • Added support for FFXIV 7.51
  • Added an option to remap layers when keyboard type is changed.
  • Multi-zone keyboards now show assignable keys for each zone instead of using the full keyboard grid intended for per-key LED layouts.
  • Updated RGB.NET device providers for Razer, Logitech, SteelSeries, Corsair and OpenRGB.
  • Updated internal Corsair, CoolerMaster, MSI & Wooting SDK libraries.
  • Fixed an issue which prevented Corsair and OpenRGB RGB.NET device providers from starting.
  • Fixed an error that could appear when Chromatics auto-checked for updates while minimized to the tray.
  • Fixed an issue where AZERTY keyboards weren't functioning properly.
  • Fixed an issue which caused Chromatics to crash when changing layer modes.
  • Fixed an issue which prevented non-bleed layers from re-applying if disabled and re-enabled, with the Enmity Tracker layer specifically going dark whenever the player wasn't on the target's hate table.
  • Fixed an issue where the Enmity Tracker layer stayed dark while a target was engaged.
  • Fixed an issue that prevented Vegas Mode from starting in The Gold Saucer.
  • Fixed an issue that could cause the title screen animation to play when loading between zones.
  • Fixed an issue where console lines copied to the clipboard could be lost when Chromatics closed.
  • Chromatics is now officially code-signed for additional installer security.
  • Updated dependency libraries to latest version
  • Increased the minimum Windows target to Windows 10 version 1809, build 17763.
  • Minor fixes and improvements.

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 4.1.38

Choose a tag to compare

@logicallysynced logicallysynced released this 14 May 10:10
fd09f36

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites - UPDATED

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience - the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • Added Auto-discovery for Hue bridges.
  • Updated Hue light adoption. After pairing, Chromatics shows a picker so you can choose exactly which Hue lights it should control. Existing setups upgraded from earlier builds keep all their bulbs (one-time auto-adopt of whatever the bridge currently exposes); from then on you can deselect bulbs you don't want from the same dialog.
  • Hue bulbs now restore their original colour and on/off state when Chromatics releases control.
  • Disabling a device on the Mappings tab now sticks across restarts.
  • Fixed an error that could appear in the log when disabling Hue (or any device provider) — "The device 'X' is not attached to this surface."

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 4.1.26

Choose a tag to compare

@logicallysynced logicallysynced released this 09 May 08:20
fd09f36

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites - UPDATED

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience - the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • New: PlayStation DS4 and DS5 controller lighting support (Beta). The DualShock 4 lightbar, the DualSense lightbar and the five player-indicator LEDs can all be mapped from the Mappings tab. Both USB and Bluetooth controllers are supported, and your controller's input still works normally in games while Chromatics drives the lights.
    Tip: if your controller is connected but Chromatics says it can't open it, another tool (like Steam Input, DS4Windows, or reWASD) is probably holding it in exclusive mode. Close it or disable its exclusive mode before launching Chromatics.
  • New: LIFX light support (Beta). Discovers LIFX bulbs, strips and tiles on your local network (uses Local LAN protocol - no LIFX cloud account required). When you enable LIFX in Settings, Chromatics shows a picker so you can choose which devices it should control. Multi-zone strips (Z, Beam, String, Neon) light up per-zone, and matrix devices (Tile, Candle Color) are mapped as a grid. When Chromatics releases control (you disable LIFX in Settings, or close the app), each device is restored to the colour and on/off state it was in before Chromatics took over.
  • The first-run welcome screen now lets you pick your Chromatics language right away - and the screen re-translates itself instantly so you can see the change before continuing.
  • Tank stance highlighting (Iron Will, Defiance, Royal Guard, Grit) and Summon Seraph now work correctly when the FFXIV client is set to Japanese, German or French.
  • The Effect Layer enable checkbox on the Mappings tab is now a per-device master toggle for everything on the Effects tab. Turning it off for a device silences raid effects, duty-finder bell, damage flash, cutscene animation, vegas mode, the startup and title-screen animations, and any reactive-weather animation overlays just for that device. Base layer painting (static, job-class colours, weather colour, screen capture) and dynamic layers (HP, target, key bindings) keep running normally.
  • Smoother Hue colour transitions. Fast-changing effects (Vegas mode, cutscenes, certain weather animations) used to look strobe-like on Hue bulbs that lack the Hue Play's hardware fade - Chromatics now asks the bridge to interpolate between colour frames so every supported bulb gets smoother motion on effects.
  • Updated underlying dependencies for stability and bug fixes.

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 4.0.153

Choose a tag to compare

@logicallysynced logicallysynced released this 01 May 06:25
95e76c5

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites - UPDATED

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience — the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • Fixed an issue where Chromatics could close itself with a crash dialog if a connected device (Hue, OpenRGB, etc.) had a brief network hiccup. These transient errors are now ignored.
  • Saving your layer setup is more reliable: if antivirus, OneDrive, or Dropbox briefly locks the file, Chromatics will retry rather than failing the save.
  • Quietened expected startup messages — if iCUE or OpenRGB isn't running, the app no longer treats it as a crash report.
  • Updated dependency libraries to latest version

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 4.0.153

Choose a tag to compare

@logicallysynced logicallysynced released this 28 Apr 13:39
95e76c5

*Important: Introducting Chromatics v4. It is a complete rebuild of Chromatics from the ground up in .NET 10. It will utilise the new version of Sharlayan for async FFXIV calls and RGB.NET to standardise RGB device SDK's (as opposed to manually managing them as Chromatics 2.x did).

Documentation

Please find the new Chromatics 4 documentation here.

Prerequisites - UPDATED

🆕 .NET 10 Desktop Runtime
🆕 Microsoft Visual C++ Redistributable 2026

Migrating from Chromatics 3.x

⚠️ Chromatics 4 stores your settings in a new location on your computer, and your previous settings will not be carried across automatically. You can bring your layers and colour palette across manually using the steps below.

To bring your layer mappings across:

  1. Find your old layers.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Mapping tab.
  3. Click Import and select your layers.chromatics3 file.

To bring your colour palette across:

  1. Find your old palette.chromatics3 file. It will be in the same folder you had Chromatics 3 installed in.
  2. Open Chromatics 4 and go to the Palette tab.
  3. Click Import and select your palette.chromatics3 file.

Your effects settings will need to be configured again from scratch. We apologise for the inconvenience — the rebuild was significant enough that a fully automatic migration was not possible.

Changes

  • Complete rebuild of Chromatics from the ground up.
  • New modern UI built with Avalonia, improving responsiveness, efficiency and maintainability.
  • Implemented Sharlayan 9.x, now powered by FFXIVClientStructs, the same underlying client structure library used by Dalamud.
  • Full Dawntrail support up to Patch 7.5, Trail to the Heavens.
  • Raid Effects have been separated from Reactive Weather. When active, they now replace the current base layer instead of being treated as weather effects.
  • Added new Raid Effects for Arcadion M5-M12 and Dawntrail trials.
  • Added support for custom LED positions on the Mapping tab, allowing non-keyboard devices to define their own layouts. Effects will use these positions as their reference points.
  • Added new base layers: Screen Ambient Capture and Audio Visualiser.
  • Added an option to automatically close Chromatics when FFXIV closes.
  • Added per-device brightness control.
  • Added a new Job Gauge C dynamic layer.
  • Cutscene animations no longer play when transitioning between loading zones or instanced content.
  • Updated RGB.NET support to version 3.2.
  • Added full support for Philips Hue devices.
  • Added support for QWERTZ and AZERTY keyboard layouts.
  • Added built-in crash reporting and performance monitoring tools. These can be turned off in Settings. Crash reports are optional and must be submitted manually each time.
  • Added a Settings option to opt in or out of beta releases.
  • Improved performance and resolved multiple memory leaks.
  • Fixed many minor bugs and stability issues.

Known Bugs

This is a major new release of Chromatics, so some initial bugs may still be present. If you encounter an issue, please open a bug report so it can be investigated and addressed.

Chromatics 3.2.1.0

Choose a tag to compare

@logicallysynced logicallysynced released this 12 Jan 00:04
3af92a7

Please uninstall Chromatics 2 before installing Chromatics 3, or extract Chromatics 3 to a new location.

Documentation
Please find the new Chromatics 3 documentation here.

Prerequisites
.NET 8 Desktop Runtime
Microsoft Visual C++ Redistributable 2022

Changes

  • Fixed issue which caused a 404 error when pulling down data from garland tools.
  • Minor improvements to update engine.
  • Updated RGB.NET to latest major version (3.1).
  • Updated other dependencies to latest version.

Known Bugs
Theses are bugs that I have already identified and don't need to be reported on.

  • If you get a teapot error while trying to update - please download & re-install from github releases.
  • Not updated for latest patch (7.4). This is minor internal fixes only.
  • Layer help text doesn't always scale to the rich text box correctly.
  • Interface can lag when dragging and resizing the window on high resolution monitors with non-standard DPI's.
  • When changing key mappings on a layer, sometimes you need to disable and re-enable the layer or preview the layer before the lighting will apply.
  • When de-selecting keys from a layer, they appear gray instead of taking the colour of the base layer. Previewing the layers should fix this.
  • Only one keyboard layout en-us is available on the mapping tab. This is a QWERTY keyboard so if you use a different layout, such as AZERTY you will need to map keys accordingly.
  • Azerty & Qwertz layouts not working correctly.

Chromatics 3.2.0.0

Choose a tag to compare

@logicallysynced logicallysynced released this 09 Feb 01:14
779b3f1

Please uninstall Chromatics 2 before installing Chromatics 3, or extract Chromatics 3 to a new location.

While Chromatics 3 is in beta, only the portable version will be available for download

Documentation
Please find the new Chromatics 3 documentation here.

Prerequisites
.NET 8 Desktop Runtime
Microsoft Visual C++ Redistributable 2022

Changes

  • Updated RGB.NET to latest major version (3.0).
  • Updated Philips HUE dependencies to latest version.

Known Bugs
Theses are bugs that I have already identified and don't need to be reported on.

  • If you get an error message regarding terriTypes.json - please re-install from github.
  • Job gauges have not been updated for 7.1
  • Layer help text doesn't always scale to the rich text box correctly.
  • Interface can lag when dragging and resizing the window on high resolution monitors with non-standard DPI's.
  • When changing key mappings on a layer, sometimes you need to disable and re-enable the layer or preview the layer before the lighting will apply.
  • When de-selecting keys from a layer, they appear gray instead of taking the colour of the base layer. Previewing the layers should fix this.
  • Only one keyboard layout en-us is available on the mapping tab. This is a QWERTY keyboard so if you use a different layout, such as AZERTY you will need to map keys accordingly.
  • Azerty & Qwertz layouts not working correctly.

Chromatics 3.1.6.0

Choose a tag to compare

@logicallysynced logicallysynced released this 02 Jan 18:03
a75df95

Please uninstall Chromatics 2 before installing Chromatics 3, or extract Chromatics 3 to a new location.

While Chromatics 3 is in beta, only the portable version will be available for download

Documentation
Please find the new Chromatics 3 documentation here.

Prerequisites
NEW!! .NET 8 Desktop Runtime
Microsoft Visual C++ Redistributable 2022

Changes

  • Added support for Dawntrail 7.1
  • Added raid effects for Cloud of Darkness Chaotic Raid.
  • Updated RGB.NET to latest version.

Known Bugs
Theses are bugs that I have already identified and don't need to be reported on.

  • If you get an error message regarding terriTypes.json - please re-install from github.
  • Job gauges have not been updated for 7.1
  • Chromatics may take up to 30 seconds to fully shut down and restore lighting to defaults upon closing or updating.
  • Layer help text doesn't always scale to the rich text box correctly.
  • Interface can lag when dragging and resizing the window on high resolution monitors with non-standard DPI's.
  • When changing key mappings on a layer, sometimes you need to disable and re-enable the layer or preview the layer before the lighting will apply.
  • When de-selecting keys from a layer, they appear gray instead of taking the colour of the base layer. Previewing the layers should fix this.
  • Only one keyboard layout en-us is available on the mapping tab. This is a QWERTY keyboard so if you use a different layout, such as AZERTY you will need to map keys accordingly.
  • Azerty & Qwertz layouts not working correctly.