Now I'm well past the return policy and I can't really just send my only keyboard away. Its an issue I have brought up every time it has returned. Why would I be using some of my macros on the K95 RGB that way? Simply put its because periodically the regular keys I mentioned will refuse to input the functions. Wouldn't be a big deal if I wasn't relying on them to act as my left ctrl, left shift, tab, and caps lock. After doing so all of my macros were wiped. But in going through the process of trying to play the game I ended up having to reinstall CUE, which automatically chose the latest version available. So CUE doesn't play nice with ME: Andromeda, however EA has said that they resolved the issue in their latest patch which will most likely release on launch day. ![]() ![]() I was hoping there can be some sort of acknowledgement of this, because it works perfectly fine in CUE 1, but in CUE 2 there is a very big issue. I can't use CUE2 because of this annoying issue. Re-produce it with the original CUE v1, and this problem doesn't exist there. The effect is that the mouse "lags" on the screen, indicating there's a latency issue or something. To reproduce this: set the mouse DPI to 2000 or so, and set the sniper button to 100, and then move the mouse around at a steady pace and tap on the sniper button then let go of it instantly. Furthermore, releasing the sniper button is also delayed. ![]() Now whenever you attempt to activate it, there is a tiny delay which is insanely annoying. In the previous CUE software (v1), pressing the sniper button meant that it instantly activated it. In the current CUE 2 driver release (and any CUE 2 driver release), the sniper initialization appears to 'lag" and have a noticeable delay of ~250 ms or so. Is there still any acknowledgement of the M65 Pro sniper issue?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |