Jump to content

Search the Community

Showing results for tags 'k55'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CORSAIR COMMS DEPARTMENT
    • Community Rules & Announcements
    • Live Event Announcements
    • New Product Releases
  • COMMUNITY DISCUSSIONS
    • Non-CORSAIR Tech, Benchmarks, and Overclocking
    • Games & Gaming
    • Battlestation and Build Showcase
  • TECHNICAL SUPPORT & CUSTOMER SERVICE
    • iCUE Software Troubleshooting
    • Build Hardware Troubleshooting
    • Gaming Peripherals & Audio Troubleshooting
    • Furniture and Ambient Lighting Troubleshooting
    • CORSAIR Pre-Built Systems Troubleshooting
  • PRODUCT DISCUSSIONS
    • CORSAIR iCUE
    • Build Hardware
    • Gaming Peripherals
    • Audio Devices
    • Battlestation Hardware: Ambient Lighting, Furniture, etc.
    • CORSAIR Pre-Built Systems
    • CORSAIR Technologies Q&A
  • Alternative Languages
    • Deutscher Support (German Support)
    • French Support
    • Spanish Support
  • LEGACY TOPICS
    • Corsair Enthusiasts Section
    • Corsair Product Discussion
    • Alternate Language Support
    • Customer Service

Categories

  • System Build Inspiration
  • Memory
  • Cases
  • iCUE CONTROLLERS
  • Maximizing Performance
  • Peripherals
  • Storage
  • Liquid Cooling
  • Gaming Mice
  • News and Events
  • How-tos and DIY
  • USB Drives
  • Extreme OC Mods
  • Gaming Keyboards
  • Power Supply Units
  • Gaming Headsets
  • Uncategorized

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Interests


Occupation


Optical Drive # 1


Homepage


ICQ


AIM


Yahoo


MSN


