Skip to content

Releases: Aurora-RGB/Aurora

v254

24 May 15:12
Compare
Choose a tag to compare

Changes

  • Added new menu for Chroma Wrapper. Includes "Disable Bloat", "Restore Device Control" and "Uninstall" buttons

Fixes

  • Fixed Chroma SDK installation not disabling Razer bloat
  • Fixed Audio Visualizer layer resetting device and briefly not rendering every 20 seconds

Full Changelog: v253...v254

["Aurora"]

v253

23 May 16:57
Compare
Choose a tag to compare

Changes

  • Fixed chroma profile not detecting process names

Full Changelog: v252...v253

["Aurora"]

v252

22 May 06:47
Compare
Choose a tag to compare

Changes

  • Fixed Aurora window not opening if Chroma SDK was not installed

Full Changelog: v251...v252

["Aurora"]

v251

22 May 02:52
Compare
Choose a tag to compare

Changes

  • Fixed a crash that could happen while quitting Aurora that affected restarts, updates etc.
  • Fixed settings not loading when template functions are used
  • Chroma module will now wait 2 seconds if RzChormaSdk service is detected
  • Reminder to clean your keyboards

Full Changelog: v248...v251

["Aurora"]

v248

20 May 23:38
Compare
Choose a tag to compare

Changes

  • Fixed MicrophoneLevel, SpeakerLevel and MicLevelIfNotMuted properties broken from previous update
  • Improvements to Chroma profile exclusions, though whis will reset everyone's selections

Full Changelog: v247...v248

["Aurora"]

v247

19 May 16:50
Compare
Choose a tag to compare

Changes

  • Updater will now properly try to close AuroraDeviceManager.exe while updating
  • Fixed audio device Volume and IsMuted properties sometimes not working

Full Changelog: v246...v247

["Aurora"]

v246

18 May 23:58
Compare
Choose a tag to compare

This update turns background updates "on" by default.

Fixes

  • Fixed UI freezes while changing progile settings like names, hidden etc.
  • Increased threads used while starting Aurora back to what it's supposed to be
  • Aurora will no longer take it's time to quit if config window is open
  • Closing config window will disable the profile preview
  • Hidden profiles' "disabled" icons won't appear anymore

Full Changelog: v245...v246

["Aurora"]

v245

17 May 16:40
Compare
Choose a tag to compare

This update brings automatic background updates. For now, it needs to be enabled in Updates settings. It will be on by default later.

Changes

  • Failing layers now will only show a notification message instead of a dialog message, without interrupting other layers
  • "Automatic" Additional Leds layout will now consider Lightsync status
  • "Automatic" Additional Leds will now update when Chroma and Lightsync state changes
  • Chroma integration will now listen for Chroma Service process and enable/disable itself
  • Equalizer layer will now release audio device after a while it is not used

Devices

  • RGB.NET devices with no hot-plug support will now fail to initialize if no devices are detected. Exceptions are:
    OpenRGB, Yeelight
  • Improve DeviceManager launch time

Fixes

  • Reused instances of certain memory object to prevent a memory leak for some people
  • Fixed currently selected profile and it's layers not saving when Aurora closes
  • Fixed Aurora window staying in memory after closing it if settings has been clicked before
  • Fixed DeviceManager's variables incorrectly saving colors
  • Fixed Aurora plugins not compiling with Runtime error
  • Fixed "overflow error" can happen when freeform selection is moved

Full Changelog: v239...v245

v244

16 May 20:50
Compare
Choose a tag to compare
v244 Pre-release
Pre-release

Changes

  • New updates after this can restart Aurora or the DeviceManager alone if only affected component changes
  • Improve DeviceManager launch time
  • Equalizer layer will now release audio device after a while it is not used

Full Changelog: v243...v244

v243

15 May 00:04
Compare
Choose a tag to compare
v243 Pre-release
Pre-release

Fixes

  • Fixed "Element not found" exception when no new update is found
  • Removed recreation of certain memory object to prevent memory leak for some people

Devices

  • RGB.NET devices with no hot-plug support will now fail to initialize if no devices are detected. Exceptions are:
    OpenRGB, Yeelight

Full Changelog: v242...v243