Jump to content

SimonHF

Members
  • Posts

    10
  • Joined

Reputation

13 Good

About SimonHF

  • Birthday 12/26/1967
  1. I'm running iCUE 3.38.61 on a "MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)" with macOS Big Sur. iCUE recognizes my keyboard, mouse, but not the Nexus... should it? And how can I get it to work?
  2. I'm running iCUE 3.38.61 on a "MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)" with macOS Big Sur. The K95 RGB Platinum XT keyboard is connected and recognized via iCUE. I have sound redirected to my external monitor which works. When I try to use the keyboard mute or volume control then the sound via the external monitor is not affected. How to get this working?
  3. Update: I was experiencing this other issues to do with the mouse not showing up in iCUE [1]. After the mouse finally showed up in iCUE, after iCUE restarting, then the iCUE CPU usage at idle went down to about 4%. Which is much better than 20% to 25% :-) So maybe the mouse not showing up originally was causing the constant extra CPU? [1] https://forum.corsair.com/v3/showthread.php?p=1093259#post1093259
  4. Update: Due to another issue with iCUE CPU usage [1] then I quit iCUE to avoid the CPU. Later I opened iCUE again and was surprised that this time the mouse showed up and I could change it to 125 Hz to appease WindowServer. Not sure why it didn't work the first time... [1] https://forum.corsair.com/v3/showthread.php?p=1093260#post1093260
  5. I'm running iCUE 3.38.61 on a "MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)" with macOS Big Sur. With iCUE running but idling with on visible window on the desktop, then the iCUE process is continuously using 20% to 25% CPU. How to keep it running but without the CPU usage? Or is it okay to just quit iCUE when not using it?
  6. I'm running on a "MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)" with macOS Big Sur. Installed iCUE which only started working after a reboot. I installed it because WindowServer is using much CPU -- especially when I move the mouse -- and some posts online -- e.g. [1] -- suggest that gaming keyboards and mice can provoke WindowServer due to the sampling rate being too high. Idea is to reduce sampling rate via iCUE which might help get a lower WindowServer CPU rate. I have a K95 RGB Platinum XT keyboard and a Scimitar RGB Elite mouse. Upon reboot then iCUE worked and detects the keyboard and I can change the sampling rate down to 125 Hz. But iCUE does not detect the mouse. Tried replugging the mouse and/or the keyboard USB but with no luck. Obviously everything goes through a dongle on Mac because there are no USB ports on the laptop itself. I use a relatively expensive Anker hub with very many positive reviews. Should the mouse be detected by iCUE and how can I fix the issue or diagnose it further? Another question: If I hooked up the mouse to a Windows box running iCUE then could I change the mouse to 125 Hz there and would it remember that setting if I plug the mouse into the MacBook Pro? [1] https://www.reddit.com/r/mac/comments/juqcrd/calling_all_big_sur_users_here_check_windowserver/
  7. Update: Fixed my volume wheel issue: Turns out that my UGREEN USB Switch was causing the volume wheel to fail even though the rest of the K95 XT keyboard works. Plugging in the keyboard without the USB switch made the volume wheel also work. Solution: I upgraded to a better / different USB switch; "Cable Matters 4 Port USB 3.0 Switch Hub USB Sharing Switch for 4 Computers and USB Peripherals" [1]. Now the keyboard just works even though it is plugged in via the new USB Switch. Side note: After hot plugging the new USB Switch then the Nexus stopped working! It went into a kind of crash loop whereby Windows mounted it, but then immediately unmounted it, and repeated forever. This happened when it was plugged in via the USB Switch or directly into the laptop itself. Called the Corsair support line and they pronounced it 'bricked' and wanted to send me a new one. However, after the call, I restarted the laptop and everything just worked again... so false alarm. And tech support should always try and get the customer to reboot at least once :-) [1] https://www.amazon.ca/gp/product/B083JKDNRJ/
  8. Okay, I got a little further diagnosing this issue: I have the keyboard shared between two laptops via a UGREEN USB switch [1] which I use to switch USB peripherals between the two laptops. However, I noticed that if the k95 XT is plugged into the UGREEN USB switch then the volume wheel issue occurs, but if it is plugged into the laptop directly then the issue does not occur! I also noticed that if the keyboard is plugged into the UGREEN USB switch then only 'HID Keyboard Device' appears in Windows 10 'Devices and Printers' whereas when plugged in directly, then a 'CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyb...' device shows up. Question: Should the keyboard work in general with USB switches? And is there a USB switch known to work with the keyboard? It would be very annoying to have all my USB peripherals switching correctly except for the K95 keyboard... [1] https://www.amazon.ca/UGREEN-Computers-Peripheral-Switcher-One-Button/dp/B01N6GD9JO
  9. Got my k95 today and everything appears to work except the volume wheel. I can increase the volume. I can mute and unmute the volume. But decrease the volume it will not. I also looked at how the wheel is mapped etc using the software. It seems to be mapped correctly to decrease volume. There doesn't seem to be any funny business there. Also, the Nexus arrived too and the on-screen volume adjustment via the Nexus works just fine for both increasing or decreasing the volume. Any ideas why the k95 volume wheel is not decreasing volume for me? Or how to debug it further?
  10. My Nexus arrived today and I have some comments and suggestions: 1. I tried the individual CPU widgets but it only offers me 8 of them but I have 16. If I config the first 6 widgets for CPUs 1 thru 6 then the values on each widget does not look anything like any of the graphs of Task Manager. Bug? 2. The Load widget seems to work and be accurate. However, I was hoping that if I have a widget n times as wide then the graph will work for n times as much time. However, it's the exact same graph just stretched out n times. Would be great to have an option for that. 3. Would be great to have widgets to monitor memory, disks, network, etc too. 4. Could you not create some kind of custom API whereby e.g. an external app creates a bitmap every second and it can be transmitted to the Nexus? In this way then 3rd parties can create arbitrary content for the Nexus? For example, then I (or anybody else) could whip up a script to create monitoring for whatever I want and share it with others... 5. I always have task manager open and would love to show the following info on the Nexus either as widgets or myself somehow via some kind of custom API: CPU graph and/or percentage for each of 16 CPUs, Memory usage in GB, Disk I/O, and Network I/O. Thanks for reading! And -- as an experienced programmer -- I'm happy to chime in with implementation suggestions if necessary :-)
×
×
  • Create New...