[Tech Issue] Double-click issues after 4.9 update - general issue

Platform, device version and operating system:
PC, Steam client
4.9
Win 10 (x64)

Screenshot or image:
None.

What you were expecting to happen, and what actually happened:
In the game menu or in battle there’s a new issue after a new update. I don’t think it’s my mouse, because it’s was functioning perfectly before the update, and there are no such issues in other games as well.
I could call it the Double-click effect. For example, if I click on some ability, it will also instantly close because of it. This also happens with Gem selection, etc. It’s also happening more if you press on the edge of some troop or ability, but the bug is still present if you click the ability in the middle, just a bit less frequently.

How often does this happen? When did it begin happening?
Very commonly. After the update 4.9.

Steps to make it happen again

  • Click on the icons in the game menu in general, including PvP, etc.
  • Play battles and try to select abilities or gems, etc.

On Xbox, I may have noticed the same thing.

You are double clicking, but it seem the time it takes to register two clicks has decreased. I have to be less sloppy button pushing, making sure my finger doesn’t slide of the button which can result in a double tap. Though I am not 100 % it is not my imagination.

But since you are on Windows, you can adjust your mouse double click speed.

1 Like

There’s no difference for me, I would have a look at the link UK posted.

2 Likes

The slider is set to default settings.
It could be a mouse issue then, because I just noticed that it started to cause issues outside of GoW.

Logitech G-203 Prodigy Gaming Mouse is updated with the newest drivers.
I may need a new mouse… after a good year of usage.

Were the drivers updated recently? If so, maybe they changed something?

2 Likes

No, over a year ago and they are still up-to-date. This is strange, still.
I’ll update this thread if any changes occur.

I’ll rather post a fresh video so that you can see it for yourself.

Call me strange, but the update 4.9.5 fixed the issue and I did nothing different on my end.

2 Likes