#60HE is messing up my aim by just it plugging and using my old keyboard

1 messages · Page 1 of 1 (latest)

junior quarry
#

Hello,

I just got my 60HE a few days ago and my aim has been off every since.

At first I thought it was just the new features of the keyboard (rapid trigger) but I have been able to confirm that by just plugging in the keyboard and not even using it my aim is still off somehow.

It's hard to explain because it isn't dropping frames but it feels like it might be super tiny microstutters and/or input delay.

The game (Warzone 2.0) feels less smooth too while just having the keyboard plugged in and it's extremely subtle as I hardly even noticed it until I tried plugging in and out the 60HE mid game.

I've tried different USB ports (currently in a USB 2.0 as recommended), turning off Rapid Trigger, Tachyon Mode, and resetting the actuation points back to default. All with no luck unfortunately.

I'm LOVING the keyboard itself but this is a major issue! I really want to keep this keyboard, please help! Thanks!

PC:
CPU: 5800X3D
GPU: 6800XT
Ram: 32gb CL-14 B-Die
SSD: 970 EVO Plus

deft hornet
#

have you tried turning off the gamepad mode in the wootility settings

junior quarry
#

yes, gamepad mode is off

deft hornet
#

cant really think of another reason especially since this would be the first case.

#

gamepad seemed plausible cause shooters often have aim assist for controller users

junior quarry
#

yea I googled for a while and couldnt find anyone else with the same issue

#

it's unusable in this condition unfortunately, what should be my next step to try to fix it?

deft hornet
#

did you ever do any sort of "usb overclocking" setting it to 8khz polling with some tools from the internet?

#

or install/use other tools to "improve performance"

junior quarry
#

no usb overclocking

#

and nothing else running that i can think of

deft hornet
#

hm.... have you tried a firmware recovery of the keyboard?

#

just to make sure its not a somehow bugged firmware

junior quarry
#

have not, i can try that next

#

is that the "Troubleshoot" section in the settings?

deft hornet
#

imma already mention a more technically versed troubleshooter @ashen scarab

junior quarry
#

ok i'll try that, the 60HE is ANSI right?

deft hornet
#

check the enter key shape

#

the wootility shows you which is which

junior quarry
#

oh, lol yea, it's obvious

#

thanks, ill give it a try!

timber granite
#

Brother I have the same issue!! I thought it was just me going crazy or old lol. I feel some kind of delay and it feels weird.

junior quarry
#

any luck?

obtuse musk
#

same here i had to up my sens for it to feel better

junior quarry
#

that doesn't solve my problem unfortunately, thanks tho

junior quarry
#

@deft hornet firmware recovery didnt fix this problem unfortunately, what else can i try to do to resolve this issue?

deft hornet
#

right now the best is wait for rocky to be online. he has way more indepth knowledge of error causes and how to troubleshoot new issues

junior quarry
#

okay, should i message him or just wait for him to reply here?

deft hornet
#

he was already mentioned

junior quarry
#

oh sry, wasnt sure, thanks for trying tony, i really appreciate it!!!

ashen scarab
#

If I understood you right you having FPS issues. Because you mentioned your aim is off, did that happen due to the FPS drops or is the mouse input effected?

#

If it's hard to explain, best to provide a video with explanationd.

junior quarry
#

fps is not dropping, but everything feels just a tiny bit stuttery even though fps seems to be unaffected

#

it does feel like the mouse input is affected

#

like there's more input lag or something

junior quarry
#

@timber granite @obtuse musk are you guys running AMD gpus?

timber granite
junior quarry
#

ok thanks, appreciate it

ashen scarab
#

If you want my help I would need more info.

lyric jackal
#

Personally, I have a 13700k. It is a tunned system. I haven't noticed anything. It's possible you just noticed these "fps issues" just now. The Ryzen series CPUs aren't monolith and have major 0.1 low issues. ( I know as I've had every zen cpu up to the 5950x) I also had two 5800xs.

#

I believe your fclk frequency is not stable if you have ocs higher than the 1600 imc frequency that's supported.

#

1600 imc=3200mhz ddr frequency

#

The other basic keyboard probably doesn't push the fclk as hard so you don't notice it and might have been on the edge of stability. This is all coming from experience but it's just an opinion.

junior quarry
#

Appreciate the help!

Was recording to try to show the issue as requested but the video is actually useless since it’s not visually apparent and frames, cpu, gpu, and ram performance is unchanged

Read some other stuff online looking for help that might be promising and will give any feedback that might be helpful

Im VERY impressed with the product (except this issue) and really appreciate the immediate support here on Discord. Really hoping I can find a fix!

