AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Icue asus plugin11/23/2023 ![]() ![]() Also, this is still a BETA so more features will be added. When asked if you want to save changes, click Yes. That process takes about 15 seconds to be able to see the correct RGB configuration applied to all devices. When you install the plugin any supported motherboard will show up in iCue and some functionality is retained in Aura. Click the Link/Unlink button beneath the DRAM icon the icon will change to white when linked. If your motherboard has an analog 12-volt RGB header, you can also use iCUE to control the lighting of devices attached to the header. If your motherboard has an analog 12-volt RGB header, you can also use iCUE to control the lighting of devices attached to the header. ASUS Motherboard integration in iCUE If you have an ASUS Motherboard with RGB lighting, you can use iCUE to control its lighting and the RGB lighting of ASUS GPUs. My Workaround to all of this is a little batch file that just kill the ICUE Process, wait 5 seconds and run the program again. If you have an ASUS Motherboard with RGB lighting, you can use iCUE to control its lighting and the RGB lighting of ASUS GPUs. CORSAIR iCUE enables advanced control over lighting and performance for our vast ecosystem of iCUE-enabled CORSAIR products. That's an interesting theory and for me is much more frequent (maybe 3 or 4 hours in between fails). I have a workaround that works for me, for now that's enough. Just my two cents though, I'm not on Asus or Corsair's dev team, and I'm not good enough at reverse engineering things to go and try diagnose this. It always seems to be around the 12-14 hour mark though. Or if I reboot during the day, then the integration breaks sometime at night or early morning when I'm asleep. I've noticed that the integration will run fine in the morning, but often break later at night. Corsair is using a "game integration" to control Aura, and I think that Asus never thought people would be playing a single Aura-integrated game for >12 hours. My theory regarding why this issue exists is due to the way that this is implemented. I also have a Strix 3070 and its infuriating to have the one zone issue, but it seems to be an Aura issue rather than anything iCUE-related. You can check this in the settings->updates section in the bottom left of AC. I've found that reinstalling (using the uninstall tool, rebooting, installing, rebooting again) Armoury Crate can help, but the most important thing seems to be ensuring that your device HAL is up to date. RainbowĪfter a few seconds your iCUE should take control of Aura againĪs for the "one zone" issue, this one is a bit harder to pin down. This should reset your lighting to whatever your Aura default is, e.g. Ive got all my RGB controlled via ICUE (barring the AmiMe Matrix panel) and my GPU isnt ASUS so Im not missing out. I have the plugin disabled (actually I think I deleted it) as I was finding RAM RGB would lock up (all the time) as well as the ARGB headers (some of the time). The only other solution is not attempting to use ICUE to control your motherboard RGB then because the latest Armoury Crate simply breaks compatibility with the Asus provided plugin that iCUE uses to communicate with the Asus motherboard and GPU. In Armoury Crate, enable then disable "Performance Mode" (under the Aura Sync menu) I think youll find that the ASUS plugin is causing issues. ![]() In iCUE settings, disable the plugins slider/toggle switch Unless Remote Debugging to a customer's machine is a common thing for you there is no need to bloat the executable with a wrapper function to every single function.I've been dealing with this issue for a couple months now, and I seem to have found at least a workaround for now: Here's the Reddit thread where I went into a little more detail.Īlso unrelated note: Please stop shipping iCUE.dll with Edit and Continue enabled. Perhaps even releasing the header files for the plugin com layer, though I've managed to decode a decent amount of it already the new API functions added in version 0圆7 with the Nvidia plugin are not as enlightening. Are there any plans to maybe include more accessible options to loading unofficial plugins beyond patching the dll? I noticed that there is a mechanism in cuecfg when the dll has a "debug mode" global set that bypasses the dll validation. Though I've already done it, what is the stance on this? It seems like there is some validation to prevent non-signed dlls from being loaded into iCUE but I've included a circumvention for that. Some might know I've created an unofficial iCUE plugin by reversing the communication layer to the current series of plugins to very roughly support unsupported devices as well as RGB strips via the work of another who makes OpenRGB. ![]()
0 Comments
Read More
Leave a Reply. |