Jump to content

elfas

Members
  • Posts

    4
  • Joined

Reputation

11 Good
  1. @c-attack - disregard my last post. I again reapplied my desired colors on the individual components and cycled the power on the machine. The colors this time remained saturated and bright as intended. I did run a repair on icue from windows apps and features. Perhaps that helped. But yeah, the color previews on the "scenes" remain buggy. Thank you for the workaround once again!
  2. Dear @c-attack, Thank you for looking into my reported issue. I tried your workaround, and yes - that works. Please note that this bug also applies on color settings when choosing colors for individual components (not just in the "scenes" area ). But yet again - your suggested workaround works here also (so basically the color needs to be chosen first, and then it needs to be reapplied using the correct color code a second time). BUT - I restarted my PC, then I cycled to my newly created theme from another theme via a keyboard shortcut - and the colors reverted back to these faded out colors like in the beginning. Please see two new attached pictures of when I tried your workaround, then rebooted machine, then switched themes via keyboard shortcut. Thank you for clarifying that this isn't a hardware issue 🙂 Will be waiting for the bugfix in a future icue release.
  3. Not sure if this is the fault of the new version of icue, but I'm experiencing a weird fading color issue for completely all components when I try to set up custom colors. Easiest way to demonstrate this in my case is by going to "scenes" and attempting to set a custom scene with a single static color: first select the predefined red (first picture); I then select the predefined blue (second image); then I cycle back to the same predefined red (third image). As you can see - the red ends up looking pink. When I go and set colors for individual components of the machine - I straight away get these washed out / faded colors (not only red). A short story of how I came to this situation: I upgraded my PC case from 280X to 7000X (needed more cooling room for the GPU). I swapped my H100i AIO to H150i elite capellix. I added more QL140 and QL120 fans (11fans in total (included the default ones of the AIO)). Since my MB (ASUS maximus gene XI) has only two internal USB2.0 headers - I had to daisy chain my 3 Commanders: Commander XT (came with 7000X case) & Commander Core (came with AIO) both connected to USB2.0 ports on my older Commander Pro. The Commander Pro is connected to one USB header on the MB, and the other USB header is used for the PSU connection (HX1200i). I tried daisy chaining the commanders in different combinations (the XT has an additional USB lead also). i.e. I had two commanders on both MB USB ports and just one commander daisy chained. All components show up fine in icue and they can all be individually addressed, but I cannot get proper colors - they are all faded like in the third pic. BTW all devices are on the brightest level and the opacity is not reduced. Please let me know if I should post this elsewhere and or provide the icue logs. Thank you.
  4. This plugin worked for me for a while, but after the latest iCue update (3.25.60) and possibly some update that came from ASUS armoury crate on the same or next day (did not notice what was updated from ASUS) - the motherboard now does not show up in iCue anymore or in Asus Aura. The MB now continues cycling through the default rainbow. MB: Asus Maximus Gene XI Would anyone from Corsair help to understand if the problem was caused by iCue or if this is something I should take up with ASUS support? Is there any log saved on my system by iCue to understand if the plugin is even loaded up during iCue startup? Can provide more details if needed. Thank you.
×
×
  • Create New...