It requires RGBFusion 2 installed to work.
It automatically install the Bridge in the RGBFusion Folder.
RGBFusion should be closed in order to work.

Note: RGBFusion will slowdown when changing peripherals (area index above 7). it is recommended to maintain these areas static.

Using new bridge version that reduce calls to RGBFusion when an area has not been changed.

v0.8.0-rc2

Patched LedLib2.dll B20.0430.1
Update MD5 table.

This command should be used to avoid RGBFusion Bridge control some areas. It is useful if you want to control your RAM RGB with another application because RGBFusion is slow handling RAM.

RAM is usually Area index 9. In some cases it could be 8.

Values should be comma separated.

Default ignore list is "0,8,9" (without quotes)

Don't require specific RGBFusion. Feel free to test your favorite version.
Testing bulk commands to reduce latency. It should show always 0 in Aurora device list.
Update MD5 tables to the latest Bridge and remove patched LedLib2.dll installation.

v0.8.0-rc3

More logging for debug
Better start stop control
Wait until RGBFusion HAL is loaded and pipe is listening to send first command at Aurora's start.
Restore last color if device restart.
Code cleanup.
Updated RGBFusion Bridge
More flexible RGBFusion Bridge installation procedure

Avoid scan key array for commit key

Used to load custom drivers

And code clean up

Use updated RGBFusion Bridge

This reverts commit dea4ec88e61a99d7a64ab3e5dc148c73a72ee481.

Thanks to https://github.com/diogotr7/Aurora/blob/RGBFusion/Project-Aurora/Project-Aurora/Devices/RGBFusion/RGBFusionDevice.cs

Fix lights not changing of commit key was not used.
Kill RGBFusion process on device start
Relax autoreset time