k95 rgb Macro Input Buggy - Delays

[Shiromage]

Hello.

 

I recently got a K95 as a gift and I'm trying to fix an issue I have with macros. My previous keyboard, the G510 from Logitech, would input macros instantly. The K95 does not appear to input macros instantly despite having no delays recorded. This is frustrating to me because I don't want other keystrokes I'm making during gameplay to mess up the macro.

 

A specific case is World of Warcraft, where I have a simple macro that inputs

 

/focus

 

...followed by a newline to enter the command into the chat box (The box is opened by the first character, '/'). On the G510, the input happens so fast that I don't even see the chat box open when the macro starts. If the same macro is used on the K95, I see the chat box open, and sometimes characters are missing, as apparent by the error messages I get about invalid commands.

 

What causes this? Do these two keyboards give information to the computer in a different way? Is the K95 slower? Is macro processing different?

 

I have CUE version 1.13.36 and firmware 1.33. I have tried polling rates 1000 and 500 Hz.

 

I thank those in advance for any help or information regarding this issue.

[Toasted]

Can you upload the .act file for the key?

 

To export the .act file;

Actions > Right click the action > Export > Name it and save it to the desktop.

[Shiromage]

Can you upload the .act file for the key?

 

Sure, here is the focus macro file attached.

Focus Target.act

[Toasted]

Try this one.

 

it should work better according to Corsair James.

Focus Target New.act

[Shiromage]

Hello, Toasted.

 

Thanks for your reply. Unfortunately, the new macro you gave me didn't work. When I execute it, either nothing happens (probably an empty command) or my character says "s", meaning "/focu" was completely skipped.

 

As expected, the macro works fine in any text field, but fails to complete correctly with World of Warcraft's command line/chat box.

[Toasted]

Ok, It we'll need to play around with the delays in betweern the presses.

 

Try this action (Override the previous one) and see whether it can bring up the chat, type and enter it without issue in game. If it can, you could leave it as is or try to remove some delays and see whether you can get it to work.

Focus Target New.act

[Shiromage]

Hello, Toasted.

 

Even with these extra delays in your latest version, the action does not execute properly. The focus command executes more often now, but my character will still sometimes say "ocus", "us", or some other ending portion of the word.

 

Is this just something fundamentally different about the K95? On previous keyboards the entire command can be sent without delays and the game would take it just fine. It seems like my K95 only sends one key at a time, waiting in between frames or something.

[Toasted]

its probably more to do with Wow than the keyboard.. You could try messing with the delays and see whether you can get it to work more consistently.

 

According to Corsair James, you should be able to make a macro in-game for /focus and map it to a button on the toolbar then you can remap the G-key to that button. So you can try that as well.

[Shiromage]

Hello, Toasted.

 

This is a work around, however this requires action bar space. I'm running out and I still have about 20 more commands to create. This isn't the best option for me, considering the large space requirement, although it is possible. One of the main points of a keyboard with macro keys for me is so I don't have to use that space.

 

I've been playing with the delays on the macro, and currently I'm at 7ms between each event, and even still about 5% of the time the command does not execute properly. This makes the macro take over a tenth of a second to execute, which is unacceptable. I need my commands to execute as quickly as possible so that my other inputs do not cause error messages from the command line.

 

Understand that I do know that World of Warcraft's chat box does have an issue with accepting fast input (and may even be designed in such a way to prohibit scripts and other things that automate characters), but the fact that my old Logitech G510 could execute macros just fine without delays and without the chat box even appearing (without using preset keybinds), yet my new K95 doesn't execute macros the same way bothers me.

 

Is there a known explanation for the G510's macro execution? I really want to get to the bottom of this. It can't be preset keybinds because I make each macro manually.