That temporarily resolved it, but eventually reoccured after a few mins if rapid movements.
I noticed that sometimes the script will get bugged based on a certain combination of keys, but has yet to be determined. When using, holding down the left strafe moves right. I need to release all the keys and then it works again, and I think that is when i get the error I posted above.
For reference, I copy/pasted @pcooke9 ‘s version from his Gaming Tips thread. I then configured the inputs to my layout and changed nothing else. I could show you my exact script if you want, but it’s just identical to yours but with different inputs.
Do you mean it always does that, or only when it starts to bug out? When that happens, can you maybe try to switch focus to a text editor or something to see if it’s just a stuck key? Or maybe just spam the WASD keys in a text editor to trigger it there?
How often does it glitch; like how long between issues? Do you trigger any other macros around the same time you’re strafing, or within a couple seconds of letting go of the strafing keys?
When using the snap-tap macro on my old early unit UHK80, it was taxing the MCU pretty hard, and would cause all kinds of serious lag (several seconds), output issues, stuck keys, etc.. My UHK60v1 is boxed away in storage ATM, but it worked flawlessly with my V2 last time I tried it. I haven’t played any games that need snap-tap in a couple months, but I’ll check it out on the V2, and my newer UHK80 tonight.
The macros were developed and tested on UHK60v1 and UHK60v2 on firmware 11.x. There have been significant changes in the firmware starting from 12.x, and I found that my macros behave quite differently in the newer firmware. This is true for the snaptap macros just as well as the homerow mods. I think later firmware deals much less effectively with long-term running background macros. Both my snaptap and hrm solutions use such background macros, and they worked much better on firmware 11.x.
I’m not sure how to best solve this, or investigate. There are some new firmware features being developed for hrm, so I don’t want to touch any of my macros before those new features are out.
Ok, I played for a couple of hours on both the UHK60v2, and my new UHK80.
I never received any errors in Agent, but I did have a few stuck a & d keys with the UHK60 (not a lot though). Each time it was resolved by simply tapping a random key or two, with no crashes/reboots, etc.. The UHK80 didn’t have any issues at all for well over an hour of intense gaming. I left Zephyr logs running in Agent while I was gaming on the UHK80, and I didn’t see anything out of place.
This is super strange, since the last time I used the snap-tap macros (early August), the opposite was true. The old UHK80 used to hard lock very often with numerous output issues, but the UHK60v2 was rock solid.
IDK if this is due to the new UHK80, or a firmware upgrade (or maybe both).
@pcooke9 I think you and I had an odd experience with the early prototype UHK80. We probably have seen (and reported) a few problems that only existed on the prototypes, but never in the release product. I am currently waiting for my replacement; will definitely retest a number of things once I have the new one.
I decided to use this solution, as it resolved the issue as a dedicated solution and unloading the processing requirements from the UHK. I know that the UHK is super capable, but not sure if the integrated hardware is designed to run a macro with this complexity. I think that with the amount of rapid inputs from spamming left and right, the timing can get thrown off, which is when I get that `unmatched brace` error. I noticed this because in my example, the missing braces are on line 13 and 14, but other times it might be on line 63 and 64, or others. Anyway, thank for all the responses troubleshooting my issue.
Yeah, I guess I should’ve explained why I’m using a new UHK80 .
So to elaborate; when I first started having problems with the snap-tap macro, I was using the old prototype UHK80, which has since been replaced due to incompatibility with newer firmware. So, like Max pointed out, I can’t really be sure if the snap-tap issues would’ve been present on the newer models back then, because I can’t remember what FW I was using at the time.
I finally had the snap-tap macro get stuck a couple of times within a few hours of gameplay on the UHK80. One of the strafing keys gets stuck, and the “<->” LED text indicator stays on the OLED indefinitely (until I tap another key to resolve it). Still no brace errors on any of the UHKs, or anything out of the ordinary otherwise.
.