Jump to content
Corsair Community

Testing123

Members
  • Posts

    50
  • Joined

Reputation

10 Good
  1. I agree! Seems like a pretty big market for other types of mechanical keyboards, I wonder why Corsair has jumped on the bandwagon with K95 RGB Platinum keycaps.
  2. This is very interesting. I'm not sure how I skipped over this message in my previous read of the thread... glad I revisited it. What's interesting for me is: This basically means the sound generated is in the higher frequencies. My hearing now taps out at approximately 12,000 Hz (that's a very rough estimate using my iPhone). Yeah, I'm 'older'... plus too many gigs with hard-hitting drummers or deaf guitar players :-) , as well as mucho hours in fixed wing aircraft. That said, maybe I won't have any trouble with coil whine. ;-)
  3. I do this as well. Not sure why... I just feel that it may help to extend the life of the LED's, but I have no empirical evidence of such.
  4. Note: As you read the following, keep in mind that my assessments and views (no pun intended) are based on 62 year old eyes and I always have to wear glasses while using my computer. I have a fairly recently purchased K95 RGB Platinum. I've found that I like an all white keyboard illumination with a few keys (F, J, HOME and END) accented in red and the 'G' keys (G1 though G6 on the far left of the keyboard) each a different color depending on what I've programmed them for. In this type of scenario, I can see the secondary, non-alpha (shift) characters pretty well. I just ran through a couple of other profiles to see how some of the 'less bright' type of illumination settings affect the characters you're interested in. I find that I can see the secondary characters associated with the number keys (atop the keyboard) as well as the larger type of characters such as { } | < > and ?. However, characters like : and ' are a bit more difficult for me to see, although still illuminated. (Again, consider my vision constraints) -- I find the secondary 'word(s)' on the number pad a bit difficult to read, especially when using a less bright illumination. More specifically, I'm referring to INS, DEL, END, PG DOWN, HOME and PG UP. At first I was a bit put off regarding the bold and 'blocky' font used for the key characters, but it seems to help with illumination and I'm finding the primary keys pretty easy to see even with the 'darker' profiles. I suppose my biggest issue has been trying to get used to the secondary characters (word/s) being below the primary characters on the keys themselves. If your not familiar, here's a 'normal' number one key: ___ | ! | | 1 | ---- Here's the K95's number one key: ___ | 1 | | ! | ---- This is done because of the way the LED's are situated on each key. It makes the primary character really well lit, but the secondary character does not stand out as much. It's also, for me, a bit of a pain to get used to. I hope this has helped...
  5. Oh, too bad, sounds like a great feature.
  6. I’m running CUE version 2.14.58 and it exhibits the behavior you describe. What happens for me is that when I do a power on or restart of my computer, the download button does NOT show up (I have CUE set to start on system startup). What I have to do is completely quit CUE and reload it. After that, the download button shows up and everything’s fine. See if that works for you until the devs find a cure.
  7. Hmm... well, I hope they'll add it in a future version (not like they don't have enough to worry about already).
  8. I have several profiles. Some of them have been programmed using the advanced mode while others are set up in standard/basic mode. Is there a setting or switch to set so that when a profile is either selected manually, or automatically, the correct mode (advanced or standard/basic) is automatically engaged? Thanks…
  9. I was able to find a solution thanks to your suggestion. What I had to do was set up an individual Action: Disable -> Disable key if Lock button is on for every key on the keyboard; 116 Disable Actions! 2 Keys were not mapped. The obvious one was the Windows Lock Key. The other key, the Backlight Brightness Key, did not function as the other keys did. If I set it with a Disable Action, it wouldn’t work at all. That is to say, no matter if the Windows Lock Key was on or off, pressing the Backlight Brightness Key did not change the light level of the keyboard. It didn’t matter where in the Actions list I placed the action, it would not function. I believe this to be a bug in CUE. I hope someone can look into this and rectify the problem. Other than that, I am happy I was able to find a solution. Seems like a lot of work just to be able to turn off the keyboard, but at least it’s done.  Thanks again for the suggestion!
  10. Oh, hadn't thought of that. I'll look into it. Thanks so much for your advice!
  11. Attached are the CUE logs that were present in the logs folder just now. Hope these help. 2017-05-23T11-44-47.zip
  12. Ah, sorry for the misinterpretation. Ok, I'll give that a shot. I presently have no other machine to try CUE on. The machine I am using has recently had a clean install of windows, so that shouldn't be the issue (although I understand, assume nothing). Might be the version or the OS Build of Windows I'm using. Here's that info again: PC operating system: Windows 10 Pro 64-bit Version 1511 OS Build 10586.916 I'll grab the log files, zip them up and attach them to a reply to this thread. Thanks for your reply!
×
×
  • Create New...