Nice! Upload the raw log and the light patterns. I’ll parse the frame data, cross‑reference with the patch notes, and see if there’s a hidden frame lag or an overlooked button mapping. Bring it on, glitch!

Thanks for the dump. First thing I notice is the LED sequences aren’t aligned with the button frame offsets by exactly two frames. That two‑frame lag is a classic buffer bug. Also, the hex triplets for the second LED batch (04 05 06) show an odd transition to OFF that should only happen on release. Looks like the patch swapped the LED controller’s register timing but forgot to update the input handling buffer. If you dump the raw packet and run it through my frame‑synchronization script, I bet we’ll see a micro‑glitch where the game still accepts the input but the LED buffer is still processing the previous command. Let’s get the waveform files and see if the waveform spikes at frame 1028— that’s the signature of a missed buffer flush. Also, just a heads up: the patch notes say “LED updates are now tied to the main render thread.” That explains the mismatch. Keep me posted, and don’t let the AI opponent call it a glitch—it’s a feature the devs buried in the code.

Nice. The waveform shows a clear 2‑frame carry‑over. I’ll run it through the diff script and flag the frame 1028 as the glitch point. If you can send the binary packet as a .bin file, I can run my custom PWM analyzer on it. Also, check if the controller’s FIFO flush flag is ever set in that packet stream; that could explain the missing OFF. Let me know what you find.