Jump to content

Salsiccia

Members
  • Posts

    423
  • Joined

  • Days Won

    4

Salsiccia last won the day on May 14 2023

Salsiccia had the most liked content!

Reputation

34 Excellent

Converted

  • Occupation
    Professional IT Generalist

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Can confirm what c-attack has suggested, I have just experimented to be sure. I have an H150i Elite Capellix AIO so slightly different to yours, but the behaviour c-attack described is what mine does. I have a lighting effects setup (NOT Hardware Lighting) which is a monitoring profile where fan colours are set to Green/Yellow/Red based on Coolant temp for the AIO/Rad at the top of the case and 3 more fans on the bottom intaking to blow on the graphics card which plot the 3 GPU temp sensors that iCue exposes. The Hardware Lighting setup is just one of the default rainbow patterns. I have "Start on System Startup" un ticked. When the machine boots I see the Hardware/rainbow pattern. The second I manually start iCue it switches to my monitoring profile. If I tick "Start on System Startup", then reboot the PC it will come up with the monitoring profile and NOT the hardware rainbow one. For more accurate monitoring/measuring I use AIDA64 with an external sensor panel which is very flexibly customisable so you can see exactly what you want to see. I personally find this a better solution than the iCue monitoring, but that's just choice - each to their own ! I have run into issues in the past with iCue's interpretation of GPU load which is apparently a known issue - hopefully will get fixed soon, if it isn't already !! I also try to avoid running different monitoring/integration tools like Armoury Crate etc, I find they can trip over each other so I try to keep it as simple as I can, but I'm not always successful 🙂 Good luck with your setup !
  2. Latest change is I have reversed the above test and the K100 is now Bluetooth paired only and USB is disconnected and the behaviour is now what I want. iCue does not need to be running and I can cycle through the profiles via the keyboard and so far the connection has not been lost. So it appears that iCue gets confused when the keyboard has 2 different concurrent connections (Bluetooth pairing and USB cable). I guess in some way this is sort of understandable, but I do recall years ago in earlier versions of Windows it was possible to set NIC binding order where if you had multiple NICs on a computer, both connected (for redundancy, or bridging or whatever) you could specify which connection to use first and then drop back to the second (or third or ...) as necessary. So my solution is to stick with Bluetooth and then revert to cable when I need to make profile changes, check for firmware/software upgrades, charge the battery etc.
  3. Personally, I use AIDA64 with an external sensor panel (3rd monitor) and HWInfo for detailed monitoring of system stats. The sensor panel is great for a real time view of numbers and you can design the panel to whatever sensors you want as opposed to what iCue exposes. I also have the Corsair fans set colour coded based on GPU temps for the bottom 3 fans which blow as intake onto the GPU and Coolant temps for the AIO fans at the top of the case where they extract through the rad - these are a great instant visual cue, then HWInfo and AIDA for the drill down logging.
  4. Far from it - there is a lot about this ecosystem that seems to make little sense !!!!!
  5. There is a button on your keyboard on the top left with a little icon of a person. If you have the K100 it is to the left of the jog wheel. Press that and it cycles through the saved profiles on your keyboard.
  6. I have now unpaired the K100 Air from Bluetooth and it is now solely USB connected. Will monitor behaviour this way for a while
  7. Update: I plugged in a Dark Core RGB Pro SE mouse, just to charge in prep for setting it up later on. iCue recognised it and now reports 2 devices - the K100 Air and the mouse and shows the mouse charging - all good. I unplugged the mouse and hour or so late as I needed the cable to recharge my tablet and my K100 Air disappeared again. Had to unplug the keyboard and reconnect to get it recognised again. Something is not right here - I am running latest iCue software and latest firmware for both devices.
  8. I have a new K100 Air Keyboard, currently connected to my work laptop via the USB cable as I am still tinkering with the lighting settings which I cannot do over Bluetooth. I have noticed that several times a day iCue will seem to forget about the keyboard and it just vanished from the devices screen. I disconnect the USB cable from the top of the keyboard and reconnect it after a couple of seconds and suddenly it reappears again. I do have the keyboard also paired to the laptop via bluetooth and I am now wondering if this is causing some kind of conflict and iCue is confused about how to talk to the keyboard. If noone has any better suggestions I will try unpairing the keyboard and leave the only connection as the USB cable for a few days and see if the behaviour changes.
  9. P.S. - Ignore the System specs, that is my main gaming machine. This issue is on a work laptop, but I hadn't set it up as a system spec when I made the post, but that should not be relevant. Only Corsair device in play here is the K100 Air.
  10. I have saved 3 differed HW lighting profiles for my new K100 Air. I want Hardware Lighting because I do not want to have iCue running all the time and I prefer to manually flick between the profiles via the KB switch. It appears though that unless I have iCue running AND the Hardware Lighting entry selected the profiles do not work. As long as iCue is running and Hardware Lighting is selected then manually flicking between the different profiles via the keyboard works fine. It also appears that even minimizing iCue (but still running) it will occasionally deselect the Hardware lighting entry and therefore stop working. Sometimes disconnecting and reconnecting the keyboard cable will fix this and sometimes it won't. (I am running the keyboard physically connected at the moment as I am still fine tuning the profiles and I cannot do this over Bluetooth, but I can live with the cable for the time being. Screenshot attached of the HW Profiles section of the K100 Air as well as current status of software.
  11. Yeah that is my backup option to manually flick to one of the stored hardware profiles, but ideally I am hoping to have the bluetooth connection change also trigger a profile change.
  12. Forgot to mention I have a fresh iCue install 5.4.98 and firmware for the K100 Air is also the latest: 5.13.81
  13. Hi guys, Brand new K100 Air Keyboard arrived yesterday and I am setting it up today. I am using the G2-G4 keys to establish connections to different bluetooth devices - work laptop(G2), iPad(G3) and Android tablet (or maybe PS5) on G4. What I would like to be able to do is automatically change lighting profiles when I change the Bluetooth connection. So for example it has a purple theme when connected to my work laptop (Purple is a key company colour) and then maybe a rainbow wave when connected to iPad. This way I can tell at a glance which device the KB is talking to. I am sure I can achieve it by using hardware profiles on the K100 and switching whenever I change connections, but it would be neater to have the FnGn press toggle the profile at the same time. Is this possible? TIA Sal
  14. Update on this thread: Kudos to Corsair Support. I raised the ticket addressing my problem and Corsair responded with requests for more data re serial numbers, proof of purchase etc and they also asked for a video of the problem - all totally reasonable requests in my book. I replied with the proof of ownership details and serial numbers etc and promised to reinstall the problematic fan and get a video for them. I was delayed getting the video to them, but when I checked just now (I have not yet sent the video of the problem) I saw a message saying a replacement is en route via Fedex to me. That is what I call exemplary customer service. I have seen some negative comments on here of other folks' experience with Corsair customer support and I cannot comment on their circumstances, but what I can comment on is that when I reached out, I found Corsair Support responsive and supportive and willing to help. Good job Corsair, thank you for your approach. Best, Sal.
  15. Good points c-attack. On the current version of AIDA64 that I have you can select which tests you want to run. In my scenario I only selected CPU. In past tests I selected RAM to watch the RAM, GPU to watch the GPU, but in the tests I reported above I had only selected CPU. I was trying to keep the testing as "clean" as possible. I did note that OCCT does seem a lot more flexible in terms of what options you can give it so it is probably more reliable from that standpoint.
×
×
  • Create New...