ALT not registering or being released while held down

Comments

51 comments

  • Avatar
    David

    John Horvath Ok thank you so much. I guess as long as it is possible and doesn't take hours to produce then they would be able to reproduce it on the desktop? 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    David, I have uploaded a recording to YouTube that shows both my physical finger presses, as well as the key logger, in real-time during game-play (took me longer to rig up the camera and learn OBS & Shotcut than to reproduce the issue), but here it is:

    https://www.youtube.com/watch?v=xR1LhwKsAHY?vq=hd1440

    Also here is a annotated excerpt from the log, as it might be hard to see it in the SD video clip (make sure to watch at 1440p + Full-screen), but the same conditions continue to hold true, LAlt is being pressed/held and S is being pressed in quick succession, which causes LAlt to release despite still being completely depressed.

      2021-09-27 10:44:39:9390  LCtrl| LAlt↓
    2021-09-27 10:44:39:9590 LCtrl↑ LAlt|
    2021-09-27 10:44:40:0980 LAlt| X↓
    2021-09-27 10:44:40:4600 LAlt↑ X|
    2021-09-27 10:44:40:5980 X↑
    2021-09-27 10:44:40:6900 C↓
    2021-09-27 10:44:40:8960 C| LAlt↓
    2021-09-27 10:44:41:0320 C↑ LAlt|
    --------------------------------------------------------------------------------
    2021-09-27 10:44:41:1571 LAlt↑ This should be: LAlt| (LAlt Still Down)
    2021-09-27 10:44:41:3151 S↓ This should be: LAlt| S↓ (LAlt Still Down)
    --------------------------------------------------------------------------------
    2021-09-27 10:44:41:8621 S↑ (LAlt Still Down)
    2021-09-27 10:44:42:1621 S↓ (LAlt Still Down)
    2021-09-27 10:44:45:1223 S| C↓ (LAlt Still Down)
    2021-09-27 10:44:45:4573 S| C↑ (LAlt Still Down)
    2021-09-27 10:44:45:7283 S| C↓ (LAlt Still Down)
    2021-09-27 10:44:46:0053 S| C↑ (LAlt Still Down)
    2021-09-27 10:44:46:6204 S| X↓ (LAlt Still Down)
    2021-09-27 10:44:46:9164 S| X↑ (LAlt Still Down)
    2021-09-27 10:44:47:4384 S↑ (LAlt Still Down)
    2021-09-27 10:44:52:7207 C↓ (LAlt Still Down)
    2021-09-27 10:44:53:1017 C↑ (LAlt Still Down)
    2021-09-27 10:44:53:3528 X↓ (LAlt Still Down)
    2021-09-27 10:44:53:7058 X↑ (LAlt Still Down)
    2021-09-27 10:44:54:6398 Z↓ (LAlt Still Down)
    2021-09-27 10:44:54:7568 Z↑ (LAlt Still Down)
    2021-09-27 10:44:56:1529 LCtrl↓ (LAlt Still Down)
    2021-09-27 10:44:56:4529 LCtrl↑ (LAlt Still Down)
    2021-09-27 10:44:57:4080 C↓ (LAlt Still Down)
    2021-09-27 10:44:57:6690 C↑ (LAlt Still Down)
    2021-09-27 10:44:57:8900 X↓ (LAlt Still Down)
    2021-09-27 10:44:58:1300 X↑ (LAlt Still Down)
    2021-09-27 10:44:58:5871 S↓ (LAlt Still Down)
    2021-09-27 10:44:59:0391 S↑ (LAlt Still Down)
    2021-09-27 10:45:00:4262 LCtrl↓ (LAlt Still Down)
    2021-09-27 10:45:00:5762 LCtrl↑ (LAlt Still Down)
    [LAlt physically released at this point, but no change was recorded, Windows still thinks it's not being pressed]
    2021-09-27 10:45:03:0263 LAlt↓ (LAlt Repressed & Working)
    2021-09-27 10:45:04:3474 LAlt↑
    2021-09-27 10:45:05:2654 Escape↓
    2021-09-27 10:45:05:3164 Escape↑
    2021-09-27 10:45:06:7075 LButton↓
    2021-09-27 10:45:06:7735 LButton↑
    2021-09-27 10:45:07:9196 LButton↓
    2021-09-27 10:45:07:9866 LButton↑
    0
    Comment actions Permalink
  • Avatar
    David

    That's incredible, thank you so much John Horvath ! I will send this to my devs and hopefully they can replicate and fix this issue. I will keep you updated. 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    David, does the offer to send me a V2 for testing still stand? I kinda got tired of having a dual keyboard setup so I am no longer using my CODE V3 (as it's just not worth the hassle of flipping back and forth).

    Also, if there was some channel to get notifications about firmware updates, I would be willing to subscribe and test out any new firmwares as they are released.

    0
    Comment actions Permalink
  • Avatar
    David

    John Horvath I'm very sorry for the delay, we're been very busy due to the holiday rush. Yeah for sure I can send you one! If you'd like to return your V3 for a refund please let me know. 

    The developers did test this with a game they had and they told me they could not reproduce this issue, so I'm not sure if they can fix it or not, I told them to check this thread and use your tools also. 

    There should be a button on the firmware page where you can click to "follow" and it should notify. I just updated it today with the 2.8 version, but it will not fix this particular issue you are having. 

    Thank you! 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    Just a heads up, I did receive the V2 tester board (please note the stems on the LShift and LCtrl keycaps arrived broken, with the keycaps not even attached to the board, I was able to get them back into place and hold just fine, but they are damaged). I'm not sure how to tell what firmware is currently on the board (is there a way?), but I have logged several hours of testing already and cannot reproduce the issue with the V2. I'm going to continue to test further, but it could be a hardware difference on the V3s that causes this problem. I'm assuming the PCBs and Chipsets are fairly different between the two.

    0
    Comment actions Permalink
  • Avatar
    David

    @John Horvath I'm sorry to hear that the keyboard arrived damaged. I definitely checked it before shipping so I'm sure it must have been damaged on the way, and I apologize for that. It is interesting to me that this V2 is not able to reproduce this issue. The V2 and V3 are different in just about every way except for the way they look on the outside, the PCB is different, the chips on it are different, etc. The firmware on the V2 should be identical / similar to the V2.5 firmware that is offered on the V3, but I don't believe it is the firmware that is causing the difference. 

    Let me know if a V2 is a solution for you and I can send you another one (that isn't damaged) and get the broken one back from you. 

    Thank you! 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    @David, I would still like to hang onto my V3 (really love the feel of those Zelio switches for general typing), though I'm not opposed to purchasing a new CODE V2 104-Key Mechanical Keyboard - Cherry MX Clear if they are still available (what would I be looking at pricewise?).

    Crazy question though... is there a CODE V4 in the works? I like the options the V3 has and the upgradable firmware, I could just wait on it, if a V4 is in the near future.

    P.S. The @'s in posts don't seem to be working anymore...

    0
    Comment actions Permalink
  • Avatar
    David

    @John Hovath 

    Ok no problem, the V2's are not available anymore but I do have some personally - I can send you a different one or fix that one that got damaged in shipping? 

    We don't have a V4 in the works as we're still making updates to the V3, next thing will be hotswap sockets but the firmware and the PCB will remain largely the same. 

    That is strange, I'll have to ask zendesk support on why that functionality stopped working :( 

    Please let me know, thank you! 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    @David, Yeah it definitely looks like UPS did not handle the package with care, as the housing is a little loose as well right below the space bar (maybe they dropped it, it was during the holiday rush).

    Let me know where I should ship it back to (I pretty much tested it to death without issue, so the V2 looks solid). Not sure if I should just return to sender (the shipping department) or if you would prefer I return it elsewhere. I'll wait to hear from you.

    If you do have another unused CODE V2 104-Key Mechanical Keyboard - Cherry MX Clear sitting around, I would definitely take it. It's very close in feel to the Zealio, and well... it works without issue, which the the main thing.

    Still hopeful that the V3 get's fixed someday, I did subscribe to the firmware feed, so I'll continue to test as new ones are released, and if there is a breakthrough, I'll definitely post it here.

     

    0
    Comment actions Permalink
  • Avatar
    David

    @John Horvath - Ok sounds good! I just emailed you a UPS return label, please send back the broken board and I'll send you as good as a clear V2 as I can find :) Thank you for your help! 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    @David - V2 has been sent back this afternoon, tracking number should go live by the end of the day. Thanks again.

    0
    Comment actions Permalink
  • Avatar
    David

    Awesome, thanks John, let me find the best 87-clear for you and I will ship it out! 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    Oh, I assume there are no 104-Key MX Clears left then... I use the numpad like crazy when programming, so I would really prefer a 104-Key, if there are no clears I'd be fine with any other non-clicky MX (Brown, Red, Silver). Thanks again I really appreciate this.

    0
    Comment actions Permalink
  • Avatar
    David

    I'm sorry I thought you had an 87-Key, it's alright I think I can find a 104-Key in clears also. I did bring one to work today to send to you but I'll have to find you a 104-Key now, my apologies. I will be able to bring it in next week. 

    Thank you. 

    0
    Comment actions Permalink
  • Avatar
    David

    Hello John, I was able to find you a really nice 104-clear so I've shipped that out for you today, you should have been emailed a tracking number, please enjoy. Thanks so much for your help! 

    0
    Comment actions Permalink
  • Avatar
    John James

    A few updates...

    I tried the console on a different machine with USB 3.0 ports and experienced a similar issue.

    I likewise got the "WASD Firmware 2.40.exe" after messaging, and refreshed effectively, however it didn't resolve the issue.

    I couldn't say whether the other ALT key is impacted, as I have just had this occur while gaming, and LEFT-ALT is the key I use for pushing ahead. This could be a mix, or arrangement of keys, that causes it, as I utilize the left hand side CTRL, ALT, SHIFT, Z, X and S for development; and fundamentally I notice this while endeavoring to run (S) forward (ALT).

    I introduced Switch Hitter, however it doesn't seem to sign behind the scenes. So I will search for something that can log while I game to get it in the demonstration and attempt to detach an example and perhaps sort out some way to replicate it reliably.

    P.S. Would it be advisable for me to return to the 1.20 firmware?

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    Hey John, I can't speak for the firmware side of things, but...

    I had the same issue finding a trustworthy "free" key logger that logged in the background, which is why I ended up writing my own.

    You can find the source code at: https://github.com/Xorcist77/Stateus, feel free to give it a try, it's how I generated all my logs shown in this thread. If you don't want to (or aren't able to) compile it, I also generated pre-built binaries which you can find at: https://github.com/Xorcist77/Stateus/releases, it's only available for Windows at this point. I haven't tested it against Windows 11 though, but it is confirmed working on Windows 7 & 10.

    Note that my logger only logs changes to the keystate, so holding a set of keys will not generate thousands of frivolous log lines, but any time key is pressed or released a new timestamped log line will be generated showing the current state of all the pressed keys.

    I'd be interested to see your findings and compare with my own. Up until now I was the only person who ever encountered this issue.

    0
    Comment actions Permalink
  • Avatar
    David

    Hello John James, from our testing changing the firmware will not affect this issue, so you may want to try it out, but I think you will conclude that the same thing you're seeing will be unrelated to firmware. 

    Thanks! 

    0
    Comment actions Permalink
  • Avatar
    John Horvath

    Lissa? Why is your post 90% identical to John James' previous post? If I were an English teacher I'd most likely have to cite you for plagiarism. Sorry for my skepticism, but did you really encounter this issue?

    0
    Comment actions Permalink
  • Avatar
    David

    @John Horvath

    That comments was unfortunately spam - they will copy a previous post, change a few things and then add a secret link, I have deleted it. Thanks! 

    0
    Comment actions Permalink

Please sign in to leave a comment.