That’s a good idea, I’ll keep that approach in mind, although I do worry that performance will tank as soon as the camera gets close to the character. And I 100% agree, I learn so much optimizing for lower end devices.

I haven’t yet, but that sounds like a pretty fun experiment that I’d like to try in the future. Let me know how it goes!

I started off using Uno R3, back whenever I was spoofing data rather than exchanging, and I reached the memory limit while debugging an issue I was having, and switched to the Mega. The sketch should work just fine on the Uno R3 though, as most of the data is stored in flash.

You already know what comes next. 😈

I use the Arduino Uno R3. I was under the impression that if an interrupt is attached and is set to CHANGE, it would only trigger if the voltage of rises or falls over 3V. Would it trigger even if the fluctuations are in 0.05-0.1V range?

I ended up working around the issue by using a boolean to keep track of the last state of the signal, but I will look into those options as well to avoid having to fix on the software side.

I set the interrupt to CHANGE, so it would trigger on rising and falling, but whenever the CLK signal was high, it sometimes triggered the function twice, which was causing issues in the data I was sending. I fixed it with a boolean, but not sure why that was needed.