test content
Logo
What is the Arc Client?
Install Arc
From Patch Notes Corsair Keyboard Support??
rgladiato
Member, NW M9 Playtest Posts: 313 Arc User
From the patch notes:
Hardware
Corsair keyboards with dynamic backlighting are now supported by the Neverwinter game client.
By default, the top row of keys have their lighting deplete as the player's health bar decreases.
The 1, 2, and 3 keys pulse as Daily Powers and the Artifact Power, respectively, become available.
The backlighting changes color as the player enters combat.
So how does one turn this on / use this?
Hardware
Corsair keyboards with dynamic backlighting are now supported by the Neverwinter game client.
By default, the top row of keys have their lighting deplete as the player's health bar decreases.
The 1, 2, and 3 keys pulse as Daily Powers and the Artifact Power, respectively, become available.
The backlighting changes color as the player enters combat.
So how does one turn this on / use this?
Nixon the TR
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
0
Comments
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Do you have a corsair keyboard with the backlighting feature? I would suggest starting with their FAQs on how to enable it through the keyboard software.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
I downloaded the latest firmware and software and no luck.
Please could you ask the person who created this feature to let us know how to use it.
I installed the Corsair Utility Engine and made sure the "Enable SDK" option was checked in the Global Settings page of the Corsair Utility Engine tool, then started NW, still no NW-specific lights.
Then I plugged it into a single USB 2.0 port and the keyboard turned rainbow colors, the USB driver installer triggered, the keyboard appeared in the CUE window as "K70 LUX RGB", and starting NW, I got the NW-specific coloring.
So, I think my USB 3.0 ports are broken on my machine. But the Corsair keyboard lights on NW seem to work.
Note: My Corsair keyboard has 2 USB plugs - one has a keyboard icon on it, the other has two arrows pointing away from each other with a dot in the middle. I had to plug the keyboard icon one in to make it work. The arrows+dot cord didn't seem to matter.
Super-double-check that the "Enable SDK" checkbox is enabled in the Corsair Utility Engine (which it should be by default). Otherwise, games can't talk to the lights.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
I have had "Enable SDK" on and off but neither option helps.
I've tried different polling rates and still no luck.
I've tried different ports and once again, no luck.
Why do I have other keyboards? Well if you have other programmable devices, such as a mouse with extra buttons, those devices show up as additional keyboards to be able to pass the key combos you program them with.
I have not tried disconnecting all other devices because that would be a pain to do.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Who the heck still uses a standard mouse for this kind of thing?
Neverwinter Census 2017
All posts pending disapproval by Cecilia
@rgladiato, Does your Corsair setup work in other games? Do they light-up in a game-specific way? Are you sure that USB port is working (like, when you changed around what was plugged in, did you move where the keyboard was attached and it started working?)
@rgladiato Did you have any custom profiles? Are they stored to device memory?
I would love to delete my device memory but Corsair in their infinite wisdom don't have an option to do that.
@miasmat I didn't touch my Corsair keyboard connection. It's plugged into the back of my PC where I can't easily reach it. That's why I didn't totally disconnect all peripherals. Just ones I could reach.
@miasmat Other games? What is this madness you speak of? I don't know if I have any other games that do the direct interface likes this. HOWEVER, I grabbed Corsair's CUE SDK, loaded it up in Visual Studio 2017, and made an app that does indeed work. (By "made an app" I mean I compiled one of their samples because I haven't even looked at C code for 20 years or more.)
Specifically I used their Color Pulse app.
Also my "other keyboards" are a Razer mouse, Logitech headset, a flight stick, and a Yubikey. I can get specific model names if you want but my point is I've lots of other non-Corsair equipment.
@chadvaliant Hmm... you might be on to something. None of my custom profiles are stored in keyboard memory. The first success with NWO I had was when I deleted all of my custom profiles. I don't remember if I was successful when I had a custom profile active or not. I'll have to try when I get a chance.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Maybe it's specific keyboard models that are broken/working? It works with a "K70 LUX RGB". Which model is working for @rgladiato and @chadvaliant?
@rgladiato I just tried to delete all my profiles but I can't delete the last one (there has to be one there) and I can't delete my device memory either (no option to do that). I made the remaining profile a blank fresh profile though. Still no luck getting it to work. If you have nothing stored to device then it might be worth you testing if a fresh profile makes it work. Not holding out much hope but it's something to try.
miasmat maybe you could try the opposite, save something to device memory on one of your test boards and see it that breaks it.
Only thing I haven't tested is forcing a firmware update despite already having the latest firmware. Really don't want to risk that though.
I deleted all profiles and the re-imported them. I uninstalled CUE and then re-installed. I re-imported profiles again after that. I changed the brightness (thanks rgladiato for that suggestion).
None of that seemed to do anything so I took a break and played some Borderlands. Got back to NW and bam, it was working!
The only thing I didn't restart NW for was the change of brightness so it could have been that or it could have been playing another game (unlikely as Borderlands doesn't have dynamic lighting). Could have been a combo and could have been none of that.
Thanks for your help though rgladiato and miasmat.
@miasmat First throw out all my previous guesses. I was able to get it working some of the time while leaving everything plugged in as I normally would be setup. In the course of restarting Neverwinter 20-30 times or more last night (I lost count) I noticed a pattern. I was able to predict success or failure by Watching the Cryptic loading screen with the progress bar. Normally my progress bar fills in about 3 seconds or less* and the keyboard wouldn't work. But sometimes for whatever magical reason the progress bar would take longer, say 5-6 seconds or more. Then the keyboard would work! So I experimented with adding delays when the gameclient.exe started loading. I did things like load other programs at the same time, lower the thread priority, etc. Now these didn't always significantly slow down the Cryptic loading screen but every time it did slow down the keyboard worked!
I got the most success by changing the proxy server from it's default of blank/none to US. I'd say this setting caused the loading progress bar to take a few extra seconds most of the time,like 4 out of 5 times. Lo and behold the keyboard worked those 4 out of 5 times.
My new and more data filled guess is it's all down to a timing issue. Perhaps when the game finishes loading the routine that searches for the keyboard is getting killed? Maybe before when I was shuffling around the USB devices it was causing Windows 10 to slow down just enough?
*My load time is fast because I have multiple SSDs in a raid 0 stripe set.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
On the plus side it was fun while it lasted.
Have you considered switching the in combat colour scheme with the out of combat scheme though? Soothing, calming blue for combat?!?! Angry orange for out of combat?!?! Seems backwards to me.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
Re: The color scheme. We picked it a long time ago, when we first added support for Alienware and Razer keyboards. We kept the Corsair scheme the same. I'm guessing the blue was picked because of the little blue circle that appears under your feet when you enter combat, and as a strong contrast with the red "hp low danger" color on the screen. And the orange was to match the lava theme on the loading screen. It's a cool idea to match the idle colors to the general color of the zone tho... I wonder if we could do that efficiently.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
On the subject of colours... What about changing the colour to match the current chat colour when typing in chat (only when typing of course)? Make typing in the wrong chat more difficult. This sounds more difficult to implement but might be a nice gimmick.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.
There is a newer version 2.15.83 (off the top of my head).Sorry you meant the SDK not the CUE itself, I should learn to read.
I am using the Corsair K70 LUX RGB with up to date software.
I am also using a Logitech G500s gaming mouse running the most recent version of the Logitech gaming software.
Give a man a fire and he's warm for the day. But set fire to him and he's warm for the rest of his life.