Skype

  1. Whenever the iCUE (v. 4.27.168) application is running, my Corsair K55 RGB keyboard is inoperable (80% of the time, the signal is not processed, even the rainbow wave keyboard light stops). Attached is a screen capture on what I see in iCUE app (note the disappearing-reappearing of the keyboard) At the bottom, below, is a slice of the exported log. I only added the part that repeats. I don't know where I can submit the entire log. Specs are also mentioned at the end. Steps to reproduce: - install iCUE v 4.27.168 software - have keyboard Corsair K55 RGB - open iCUE and wait 10 seconds - observe cyclic freezes (no signal) of about 15 seconds, then 5 seconds of signal, then repeat (no signal again, signal, no signal....). NOT OK - observe that during cyclic freezes, the rainbow wave light animation on the physical keyboard stops. NOT OK LOG SLICE: 2022-09-07 04:28:08.743 W cue.mod.nxp.hid_io.base: "NxpReport(Set SetDeviceMode)" failed. Retry... 2022-09-07 04:28:08.743 W cue.mod.nxp.feature: "NxpReport(Set SetDeviceMode)" failed for "K55 RGB" 2022-09-07 04:28:08.743 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&302528b7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-09-07 04:28:08.743 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-09-07 04:28:08.743 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col04#8&302528b7&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-09-07 04:28:08.743 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_01#8&c4deaf5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-09-07 04:28:08.743 I cue.dev.enum.adapter: Removing proto: "AF47A4435C3296F1F5001BC140048000" 2022-09-07 04:28:08.744 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&302528b7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed. 2022-09-07 04:28:08.745 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed. 2022-09-07 04:28:08.746 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col04#8&302528b7&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed. 2022-09-07 04:28:08.747 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_01#8&c4deaf5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed. 2022-09-07 04:28:08.747 I cue.hid_device_detector: Mark all tasks as finished. 2022-09-07 04:28:08.784 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-09-07 04:28:08.784 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-09-07 04:28:09.378 I cue.dev.hidenumerator: Found device VID 6940 PID 6973 Usage Page 12 Usage 1 2022-09-07 04:28:09.380 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col02\\8&302528b7&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.380 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col02\\8&302528b7&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.380 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col02\\8&302528b7&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.380 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col02\\8&302528b7&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.401 I cue.dev.hidenumerator: Found device VID 6940 PID 6973 Usage Page 65472 Usage 2 2022-09-07 04:28:09.402 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col03\\8&302528b7&0&0002")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65472")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.402 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col03\\8&302528b7&0&0002")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65472")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.402 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col03\\8&302528b7&0&0002")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65472")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.402 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col03\\8&302528b7&0&0002")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65472")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.416 I cue.dev.hidenumerator: Found device VID 6940 PID 6973 Usage Page 65474 Usage 3 2022-09-07 04:28:09.417 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col04\\8&302528b7&0&0003")("hid-direction", "input")("hid-type", "report")("hid-usage", "3")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.417 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col04\\8&302528b7&0&0003")("hid-direction", "input")("hid-type", "report")("hid-usage", "3")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.417 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col04\\8&302528b7&0&0003")("hid-direction", "input")("hid-type", "report")("hid-usage", "3")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.417 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col04\\8&302528b7&0&0003")("hid-direction", "input")("hid-type", "report")("hid-usage", "3")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.428 I cue.dev.hidenumerator: Found device VID 6940 PID 6973 Usage Page 65474 Usage 4 2022-09-07 04:28:09.429 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.429 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.429 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.429 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.429 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.430 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.430 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.430 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "feature")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.430 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.430 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.430 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.430 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.430 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.430 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.430 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.430 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "4")("hid-usagepage", "65474")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.440 I cue.dev.hidenumerator: Found device VID 6940 PID 6973 Usage Page 1 Usage 6 2022-09-07 04:28:09.441 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.441 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.441 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.441 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.441 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.441 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.441 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) not found. 2022-09-07 04:28:09.441 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Corsair Gaming K55 RGB Keyboard")("usb-pid", "6973")("usb-vid", "6940")("vendor", "Corsair")) 2022-09-07 04:28:09.441 I cue.mod.legacy.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&302528b7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3d&mi_00&col02\\8&302528b7&0&0001", ParentInstanceId: "USB\\VID_1B1C&PID_1B3D\\AF47A4435C3296F1F5001BC140048000\u0000") inserted. 2022-09-07 04:28:09.441 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&302528b7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms. 2022-09-07 04:28:09.441 I cue.devices: Device vid=1b1c pid=1b3d ignored by HidDeviceEnumerator 2022-09-07 04:28:09.442 I cue.mod.legacy.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3d&mi_00&col03\\8&302528b7&0&0002", ParentInstanceId: "USB\\VID_1B1C&PID_1B3D\\AF47A4435C3296F1F5001BC140048000\u0000") inserted. 2022-09-07 04:28:09.442 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms. 2022-09-07 04:28:09.442 I cue.devices: Device vid=1b1c pid=1b3d ignored by HidDeviceEnumerator 2022-09-07 04:28:09.442 I cue.mod.legacy.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col04#8&302528b7&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3d&mi_00&col04\\8&302528b7&0&0003", ParentInstanceId: "USB\\VID_1B1C&PID_1B3D\\AF47A4435C3296F1F5001BC140048000\u0000") inserted. 2022-09-07 04:28:09.442 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col04#8&302528b7&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms. 2022-09-07 04:28:09.442 I cue.devices: Device vid=1b1c pid=1b3d ignored by HidDeviceEnumerator 2022-09-07 04:28:09.442 I cue.mod.legacy.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_01#8&c4deaf5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3d&mi_01\\8&c4deaf5&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1B3D\\AF47A4435C3296F1F5001BC140048000\u0000") inserted. 2022-09-07 04:28:09.442 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_01#8&c4deaf5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms. 2022-09-07 04:28:09.442 I cue.devices: Device vid=1b1c pid=1b3d ignored by HidDeviceEnumerator 2022-09-07 04:28:09.442 I cue.mod.legacy.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col01#8&302528b7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd", InstanceId: "hid\\vid_1b1c&pid_1b3d&mi_00&col01\\8&302528b7&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1B3D\\AF47A4435C3296F1F5001BC140048000\u0000") inserted. 2022-09-07 04:28:09.442 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col01#8&302528b7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd" with delay 1000 ms. 2022-09-07 04:28:09.442 I cue.devices: Device vid=1b1c pid=1b3d ignored by HidDeviceEnumerator 2022-09-07 04:28:10.432 C cue.hid_device_detector: Failed to open: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col01#8&302528b7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd" 2022-09-07 04:28:10.432 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&302528b7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-09-07 04:28:10.432 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&302528b7&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-09-07 04:28:10.433 I cue.mod.legacy.enum: Protocol for DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&302528b7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3d&mi_00&col02\\8&302528b7&0&0001", ParentInstanceId: "USB\\VID_1B1C&PID_1B3D\\AF47A4435C3296F1F5001BC140048000\u0000") not found. Create new 2022-09-07 04:28:10.433 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col04#8&302528b7&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-09-07 04:28:10.433 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_01#8&c4deaf5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-09-07 04:28:10.433 C cue.mod.audio.enumerator: Cannot attach audio device to "K55 RGB". AudioDeviceComponent not found 2022-09-07 04:28:10.433 I cue.hid_device_detector: Mark all tasks as finished. 2022-09-07 04:28:10.433 C cue.mod.audio.enumerator: Cannot attach audio control device to "K55 RGB". AudioControlComponent not found 2022-09-07 04:28:10.433 C cue.mod.audio.enumerator: Cannot attach audio device to "K55 RGB". AudioDeviceComponent not found 2022-09-07 04:28:10.433 C cue.mod.audio.enumerator: Cannot attach audio control device to "K55 RGB". AudioControlComponent not found 2022-09-07 04:28:10.433 C cue.mod.audio.enumerator: Cannot attach audio device to "K55 RGB". AudioDeviceComponent not found 2022-09-07 04:28:10.433 C cue.mod.audio.enumerator: Cannot attach audio control device to "K55 RGB". AudioControlComponent not found 2022-09-07 04:28:10.437 C cue.mod.audio.enumerator: Cannot attach audio device to "K55 RGB". AudioDeviceComponent not found 2022-09-07 04:28:10.437 C cue.mod.audio.enumerator: Cannot attach audio control device to "K55 RGB". AudioControlComponent not found 2022-09-07 04:28:10.439 I cue.mod.legacy.enum: Initializing "K55 RGB" "(vid=1b1c, pid=1b3d)" 2022-09-07 04:28:10.471 I cue.mod.legacy.enum: Initialized true "K55 RGB" "(vid=1b1c, pid=1b3d)" 2022-09-07 04:28:10.489 I cue.dev.mgr: Candidate device for QMap(("bus", "legacy")("usb-pid", "6973")("usb-vid", "6940")) not found. 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 30 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 95 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 164 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 165 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 166 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 167 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 168 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 169 2022-09-07 04:28:10.490 W Unimplemented conversion for command: 161 2022-09-07 04:28:10.491 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "6973")("usb-vid", "6940")) 2022-09-07 04:28:10.597 I cue.devices: Device insertion processing complete for K55 RGB (vid=1b1c, pid=1b3d) 2022-09-07 04:28:10.597 I cue.dev.conn_proxy: Device does not support multiple connection types 2022-09-07 04:28:10.597 I cue.profiles.mappings_actualizer: Use volume wheel workaround for "K55 RGB" 2022-09-07 04:28:10.598 I cue.lightings.direct_player: Started lighting worker in 0x9e4 2022-09-07 04:28:10.631 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2022-09-07 04:28:10.632 I cue.firmware.index: "K55 RGB" firmware update, expected version: 30.9 same version found, on device: bootloader: 3.0 firmware: 30.9 2022-09-07 04:28:10.632 W cue.common.download: The download process is not started 2022-09-07 04:28:13.111 I cue.dev.enum.adapter: Before removed proto: "AF47A4435C3296F1F5001BC140048000" 2022-09-07 04:28:13.111 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditorDeviceComponent.qml:19: TypeError: Cannot read property 'deviceImageSource' of null 2022-09-07 04:28:13.111 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditorDeviceComponent.qml:20: TypeError: Cannot read property 'deviceFwVersion' of null 2022-09-07 04:28:13.111 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditorDeviceComponent.qml:18: TypeError: Cannot read property 'deviceName' of null 2022-09-07 04:28:13.111 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditorDeviceComponent.qml:21: TypeError: Cannot read property 'deviceUpdateController' of null 2022-09-07 04:28:13.111 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditorDeviceComponent.qml:23: TypeError: Cannot read property 'isGenericMultipid' of null 2022-09-07 04:28:13.111 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditorDeviceComponent.qml:24: TypeError: Cannot read property 'genericUpdateModel' of null 2022-09-07 04:28:13.113 W qrc:/qml-imports/com/corsair/cue/settings/UpdatesSettingsEditor.qml: Writing to "deviceModel" broke the binding to the underlying model 2022-09-07 04:28:13.113 W QCoreApplication::postEvent: Unexpected null receiver 2022-09-07 04:28:13.113 W QCoreApplication::postEvent: Unexpected null receiver 2022-09-07 04:28:13.113 W QCoreApplication::postEvent: Unexpected null receiver 2022-09-07 04:28:13.113 W qrc:/qml-imports/com/corsair/cue/mainwindowplugin/MouseoverPopup.qml:144: TypeError: Cannot read property 'currentPresetName' of null 2022-09-07 04:28:13.113 W qrc:/qml-imports/com/corsair/cue/mainwindowplugin/MouseoverPopup.qml:86: TypeError: Cannot read property 'enabled' of null 2022-09-07 04:28:13.113 W qrc:/qml-imports/com/corsair/cue/mainwindowplugin/MouseoverPopup.qml:78: TypeError: Cannot read property 'toolTipText' of null 2022-09-07 04:28:13.113 W qrc:/qml-imports/com/corsair/cue/mainwindowplugin/MouseoverPopup.qml:69: TypeError: Cannot read property 'title' of null 2022-09-07 04:28:13.113 W qrc:/qml-imports/com/corsair/cue/mainwindowplugin/MouseoverPopup.qml:61: TypeError: Cannot read property 'iconSource' of null 2022-09-07 04:28:13.142 W cue.mod.nxp.hid_io.base: "NxpReport(Set RgbZoneData)" failed with "The device is not connected. (1167)" 2022-09-07 04:28:13.142 I cue.mod.nxp.hid_io.base: Disconnect device "K55 RGB" 2022-09-07 04:28:13.153 W cue.mod.nxp.hid_io.base: "NxpReport(Set RgbZoneData)" failed. Retry... 2022-09-07 04:28:13.153 W cue.mod.nxp.feature: "NxpReport(Set RgbZoneData)" failed for "K55 RGB" 2022-09-07 04:28:13.183 I cue.lightings.direct_player: Stopped lighting worker in 0x9e4 2022-09-07 04:28:13.184 I cue.dev.enum.adapter: Freeing device: "AF47A4435C3296F1F5001BC140048000" 2022-09-07 04:28:13.184 W cue.mod.nxp.hid_io.base: "NxpReport(Set SetDeviceMode)" failed with "The device is not connected. (1167)" 2022-09-07 04:28:13.185 I cue.mod.nxp.hid_io.base: Disconnect device "K55 RGB" 2022-09-07 04:28:13.195 W cue.mod.nxp.hid_io.base: "NxpReport(Set SetDeviceMode)" failed. Retry... 2022-09-07 04:28:13.195 W cue.mod.nxp.feature: "NxpReport(Set SetDeviceMode)" failed for "K55 RGB" SPECS: ----------------------------------------------------- BIOS ----------------------------------------------------- Name : F50 Manufacturer : American Megatrends Inc. : Default string Version : ALASKA - 1072009 ----------------------------------------------------- Motherboard ----------------------------------------------------- Product name : B450 AORUS M Serial number : Default string Manufacturer : Gigabyte Technology Co., Ltd. ----------------------------------------------------- CPU ----------------------------------------------------- Name : AMD Ryzen 5 3600 6-Core Processor Serial number : Unknown Description : AMD64 Family 23 Model 113 Stepping 0 Frequency : 3593 Number of cores : 6 Number of logical processors : 12 ----------------------------------------------------- Physical memory ----------------------------------------------------- Manufacturer : Corsair Serial number : 00000000 Model : CMK32GX4M2B3200C16 Speed : 2133 Form factor : DIMM Memory type : DDR4 Capacity : 17179869184 ----------------------------------------------------- Manufacturer : Corsair Serial number : 00000000 Model : CMK32GX4M2B3200C16 Speed : 2133 Form factor : DIMM Memory type : DDR4 Capacity : 17179869184 ----------------------------------------------------- USB Controller ----------------------------------------------------- Name : NVIDIA USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) Serial number : PCI\VEN_10DE&DEV_1AD8&SUBSYS_C7291462&REV_A1\4&1FC990D7&0&0219 Manufacturer : Generic USB xHCI Host Controller ----------------------------------------------------- Name : AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) Serial number : PCI\VEN_1022&DEV_43D5&SUBSYS_11421B21&REV_01\4&2C18E2E3&0&000B Manufacturer : Generic USB xHCI Host Controller ----------------------------------------------------- Name : AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) Serial number : PCI\VEN_1022&DEV_149C&SUBSYS_50071458&REV_00\4&1FDE7688&0&0341 Manufacturer : Generic USB xHCI Host Controller ----------------------------------------------------- Name : NVIDIA USB Type-C Port Policy Controller Serial number : PCI\VEN_10DE&DEV_1AD9&SUBSYS_C7291462&REV_A1\4&1FC990D7&0&0319 Manufacturer : NVIDIA ----------------------------------------------------- Operating System ----------------------------------------------------- Name : Microsoft Windows 10 Pro Architecture : 64-bit : 10.0.19044 Service pack version, major : 0 Service pack version, minor : 0 : Windows Professional ----------------------------------------------------- User properties ----------------------------------------------------- Is run under administrator : 0 : User has administrator privileges : true
  2. I just installed icue 4, the latest version as of 12/29/21 and it is causing my k55 rgb keyboard to disconnect and reconnect over and over with the windows device tones. I tried doing a complete clean uninstall following the corsair how to, then installed icue4 again and the same issue happens. The keyboard can not type while this is happening. The keyboard works like normal if I uninstall icue. I also tried different USB ports on the motherboard IO. I have a gigabyte b450 motherboard with a ryzen 5 1600. The keyboard also seems to work normally if I just quit icue.
  3. Bonjour, J'utilise votre clavier K55 depuis plusieurs ainsi que l'application iCUE qui va avec. J'ai paramétré les touches macros de G1 à G6 sur des raccourcis claviers que j'utilisais sur OBS. Jusqu'à hier cela fonctionnait sans souci mais depuis elles n'ont plus aucun effet. Si je fais le raccourci clavier associé manuellement, cela fonctionne. OBS réagit. Mais les touches macros n'ont plus aucun effet. J'ai effectué la maj logicielle et firmware (branché avec touche Page Up + Page Down enfoncées). Mais rien n'y fait. Je n'ai pas su trouver une recherche correspondant à ma situation ce qui m'amène à écrire ce message. Je vous remercie par avance pour votre aide. _Waric
  4. So i have had the k55 RGB keyboard for awhile now, i got this keyboard and some other stuff a couple years back to get into PC Gaming, and after sometime. I noticed that there was a macro set on the g1 key, No problem right, so i went into ICue and noticed that there was nothing set on it. I didnt really think much of it, now like 3 years later im on a different pc now, using the same keyboard and that same macro is still set on there, and only is there when icue is not running. I have never seen anything like this before and I could not find anything online, Im already looking into getting another keyboard, but it just stumps me as to why there is a macro set on that key even though there isnt? If anyone else can think why that is that would be awesome! like I said this has been stumping me now for a couple years!
  5. Following will solve the install issue of the latest iCUE application and fixing the random command programing the G macro keys. Excellent product, but........ iCUESetup_4.16.194_release.msi installs without completely but does not launch, does not create a start or functional icon to start the application. Solution: Uninstall Corsair Icue application . Reboot. Install an older version of 4 series. (Corsair-LINK-Installer-v4.9.9.3.zip is good) (Not the 3 version). reboot.. Now install the lates version. In my case I installed iCUESetup_4.16.194_release.msi. Application works but does not install the Corsair K55 keyboard functionality G key programing. A pop up will instruct to install the following Stream Deck driver. Install Stream_Deck_5.1.1.14737.msi according to the iCue instruction (or manually install) in order to gain functionality with the ICUE application using the keyboard G macro programable key. Do not use the keymapping of Stream Deck.. Go into the ICUE application to map the G1-6 keys. ALL above installs originated from the an ORIGINAL problem with my Corsair out of the box. Random keystroke output when programing G keys. The mapping of the keys programmed from keyboard (with no computer application) produced a bunch of RANDOM key strokes that caused multiple running of all types of strange application on my windows screen when ever a G key was programmed. . With the iCUE application/Stream Deck, all the mapping works great. Both the keyboard and iCUE application has some careless code/firmware that does NOT work with all the computer. Took me a few hours to figure out the solution. My computer is not special. Just a Dell I7 processor running Windows 10.
  6. my keyboard shift key isnt working..i tried everything possible sticky key unistalled driver and installed it bk ,fn plus f4 reset thing , even esc reset thing,, its still not working., help me..and how much warranty it has,, i need help in it
  7. So let me get this straight. iCUE previously had lighting link for the K55 keyboard which worked with other corsair products such as the Harpoon mouse. Corsair decided to update the software and remove the K55 keyboard from the lighting link. Now Corsair are working with 3rd parties such as Asus to get lighting link working with their motherboards, such as my X470i. Yet, the K55 has still been left out and not allowed to integrate with lighting link. Even though its a Corsair product? Your options are simple. Either use the old software with lighting link features on both keyboard and mouse (no motherboard). Or use the new software with mouse and motherboard lighting link integration (no K55 keyboard). Or there is a third option. Use old software, get K55 keyboard into lighting link settings, then update software to most recent, which will also include the Asus motherboards. This glitch method allows for all three to synchronise with lighting link, but iCUE starts acting up and crashes occasionally this way. Q1. Why did Corsair officially remove K55 keyboard from lighting link? Q2. On a separate note. Why is your iCUE software acting like bloatware, eating up all the memory? I did raise this issue with Corsair customer support, but they lied and told me to uninstall and re-install new iCUE software again, which is load of nonsense. If I knew this before purchasing your products, I would have stayed well away and not purchased to begin with. In future I've made a decision not to purchase from Corsair.:mad: Look forward to hearing from you.
  8. im on my last straw and nothing frustrates me more than tech issues. I bought the k55 today and I am on a early 2015 Mac book air on Big Sur. Icue keeps saying no device detected. I've tried turning off bios, I've uninstalled and reinstalled, I've changed USB ports, unplugged all usbs besides the keyboard, restarted my computer, made a second profile in icue, NOTHING WORKS. please please please find the kindest to help me out, no one has answers me across several platforms. I wouuld REALLY appreciate it....
  9. This is a copy/paste message from other site that explains perfectly my problem. Just bought a new K55 keyboard earlier this week and things were great for the first two days, today though has been a big headache. What's happening is, when going from a COLD Boot, my computer hangs before Bios. This is only happening when my K55 is plugged in to any, USB 3.0 or USB 2.0, port. The only solution that's actually done anything is unplug/plug the K55 back in or turn off/on again pressing On button. My computer boots perfectly fine with another keyboard plugged in so long as the K55 isn't plugged in. However, when I restart instead of a full shutdown, my PC boots perfectly fine with the K55 plugged in. Anyone with this issue?
  10. Heyyo, I've really wanted a new keyboard for quite some time, and having RGB is a near-to must for me when it comes to computer accessories nowadays. Seeing how within my budget the K55 was as well, it was the perfect buy! The keyboard has been working far beyond my expectations, until last night. All the LED's at the topright stopped working, though the functions themselves worked (CAPSLOCK and NUMLOCK, specifically). I tried installing CUE and clicking around on mostly everything with no progress, leading me to uninstalling it as I saw it as unneeded software (but, is there a way to fix the issue using that software, i'll be glad to install it again). On a good note, reconnecting the keyboard seems to have fixed the LED's, but on a bad note, this is not issues I want with a new product, about a day into use. I've also had to do this twice so far. Should I bite the bullet and plug in my good old Logitech G110 and take this back to the shop first thing tomorrow, or are we rather looking at a firmware/software issue? I've seen people have similar problems, but do we yet have a "waterproof" fix or are we still lost on that? For what it's worth, it seems to happen when I use fullscreen applications, or at the very least, I've seen it happen whenever I sit playing Watch Dogs. But I guess it may, or may not be a coincidence. I've very recently updated my Bios and Chipset drivers for my motherboard (ASUS Z87-K), ensured that I've got the latest windows updates, and "force reinstalled" the generic keyboard drivers via Windows own device manager (following this guide). Thanks a lot in advance! EDIT 1: I NOW HAVE THE CAUSE OF THE ISSUE! (Though not the solution). When I unplug any other USB device, then plug it back in (for example, my headset charger), the Capslock and Numlock LED's freeze. Nice having the issue pinpointed, now for a solution. Anyone?
  11. So I usually unplug my keyboard at night to prevent my cats from turning on my computer, and it usually works fine the morning after. But today, when i turned on my computer, my keyboard stopped working. It still lights up and I can still use the numerical keypad, but i can’t adjust volume or use any of the other keys. It also won’t restart/reset, I held the escape key for 5 minutes and it didn’t start flashing. What should I do? Is my keyboard broken?
  12. I'm using the K55 Corsair keyboard, and usually I don't care much about RGB lighting and stuff, but found the macro features in iCUE pretty useful. For my toggle macros tho, I would like to change the lighting profile while the macro is actively running. I've searched multiple threads and people are saying I should be able to tie lighting layers to keys, but I can't find a feature like that. Is this possible at all with the K55 keyboard? How would I do it?
  13. Hallo zusammen, ich habe eine Corsair K55 Tastatur und auf der Seitentaste G1 ohne ICUE offen zu haben ein Makro. Die Frage ist jetzt kann ein Programm bei meiner Tastatur die G1 Taste beeinflussen und das Makro aufnehmen? Bekomme das ganze nicht weg... Vielen Danke im Vorraus für die Hilfe. Danke Walsh.
  14. Hi guys, Does anyone know if the K55 is available with English/Cyrillic keys? I've searched the forum and checked out the web shop but can't find an answer.
  15. Hey guys! new user here so forgive me if this has been covered already. I have a k55 keyboard and am having trouble with my lighting effects. I only have access to " Rainbow Wave Color Shift and Color Pulse". If you have any idea why that may be please let me know! Thank you.
  16. Hola! Me gustaría saber como puedo conseguir una tecla de remplazo de mi teclado Corsair K55 (versión ES) ya que me puse en contacto con soporte Corsair y solo me decían que tenían la versión (UA) y (UK), la verdad que necesitaría la tecla MAYÚS derecha del teclado versión ES de España, como puedo o donde conseguirlo. Gracias
  17. hey leudde meine relativ neuen corsair produkte m55 rgb pro und k55 haben beide seltsame probleme. kleine info: ich verwalte beide mit icue es hat zuerst mit der maus angefangen: plötzlich, nach etwa immer 10-15 minuten nach start des computers reagierte sie plötzlich nicht mehr und ich muss sie erneut anschließen. ab und zu sehe ich auch in icue ein kleines rotes dreieck bei den einstellungen der maus. dann fing es mit der tastatur an: manchmal reagiert sie nicht oder entkoppelt sich einfach so beim drücken einer taste und verbindet sich sofort wieder. machmal spammt die tastatur ohne dass ich etwas mache die letzte taste, die ich gedrückt habe und hört dann irgendwann wieder auf. auch bei der tastaur wird gelegentlich ein rotes dreieck angezeigt. ich habe icue reinstalliert, die geräte entfernt, updates erzwungen und komplett neue profile erstellt, aber nichts hilft. hat irgendjemand tipps? danke im voraus<3 leo
  18. Bonjour, Je possède le clavier K55 RGB, mais je rencontre diverses problèmes : Hier j'avais un problème : les touches couleurs (FN + ...) ne fonctionnaient plus j'ai donc cherché sur internet et j'ai trouvé la solution de faire F1 + Verrouillage Windows, depuis que j'ai fais ça les touches couleurs remarchent mais depuis le clavier n'est plus reconnu dans le logiciel CUE, et la touche verrouillage windows ne fait que clignoter et même en appuyant dessus je ne peux pas l'éteindre.
  19. So, the high CPU is even worse with the latest update to v3.20.80. I'm now getting 3.5 to 5% in the background and 7.5 to 10% when running the interface on a new i7-7700. This sort of thing has been going on for years and I'm sick of it and gotten to a point where I want to just uninstall and say goodbye to some of my mouse and keyboard functionality. Besides, I'm an old guy and I don't need half of that childish rainbow eye-candy. I don't need my system to look like something from Pink Fluffy Unicorns. What's held me back is I use functionality like sniper mode on my mouse and some of those extra keys and macros on the keyboard. Anyway, I found a partial solution: > Select the mouse > Click the hamburger menu to the right of Profiles > Click the memory card button which saves to device This will allow you to kill iCUE while retaining the mouse functionality. You can uncheck Start on system startup in the settings menu. The Corsair services stay running but it doesn't use as much CPU, although still a bit more than you'd expect from a keyboard and mouse. I can't speak for other devices. Unfortunately, the option to Save to Device is not available for the keyboard, or at least not my case (a K55). I'm just going to have to lose that functionality until Corsair sorts this out ... or until I need a new set and try some other brand. 😪
  20. I've already created a ticket, but posting here in the event that someone else has a solution. Recently the keyboard has been disconnecting and re-connecting on it's own accord noted with the 'bing bong' connect noise in Windows. Today it doesn't even do that. When unplugged and re-plugging it in I get no noise, it doesn't appear in the device manager, iCue, as well as USBDeview (an application I came across to attempt to diagnose the re-connection issue). So, yeah, the board is plugged in and lit up with a color I had set it at previously but it isn't accepting any input from keys. Things I've tried already that didn't work: FN + F4 while plugging it back in ESC while plugging it back in Changing USB ports ESC + F1 + Window Lock Button (and all manner of other combinations I've found all over the internet) Uninstalling the Corsair composite virtual input device from the Device Manager and restarting my system Uninstalling and re-installing iCue (the board is not listed there but my mouse is) Does anyone have any suggestions? I'm at wits end here. I'm typing this through a free crummy USB keyboard, so some sort of input works.
  21. My K55 RGB KeyBoard hasn't been lighting up for about a few months now and I figured it was nothing so I just let it not light up. Now, since it's summer I stay up later and it's kinda hard to see which keys I'm pressing in the dark. Previously the RGB helped with this. I tried plugging and unplugging it holding ESC. Then I did it holding FN and F4. I opened iCUE up and updated it. It is still not showing lights. I've also clicked the little sun looking light button. Nothing works and the lights wont show. How can I fix this?
  22. Bonjour, Je possède un clavier k55 rgb et celui ci n'est pas compatible avec la fonction lighting link. Au début, je me suis dit que c'était certainement du a une incompatibilité du matériel mais, j'ai trouvé un tutoriel qui expliquait que la fonction existait sur la version 3.1.133 du Corsair utility engine. J'ai donc installé celle-ci et cela fonctionnait effectivement. J'ai malheureusement du revenir à la dernière version du logiciel suite à une incompatibilité de mon casque (un Corsair hs 60 pro) avec l'ancienne version. Ensuite, suite à une mauvaise manipulation de ma part en réinstallant le logiciel ICUE (je n'ai pas supprimé les réglages) cela fonctionne toujours mais lorsque je cherche à changer les réglages du clavier, le logiciel se ferme. Je me doute que je n'ai fait que provoquer un bug mais cela renforce mon idée qu'il serait possible de rendre le K55 compatible avec le lighting link. Est-il donc possible de voir cette fonction arriver dans de futures versions d'ICUE?
  23. bought a new K55 RGB keyboard and the RGB backlights won't turn on. tried it with icue installed and uninstalled still facing the issue. tried manually resetting the keyboard using Fn + F4 method still not working. did I receive a defective keyboard?
  24. I have created a bunch of macros in ICUE. Example: 1. Press shift 2. Press 0 3. Release shift 4. Release 0 Tested it in browser, and results are as expected - ). But in applications (like Final Fantasy XIV Online) absolutely nothing happens. Any suggestion how to fix it?
×
×
  • Create New...