(354 MB) Corsair K68 RGB Keyboard Pilote/Utility 3.27.68 - CORSAIR LINK and CUE users If you are currently using CORSAIR LINK you MUST update to the latest version (Corsair Link Software v4.9.6.19 or newer). Catégorie: Claviers et souris Système: Windows 10, Windows 7, Windows 8. If you are using CUE, installing iCUE will automatically replace your CUE software and migrate settings.&nb. (354 MB) Corsair Sabre RGB Mouse Pilote/Utility 3.23.66 - CORSAIR LINK and CUE users If you are currently using CORSAIR LINK you MUST update to the latest version (Corsair Link Software v4.9.6.19 or newer). (354 MB) Corsair K70 RGB LOW PROFILE Keyboard Pilote/Utility 3.23.66 - CORSAIR LINK and CUE users If you are currently using CORSAIR LINK you MUST update to the latest version (Corsair Link Software v4.9.6.19 or newer). (328 MB) Corsair K70 LUX Keyboard Pilote/Utility 3.23.66 - CORSAIR LINK and CUE users If you are currently using CORSAIR LINK you MUST update to the latest version (Corsair Link Software v4.9.6.19 or newer). However, I advise using iCUE is the best method when possible.Ĭorsair K65 LUX RGB Keyboard Pilote/Utility 3.17.94 - CORSAIR LINK and CUE users If you are currently using CORSAIR LINK you MUST update to the latest version (Corsair Link Software v4.9.6.19 or newer). You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol).įor users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. Users should use iCUE (Windows) to update their hardware. Devices that will support iCUE without requiring a firmware update: This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. To resolve this problem, we had to implement a new protocol for firmware. Those who tested CUE2 would be familiar with this issue. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. 1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform.Ģ.) Complete iCUE for Windows and then port it over to macOS.ģ.) Validate it for MacOS on desktop and laptop models to ensure a clean transition.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |