Jump to content

--MAILMAN-

Members
  • Posts

    42
  • Joined

  • Days Won

    1

--MAILMAN- last won the day on November 18 2023

--MAILMAN- had the most liked content!

Reputation

14 Good

Converted

  • Interests
    Flight Simulators:IL-2 Sturmovik 1946 HSFX; IL-2 Great Battles;Aces High 2; Hell Let Loose

Converted

  • Occupation
    Retired
  1. I have the same issue. Below are the screens that appear when I click on Device Settings. No ability to save anything to the onboard memory of the device. I used to be able to save a multilayer lighting profile directly to the Strafe RGB keyboard's onboard memory right from the list of profiles in iCue 3. Nice & simple with no need to go to the device settings etc.. That option disappeared when iCue moved to version 4 & 5. No option to save a complete profile to the library, only individual lighting layers. This used to be a simple function until iCue got "improved". 😒
  2. I have an ASUS ROG STRIX Z370-E Gaming motherboard capable of DDR4 Ram only. I have 32(4 x 8)GB of Corsair CMK32GX4M4A2666C16 DDR4 Ram installed. iCUE 5.9.105 keeps flagging a module software update for DDR5. Why am I seeing that there is a software update for DDR5 when... My motherboard does not support DDR5, only DDR4 I have DDR 4 RAM Modules installed not DDR5. Thanks for an explanation and any solutions to block this software update for DDR5 and its notifications.
  3. Yes, just like I did with all of the programs and apps for which I created profiles, but only google based programs cause the problem and only if I mute the microphone.
  4. This is very strange. I accidentally hit the mute button of my Void RGB Wireless Head Set. When I left click on any Google App (Chrome, GMAIL) to launch it from my desktop the microphone turns on (get the voice prompt from iCue; mic on) and when I close the app the microphone turns off and get the voice prompt from iCue; mic off). This does not happen with any other application or browser except Google. Any idea what is happening and causing this. Thank you
  5. This was the complete waste of my time to which I was referring. It had absolutely nothing to do with the original post/question especially since Corsair_Notepad had already answered the question and explained why. I don't know who you think I am, but keep obsessing on it if that floats your boat. I have and had only one user name, this one & posted a few dozen times in seven years so go on a fishing expedition if you think I am someone else for all I care. I don't waste my time coming to forums to get help to just get trolled (see your quote above). 99% percent of the people here provide helpful or well intentioned answers. Some just like to read their own words. I only came here now because I forgot to turn off" follow topic" and got a notification. I didn't come here to get into a pissing contest with any member on this forum. I am done with this thread. and Follow topic is off so post away to your hearts content for your audience.
  6. Not passing judgement of the vices or virtues of either iCue 4 or Armoury Crate. Simply showing what happened with my 3 year old ASUS Z370-E gaming motherboard/PC RGB lighting when I upgraded from iCue 3 & AURA Lighting_Control_1.07.79_V2.2 to iCue 4 & Armoury Crate. For whatever reason Corsair iCue 4 or ASUS Armoury Crate or both did not want to play nice with my ASUS motherboard. ---------------------------------------------------- I had iCue 3.88.88 installed because initially iCue 4 did not support my Void RGB Wireless Surround. 3.88.8 supported my keyboard, mouse, headset and the 6 RGB headers of my ASUS motherboard I opted to update to 4.22.203 because it now supported my Void RGB Wireless Surround headset. Uninstalled Aura Lighting Control 1.07.84 then iCue 3.88.8. Installed iCue 4.22.203; Installed the Corsair Plugin For Aura Sync in the correct folder; Installed Armoury Crate 3.2.3.0 Results: 4.22.203 recognized all 6 RGB headers on my motherboard, but only 4 were functional. Auto profile switching when opening an app worked for all of the Corsair devices and the ASUS motherboard except for the two aforementioned RGB headers. When the app was closed the Corsair devices returned to the default profile while the ASUS motherboard RGB Headers were stuck in the app profile. To fix this I had to close down iCue and Restart it. Only then did the default profile work on all devices, but this was only a temporary fix. No amount of restarting iCue, Armoury Crate or my PC fixed this problem. To try to fix this I installed iCue 4.30.162 through the update in iCue. Results: Only four of the ASUS motherboard RGB headers were recognized. The two RGB headers that were made non-functional in 4.22.203 were no longer even recognized in 4.30.162. Profile switching still did not function correctly. No amount of restarting iCue, Armoury Crate or my PC fixed the issue. So Completely uninstalled iCue 4 and Armoury Crate 3.2.3.0 using the Armoury Crate uninstall tool v2.1.5.0. The hunted down all Armoury Crate folders and registry entries. Installled ASUS Aura LightingControl 1.07.84; installed iCue 3.88.88 and placed the Corsair Plugin For Aura Sync in the correct folder. Everything is working as it should. Hope this is helpful.
  7. "You may be able to get away with this on the older motherboards. The newer models will not work with the older standalone Aura programs." EXACTLY This statement absolutely makes zero sense. We aren't even talking about newer models. We are talking about the here and now, two specific motherboards the Z370-E and Z390-E and no other motherboards: older or newer. "You also might have some in BIOS basic color options on those boards, something that was strangely pushed out the following cycle. The massive volume of services in Armory Crate is something to consider, especially when Asus' own cleaning tool is designed not to remove them all. One solution to all of this is to turn off the MB lighting in the BIOS. The dark beauty of the board may be more compelling with a healthy dose of RGB from elsewhere. It gets to be very difficult to match color tones with different LED types and materials regardless. The GPU going dark is a tougher pill to swallow, but as mentioned above there is no way for CUE to commandeer the motherboard. It communicates with it through the Amory Crate/Aura software." I would like to thank you for your input and advice, but I just can't in good conscience do that because it has absolutely nothing to do with this thread. I am just sorry I spent a couple of minutes reading this crap from someone who obviously likes to read his/her own writing and thinks it impresses people. I would highly recommend coming down off of your pulpit. I think the air has gotten a little too thin for you. Corsair Notepad clearly articulated what had to be done. End of story. Nothing else needed to be added unless it was contradictory to what Corsair Notepad said. I think it high time that the admin just lock this thread. The information has been asked and answered.
  8. FYI This older version of AURA_Win10-64bit_V1.05.32.02_20180307 is working with iCUESetup_4.22.203_release on both my Z370-E and her Z390-E. We have lighting profiles for various applications and games and they all switch automatically when they are launched. All of the RGB headers on these two motherboards as well as the Corsair RGB peripherals are being controlled through the iCue 4 software. The only services from Aura Sync that are running are the lighting services and yes these do run at windows start up. We never open the Aura Sync. application for anything. Her concern as is mine is the services and tasks not related to RGB lighting. We don't want Armoury Crate with all its problems controlling our liquid cooling, fans, processors etc. or bogging down our PC's. We have those components set in the BIOS the way we want them. I guess she will need to decide if it is worth installing Armoury Crate to control her video card LED. I don't have to make that choice, my RTX 2080 Ti Founder Edition LED won't show up in iCUE regardless of whether Armoury Crate is installed or not. Thank you for the explanation
  9. If this has already been answered I did not find it in my search. The Corsair instructions for integrating these two applications to control the motherboard RGB is straight forward. The instructions state that Armoury Crate will need to be installed. The instructions further explain that iCUE only needs the plug in from Armoury Crate and that Armoury Crate does not have to run. These instructions don't say how to stop Armoury Crate from running. So how does one stop Armoury Crate and all of its tentacles from running at start up or in the background? I just finished a chat session with ASUS to inquire if and how you can stop Armoury Crate from running at windows startup and also stop it from automatically updating. They also said the newest version of Armoury Crate has no conflicts with iCUE and can run at the same time. ASUS said: The only way to stop Armoury Crate from running is after windows has finished loading you have to open the task bar and end it. They make no mention of how to stop the tasks and services that Armoury Crate also runs when it starts. This means I would have to perform this action each and every time the PC gets rebooted. There is no option in the installation steps or in the UI to prevent/turn off Armoury Crate from running at windows start up. ASUS also said: There is no option to stop automatic updates of Armoury Crate either in the installation options or in the Application UI. According to ASUS the user has to go to the Microsoft Store and stop Automatic Updates of all the applications installed on a persons PC. My wife and I are running Aura Synch; AURA_Win10-64bit_V1.05.32.02_20180307version. We can control the RGB lighting on my ASUS ROG STRIXZ370-E gaming and her ASUS ROG STRIX Z390-E Gaming with this version. The later version of Aura Synch; Lighting_Control_1.07.84_v2 did not want to work with the iCUE installations on either of our PC's. I am fine with my RGB lighting setup, but my wife has an ASUS Tuf Gaming 3060ti V2 OC which has an RGB LED that can be controlled with Aura Sync (not her current versions which could in turn be controlled by iCUE if she uninstalls Aura Synch and then installs Armoury Crate which has an Aura Synch as part of the package. She just does not want the added baggage of Armoury Crate's app nor its tasks and services running in the background. So if someone could tell me How to turn off Armoury Crate running at Windows Startup and Stop Armoury Crate from auto updating it would be greatly appreciated. If either of these are even possible. If it can't be done then she will live without the video card RGB synching with the rest of the RGB lighting. Thanks Thanks.
  10. I just wanted to be sure about this before updating. I did not know if Void Wireless or Void Surround were specific headset models or were just a generic group name that included several Void models with the wireless and/or surround feature. I did not assume that Void Wireless or Void Surround included Void RGB Wireless Dolby 7.1 Gaming Headset . Thank you for the answer.
  11. My Void RGB Wireless Surround Headset was dropped from support when iCue 3 went to iCue 4. I was running iCue version 3.38.61 from May 2021 when prompted in iCue to update. It updated to the first version of iCue 4 and my headset didn't show up. Upon checking the release notes my headset was on the list of legacy devices not supported in iCue 4 so I went through the painful process of deleting everything related to iCue and reinstalling 3.38.61 and all of my profiles. Even though I had an incompatible device I kept getting notices in iCue to update. Not wanting to get burned again I would check for release notes which turned out to be all iCue 4 and no support for my head set. In January 2022 there was an iCue update, 3.38.88 which fixed issues. I successfully installed this version and have been running it ever since. Everything was just fine I had no need to update further because my headset is still working with iCue. I gratefully stopped getting notifications in iCue to update the software. This was perfect. A few weeks ago I got a notification to update iCue. I just ignored it figuring I was done with updating iCue until my headset failed and replaced it with an other than Corsair Brand. I made a post in these forums after receiving the update notice earlier wondering why I suddenly was getting update notifications since I had an unsupported legacy device. It never got answered. I happened to check for to see if it got answered and saw the post had been closed. Before logging off I decided to read all of the release notes for iCue 4 and came across the below entry for 4.22.03. Does VOID SURROUND or VOID WIRELESS = VOID RGB WIRELESS Dolby 7.1 GAMING HEADSET? If so does the support continue through the current release? I would like to know this information before I attempt to update my iCue. Thanks for any information on this. 4.22.03 03/29/2022 Software Enhancements Privacy Tab has been added to Settings Fixed an issue that caused Philips Hue to crash iCUE when enabled Fixed the LT100 tower names in Quick Lighting Zone K100’s Control Wheel will no longer have its lighting impacted by polling rate changes Resolved text overflow issues with certain translations Resolved some issues with customizing custom Scenes NVIDIA 3080 Ti Founders Edition is now supported in iCUE The following legacy devices are now supported in iCUE 4: SABRE RGB SABRE RGB Optical SABRE RGB Laser VOID USB VOID Surround VOID Wireless
  12. I have a Void RGB headset that is working just fine thank you very much. I have several profiles created. This headset is incompatible (support dropped by Corsair) with iCue 4. So I am running 3.38.88 which is the last version that I am aware of that is compatible with this headset. My understanding was that no more updates would show up if you had incompatible devices in the iCue software. Today I get a notice that 4.29.203 is available and am loathe to install it for fear of having to go through the not so easy process of wiping out everything iCue and reinstalling the last working version and then having to install all of my profiles again. Why am I getting this notification? Has there been a change to the device exclusion /inclusion for iCue 4? There is no description as to what is included/excluded in these update notices (only an install button) and no easy way to roll back to a working version when you find out it doesn't support all of your Corsair devices. One would think this would have been implemented after all of these years of iCue and its predecessor software. All my Corsair Devices are working so unless this new version includes the Void RGB headset I will stick with 3.38
  13. Thanks for pointing this out. Any mention from Corsair about addressing this anytime soon?
  14. Because my wife and I each have a Void RGB headset and this headset was dropped for support beyond iCue 3.38.61 this is the version of iCue that we have installed on our respective computers; mine is an ASUS ROG STRIX Z-370E Gaming and hers is the ASUS ROG STRIX Z-390-E Gaming. This version is required for us to have Windows recognize 8 channel sound. Without iCue Windows only recognizes 2 channel stereo. Thanks a bunch Corsair. We have not attempted to install any newer versions of iCue. Our motherboards are detected and show up in ICue and we can program the RGB headers on the motherboard. We had both selected the Temperature Lighting affect for the Back IO. These were working just fine for all of the various profiles we created. I noticed a few days ago that this RGB Header no longer worked using the Temperature Lighting affect on any of my profiles. I checked my wife's computer and the Temperature Lighting affect no longer was working for any of her profiles. When I checked the iCue dashboard on both computers System no longer appears in the drop down menu. When I check the settings we have enable hard drive widget checked and the Widget reset box is inoperable. When I check sensor logging their are no sensors. Why all of a sudden on two separate computers is the Temperature lighting affect no longer working and why is System missing from the drop down list on the Dashboard? Updating iCue is not an option of I want to have full functionality of my Corsair Void RGB 7.1 Headset. The uploaded images are from my ASUS Z-370E Gaming and are identical on my wife's ASUS Z-390E Gaming
  15. This lets me access the Bios, BUUUUTTTTT, the keys are are still inoperable. The only way to get this keyboard to work on the Z390-E Gaming outside of Windows is to force it into Bios Mode. The keyboard is LED's are lit, the pass through usb port works (mouse connected), but the keys are inoperable. The ASUS engineers are trying to recreate the problem and fix it, but no go so far. They have been getting back to me approx. twelve hours after I reply with results of their instructions.
×
×
  • Create New...