Jump to content

Corsair James

Corsair Employees
  • Posts

    4,584
  • Joined

  • Days Won

    10

Everything posted by Corsair James

  1. Everyone, I have a version of 3.38 that will contain the updated certificates - this still needs to be validated by our internal QA team but in the interest of giving everyone a chance to get their full functionality back, I am sharing it here: https://corsair-my.sharepoint.com/:u:/p/jamesca/EXTEaMBCs0ZFsYAiSa_yg5wBwBuX_SBtJYi_oxRZaYnrVA?e=zpHg6e Please note this is still considered beta until we have done a full regression.
  2. Hi everyone, I would like to provide a quick update: A.) We will deploy an immediate solution in the next week with an update to iCUE 3.38 that will contain new certificates with an extended expiration date. The reason for this is to provide a solution ASAP so everyone can regain the proper functionality of their devices on the legacy platform. B.) In January, we will deploy 3.39 which will contain additional fixes that allow the functionality of devices to persist even after expiration of the certificates. We have identified the root cause of the problem and this can be solved easily but will take additional time for testing. This is why I am moving forward with #1 above as the stopgap solution for now. As for some of the questions, I can do a quick FAQ: 1.) Why do certificates have an expiration date / Why can't the dates of the expiration be in the far distant future? Digital certificates cannot be infinitely persisting nor can expiration dates be far into the apocalyptic future - it is also not a CORSAIR process but rather one dictated by Windows App Development. 2.) Why did this issue happen? We have identified a bug that impacted the performance when certificates expire. We now have a resolution in place to prevent this so we do not have any degradation of performance when the new certificates expire. However it is expected that by the time this happens, iCUE 3 will have long been sunset by then. 3.) Was this intentional to force people to upgrade? No - it was simply an oversight and we apologize for the inconvenience. We missed this, the community caught it and we are very appreciative of the quick alert. We will fix this ASAP in both iCUE 3 and iCUE 4. 4.) Will there be ongoing support for all remaining legacy devices of iCUE 3? Yes but I do not have an ETA yet on when this happens. It is planned though to expand support for additional legacy devices in the future like what we did for Hydro Series coolers.
  3. Thanks for bringing this to our attention. All certificates will eventually expire, and since iCUE 3.x is discontinued software, this was overlooked as all of our efforts is to support iCUE 4.x. This isn't an intentional "suicide pill" as you're claiming - its just a consequence of discontinued software that has no development resources allocated to support it. I'll forward this issue to our devs and see what we can do about updating the certificate in iCUE 3 for those users who choose to remain on the legacy platform but I highly encourage everyone to update to iCUE 4 since we've already built in support for all of the legacy coolers.
  4. Release Notes for iCUE v4.13.223 are now available: https://forum.corsair.com/v3/attachment.php?attachmentid=41640&stc=1&d=1625769455 7/8 - We have updated the release notes with the following bullet under Known Issues: * Due to changes in theNVIDIAGeForce driver, fan support has been disabled temporarily-we are actively working on an update to resolve this. CORSAIR iCUE Software Release Notes v4.13.pdf
  5. Release Notes for iCUE v4.12.214 are now available: https://forum.corsair.com/v3/attachment.php?attachmentid=41461&stc=1&d=1623369287CORSAIR iCUE Software Release Notes v4.12.pdf
  6. CUESDK has been updated to v3.0.378! Release notes: Protocol version raised to 14. Extended `CorsairLedId` enum with `CLI_Oem101` … `CLI_Oem250` identifiers. Extended `CorsairLedId` enum with `CLM_7` … `CLM_20` identifiers. Extended `CorsairPhysicalLayout` enum with `CPL_Zones7` … `CPL_Zones20` identifiers. Extended list of supported devices with: IRONCLAW RGB K100 RGB K70 RGB MK.2 K95 RGB PLATINUM XT Lighting Node CORE M65 ELITE RGB MM700 Scimitar ELITE RGB STRAFE RGB MK.2 VENGEANCE RGB PRO SL VIRTUOSO RGB VIRTUOSO RGB SE [*]Dropped Visual Studio 2012 support [*]Removed `register_callback` example
  7. We can't provide these files as they're bundled with ASUS' AC software. We don't have access to these files individually. Part of the partnership with ASUS and iCUE is that we respect each other's software as this type of integration requires applications installed together. As for Lighting Service, this is what you need:
  8. Release Notes for 4.11.240 are now available: https://forum.corsair.com/v3/attachment.php?attachmentid=41240&stc=1&d=1620919445CORSAIR iCUE Software Release Notes v4.11.pdf
  9. Baio, You have several questions and I can help provide some answer. However, if you need an immediate answer, it is best to reach out to the tech support team. Here is what I understand what you want to know: 1.) Why is Armory Crate required to be installed? We are using ASUS' SDK and 'Lighting Service' to control their products. Without an install of their software, your ASUS motherboard or GPU will not be visible in iCUE. 2.) Why cannot you not use Armory Crate and iCUE simultaneously? Only one software can control the hardware at a time. If you have both software open, you'll get adverse effects because both of our hardware is not designed to be used simultaneously with each software. If you want to use ASUS software, then you must quit iCUE first (and vice versa). 3.) Why are you constantly seeing the Red Triangle? Red Triangle denotes some sort of error that prevents lighting control of your DRAM. The error could be any number of reasons (driver, memory controller, software access was revoked, etc.). The only way to properly diagnose this problem is to contact Tech Support so you can provide a log for our analysis. My advice is you should only be using iCUE 4, using the latest version of Armory Crate (not Aura Sync), and making sure only iCUE 4 is open. Make sure before you open iCUE that Armory Crate is NOT running.
  10. We need to make an enhancement on our side to increase the LEDs that are supported by their new cards. Unfortunately we weren't aware of this until after they released their product.
  11. Thanks for reporting this - this is not a known issue but I will report this so we can get it resolved. The iCUE window should remember the size and position so when you call to it from the taskbar or the task manager, it should be the same.
  12. iCUE 4.10.273 Patch Notes • Multipoint is now supported for all compatible Slipstream Devices. To start the process, users must have a combination of compatible Slipstream keyboard, mouse, and/or headset. A wizard has been implemented in the ‘Connections’ tab for your respective Slipstream USB Receiver. Please note a firmware update is required for all devices to support Multipoint pairing. • Resolved an issue related to firmware update with HS75XB • Implemented tutorials for K65 MINI • Implemented Weight Tuning feature for NIGHTSWORD • Implemented an Enhancement: Add Screen to Setup Wizard for RGB Fans • Implemented Enhancement for Nexus that Loop pages on start / end screens • Added CORSAIR One Blue Color to Custom Palette • Changed the Scaling for Opacity Slider • Changed "Set as Default" for DPI Presets to "Activate" for Clearer Consistency • Updated Message for 8K Polling on SABRE PRO mice • Resolved an issue with iCUE crashing when Skip is used during message to Re-plug Device • Resolved an issue that iCUE crashes from sleep and hibernation • Resolved an issue that Installer has a delay before launching successfully • Resolved an issue for Alert State that after "Reset" button to Restore to Normal Operation is pressed, it takes a few seconds for GUI to disappear and effect to take place • Resolved an issue that renaming a Lighting Effect when "hidden" disables the effect entirely • Resolved an issue with the Color Picker Wheel and Lighting Effects: Solid not appearing properly • Resolved an issue that Homepage sensor widgets do not update temperature units when changed until after iCUE restart • Resolved an issue for Home Screen Add Widgets Window that when scrolling through items, scroll bar keeps adjusting and popping the page up • Resolved an issue that when Enabling Dashboard Products by Toggle, all Items should be Selected • Resolved an issue that Sensors were automatically activated when user click to the on button in Dashboard tab • Resolved an issue that ALT + F4 on iCUE can cause window Title bar to appear • Resolved an issue that the 'Settings' tab doesn't close when its icon is selected • Resolved an issue that background should be darkened when Pop-Up is open • Resolved an issue that users should be able to deselect Remap: Keystroke field • Resolved an issue that Sensors on Home screen, when populated, all populate on the left column instead of filling in both columns • Resolved an issue that the scroll wheel doesn’t interact with the scroll bar of the home screen • Resolved an issue that system profile search engine cannot work automatically • Resolved an issue that Text Editor and File Explorer of Launch App Action should have a button added • Resolved an issue for MACRO that uncheck in "executive uninterrupted" button works incorrectly after restart system • Resolved a typo with surface calibration • Resolved an issue with spelling in Language Selection • Resolved an issue that the information of Import Profiles is not localized • Resolved an issue that the information of Export Profiles is not localized • Resolved an issue that the brightness of Nexus doesn't sync with iCUE when user starts iCUE first time. • Resolved an issue for NEXUS widgets that do not update temperature units when changed in iCUE Settings • Resolved an issue for Nexus that missing function "Mic Mute/Unmute" of VOID Surround Series headsets • Resolved an issue with Slipstream compatible mice unable to pair Wireless mice through the "Connections" tab • Resolved an issue for K100 that Control Wheel: Info is overlapped when users do the last instruction • Resolved an issue for K100 that allowed users to incorrectly select specific keys for predefined effects • Resolved an issue for SABRE PRO mice with the name being too long to allow for selection of buttons • Resolved an issue for K65 MINI that menu does not work when swapping menu key function • Resolved an issue for VOID PRO USB that beat effect shows the wrong color • Resolved an issue for DRAM that Lighting Effect Water that Ripple and Base colors affect the opposite element • Resolved an issue for Hydro X that Lighting does not work when multiple reservoirs are configured • MSI JCORSAIR Port will now match and share lighting data in profiles with Lighting Node PRO • Resolved an issue for K65 MINI’s FN Shortcut list not being translated • Resolved other various minor bugs and issues
  13. Contact our tech support and they can help you diagnose the issue.
  14. Remove the plugins and see if that helps.
  15. C-attack, we actually do backup iCUE 3 profiles. Going back to 3.38 will work without having to export the profiles when you migrate from 3 -> 4.
  16. I have to be honest - I don't believe we've ever tested iCUE on a setup like this. If you're crashing moving from one monitor to another, there could potentially be a bug that will follow iCUE 3 -> iCUE 4 since the backend is still the same. We can try to reproduce this but it would help if you can send us the application crash logs. Otherwise trying to replicate this will be difficult.
  17. I will report this to the devs - its odd CPURemote would cause this. This stuttering may be unrelated to our audio driver then.
  18. iCUE v3.38.61 Patch Notes:: Resolved an issue with updating HS70XB Resolved an issue with language detection on install Resolved an issue with KATAR Wireless undergoing a pairing issue after a firmware update Resolved an issue with ASUS and NVIDIA FE GPU showing up simultaneously Resets to Default for Sleep Timers have been added for all new KATAR (2020) mice Updated all URLs to use https:// ASUS plugin was updated to v1.2.2 Resolved an issue with profile switching not working when retain original is enabled Resolved various minor bugs and issues
  19. Hello Everyone- Based on everyone's feedback we have re-implemented all Legacy Devices listed below into iCUE 4.x. If you are still using iCUE 3.38.x, please update or download release version 4.24.193 or later to be able to use them with latest latest iCUE compatible products. https://www.corsair.com/us/en/downloads As we continue to develop new features in iCUE, we had to discontinue the support of certain products due to multiple reasons. While this list is a small snapshot of the 160+ products we support in iCUE 4, we understand some users of these legacy products may be unhappy or dissatisfied. We did not make these decisions lightly and users may continue using iCUE 3.38. While we do not plan on anymore updates to the older version of iCUE for product support, we will continue to resolve any crashes or critical security issues for the immediate future. Here is the list of products that will no longer be supported in iCUE 4: K66 Mechanical Keyboard Sabre RGB (2016 version) Sabre RGB Optical ((2015 version) Sabre RGB Laser (2015 version) KATAR (2015 version) VOID USB (2015 version) VOID WIRELESS (2015 version) VOID SURROUND (2015 version) Scimitar (2015 version) H80i GT Hydro Series Cooler H100i GTX Hydro Series Cooler H110i GTX Hydro Series Cooler H80i V2 Hydro Series Cooler H100i V2 Hydro Series Cooler H115i Hydro Series Cooler H110i GT Hydro Series Cooler H110i Hydro Series Cooler
  20. We do have an audio driver installed with iCUE but we haven't seen this issue internally. Does this issue happen with Windows Sonic enabled? This allows you to bypass our audio driver completely (and will confirm if our driver is the source of the issue).
  21. iCUE does use additional memory for all of the services it requires as part of the package (sensors, logging, active dynamic lighting, etc.). There isn't a solution to reduce this DRAM usage at this time but it also isn't considered extreme in comparison to other apps (my Discord for example also uses about 300MB).
  22. 1.) Thanks for the feedback regarding the UI. 2.) LLA Service is the RGB mechanism for DRAM control so this message was a failure of Windows to allow iCUE to install into 'Windows Services' - you will need to investigate your system. 3.) This is not something that should happen and may have been a coincidence - we don't delete anything unrelated to iCUE. You can download it from Corsair.com/downloads - whats the error?
  23. If you don't have a system restore point, then you'll need to go through a Windows command prompt and uninstall iCUE through it. As long as you remove the driver, this blue screen won't occur anymore. Unfortunately there is no other resolution as iCUE v2.x has stopped support for more than 3 years now.
  24. I am terribly sorry for the inconvenience and tragedy. There is a fix for this and that is simply to install the latest version of iCUE (as of this posting, it is v3.37). This blue screen is only a result of using the older versions of iCUE (v2.x)that existed more than 3 years ago As long as you don't have that version of iCUE installed, you'll be okay.
×
×
  • Create New...