Also, loved the added postcard that came with the keyboard.

That was unnecessary and extra but really showed the love and care of the company.

ashen scarab
#

The Wooting is a composite device with multiple interfaces. If you really already ruled out that the Wooting causes this it would be worth it to check which interface maybe is responsible for this. For that you can use the device manager, change the view to container so you know which nodes belong to the Wooting. Then you can disable one interface at the time and check if the problem is gone or not. Be aware that if you disable the configuration interface you can't use the Wootility anymore to configure the device. The Wooting has also two keyboard interfaces, one should be MI_01 and the other should be MI_03. If NKRO is disabled you should not disable MI_01 and if NKRO is not disabled you should not disable MI_03. Otherwise the keyboard function don't work anymore.

But as already suggested only the emulated controller should may cause issues for some games. It should be fine if the analog mode is set to no gamepad in the settings menu. But it's maybe worth to try the second Registry fix from this guide for the case Win messed up the joystick ID in a very bad way: https://help.wooting.io/en/article/issue-too-many-gamecontroller-devices-detected-n4efgy/

junior quarry
#

okay thanks, good to know! I'll look into that as well and report back!

lyric jackal
junior quarry
#

im at 3200

lyric jackal
#

Okay, just making sure it's not fclk being weird

junior quarry
#

appreciate it!

lyric jackal
#

Are you on windows 11 by chance? I had MAJOR issues with 11 not even using this keyboard. I had to downgrade. I had constant stutters like the ones you describe. It was horrid.

junior quarry
#

windows 10

lyric jackal
#

Okay, so it's not fclk (unless your ram is bad which I doubt) and you're on windows 10. You mentioned warzone 2.0. make sure voice chat is set to party only. The latest patch was also horrible and caused me to lose 100fps. Also make sure worker render Count is at 7

junior quarry
#

got all that except voice chat is completely off

lyric jackal
#

There's a bug where its constantly processing audio from people across the entire map, which caused me serious stutters.

#

Turn voice chat from all lobby to friends or party only and report back.

junior quarry
#

no difference

#

im trying the device manager stuff rocky recommended, fingers crossed

wicked zephyr
#

Does your mouse feel slightly different after changing the keystroke on your keyboard?

#

I don't know if it will help, but after trying initialization + recovery, turn off the gamepad mode and try using it without modifying the key input, and if the feeling is normal

  1. Check the RAM overclock by lowering it by one level
  2. Do not use the utility app version, try using the web version.
junior quarry
#

okay will try thanks! no overclocks at all but I was using the app version of wootility and will try a browser instead. wish it was available on Firefox...

ashen scarab
#

The Wootility is only there to configure the Wootings. You don't need to run it and have it open in the background. Also it should not have any impact at all.

#

The desktop version is a web site with a build-in Chromium web browser. So it's basically the same as when you open the web version on a supported browser.

#

If you really already know that it's due to the Wooting (which I don't believe) you should test it without the Wootiltiy running (which likely has no effect) and then disable one of the interfaces of the Wooting at the time to see which causes it (where I also doubt that it makes a difference).

junior quarry
#

PROGRESS!!!

#

so @wicked zephyr advice above worked! (mostly)

#

which was: restoring the keyboard through the web browser instead of the app and ended up fixing the issue completely

#

BUT, the issue immediately returns as soon as ANY changed setting is saved, including switching gamepad mode to disabled

#

switching between default profiles works fine and that's what im using for the moment but I cant save any custom settings at all without the unplayable input lag/microstutter returning

#

I've also disabled every interface possible within device manager with no success there unfortunately

#

the issue seems to be caused by any setting being changed and then saved to the keyboard which then immediately brings back the problem

#

Thanks for all the help and input so far from everyone, it's much appreciated!

#

if only restoring the keyboard could load my personal profiles lol

ashen scarab
#

What's the version number of the desktop Wootility and the web version?

junior quarry
#

Edge Version: 112.0.1722.64

#

Wootility v4.5.0

#

and it appears that restoring through the web browser and leaving everything default did not completely fix the issues, but it was an improvement it seems

ashen scarab
#

I want to know the Wootility version, not the browser version. The Wootility is basically a web site and the desktop version uses a packed Chromium browser to render it.

#

Because of that I mentioned that it should not matter if you open it in a Chromium based browser or via app. But the version of the Wootility itself matters.

junior quarry
#

Wootility v4.5.0

ashen scarab
#

So it should behave the same. Can you please cross check that on another system. Like to check if there the desktop version also messes up with the inputs while the web version don't.