Keyboard: Vulcan 120-series AIMO.
Using openRGB sdk server with artemis integration.
OS: Win10
When using openRGB, it is possible to set the keyboard's brightness to its maximum (same maximum as within roccat swarm). When opening artemis, the brightness of the LEDS is reduced to around half. One method of fixing this is opening openRGB and reloading the profile with the maximum LED brightness. It's not a huge issue, but some means of automating this would be fine.
I'm not sure if this is unique to my keyboard as it is particularly bright, but the steps to reproduce this are:
openRGB and load a profile with the settings at the brightest
open artemis with a profile loaded - the colour and brightness of the LEDS will change
reload openRGB profile - colour and brightness will reset
Change key colour in artemis - keys will be at this colour at the fully bright setting.
Seems like openRGB has additional conotrol over LED brightness that artemis doesn't carry over.
Keyboard: Vulcan 120-series AIMO. Using openRGB sdk server with artemis integration. OS: Win10
When using openRGB, it is possible to set the keyboard's brightness to its maximum (same maximum as within roccat swarm). When opening artemis, the brightness of the LEDS is reduced to around half. One method of fixing this is opening openRGB and reloading the profile with the maximum LED brightness. It's not a huge issue, but some means of automating this would be fine.
I'm not sure if this is unique to my keyboard as it is particularly bright, but the steps to reproduce this are: openRGB and load a profile with the settings at the brightest open artemis with a profile loaded - the colour and brightness of the LEDS will change reload openRGB profile - colour and brightness will reset Change key colour in artemis - keys will be at this colour at the fully bright setting.
Seems like openRGB has additional conotrol over LED brightness that artemis doesn't carry over.