Jump to content

Astral85

Members
  • Posts

    410
  • Joined

Reputation

12 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Files located in AppData\Local\Temp such as: CUE4fHXlUW{d4dbfc25-3c98-4dd8-aca2-103e8274d3e8} I assume are related to CUE4? Windows Defender detected two of these files on my system today as Trojan:Script/Wacatac.B!ml. Just wondering if they are likely a false positive.
  2. Lookup PirateDog on Ebay. He makes a custom ARGB cable that will connect to Corsair LED ports.
  3. It would be great to have a single toggle which could adjust the brightness for all devices. Currently I have to go through about six devices at a time to adjust the brightness level. Sometimes I just want everything at the lowest brightness.
  4. Can someone please tell me how to assign custom icons? I only have the option to select Corsair preset icons. 🤔
  5. The integration is not working for me, when I toggle CUE integration on in the game all of my lighting goes dark. Has anyone who did not have it working figure out how to get it working?
  6. Is there any chance the CUE software team has or can investigate this HW mode lag issue with CUE 4.xx and the AURA plugin?
  7. I have two waterblocks with LED's (CPU + GPU) and I've modded both with ARGB to CUE adapter cables. So CPU block is on C-Pro lighting ch 1 and GPU block is on C-Pro lighting ch 2. Currently I have 4 x LED strips on LNP ch 1 and 6 x LL fans on LNP ch 2. With the QL on LNC that leaves just the 4 x LED strips on the LNP. So if I connect the LNP to the C-Pro USB header the C-Pro would be running a total of 6 x LED strips..... The LED strip on the GPU block is only really half a strip (6-7 LED's). My motherboard only has 2 x USB 2.0 headers. So it would be C-Pro on USB header 1 and LNC on USB header 2. LNP connected to C-Pro USB header 1.
  8. I'm thinking that I will plug the LNC with 6x QL directly to a motherboard USB 2.0 header and try piggybacking the LNP with 4 x LED strips off a C-Pro USB header. Is power the issue or something else? I don't have any major issues with the C-Pro and my current motherboard/USB controller.
  9. Can the Lighting Node Core with 6 x QL fans be safely run off a Commander Pro USB 2.0 header or is there a power limitation to what can run off a single motherboard USB 2.0 header? I could run the LNP with 4 x LED strips off the C-Pro USB 2.0 header instead if power is an issue....
  10. I'm planning to replace my LL with 6x QL fans. I currently have LED strips on LNP ch 1 and the LL on LNP ch 2 via RGB hub. Can the QL connect to the RGB hub and LNP ch 2 or do I need to use the LNC? Will my profiles apply the previous effects that were on the LL (LNP ch 2) to the QL on the LNC? If not will I least still have the effects imported into the lighting layer section available to re-apply?
  11. Is it possible to get my Dominator RGB DIMM temps into the Nexus? I can't find this as an option in the libraries.
  12. I only want the motherboard lighting control in CUE but I don't want to run another hardware ecosystem's software (Armory Crate) just to be able to do that. If Asus agreed perhaps CUE could have standalone control of Asus motherboard lighting.
  13. There appears to be a bug with the CUE Asus Plugin in 4.15/4.16 and Aura (Lighting Control 1.07.84) in that it causes CUE to severely lag going into HW mode when the CUE service is terminated, i.e. System reboot. It can hang on the last software profile for 20-30 seconds.
  14. The AuraServicesetup appears to install everything it normally would except the Aura app itself. An even more streamlined install would be better. I can confirm the Asus CUE plugin works with AuraServicesetup and AacMBsetup manually. The reason I've uninstalled again is because there currently seems to be a bug with CUE 4.15 onwards and the plugin in that there is a very large lag in devices going from software mode to HW mode when CUE is exited, i.e. system reboot. I don't know if the Aura installed with Armory Crate is having this issue or not. I'm about to report the bug in another thread now.
×
×
  • Create New...