Whoops I saw @marcan42's Bad Apple on oscope video get retweeted and challenged myself to see how long it would take me to get Bad Apple working on GBA.
Answer: 2 hours.
-
Show this thread
-
It's twice the size and half the audio rate as one that's already floating around though so I'm not sure there's any point to me releasing it heh
3 replies 0 retweets 4 likesShow this thread -
Replying to @endrift
Hector Martin Retweeted Hector Martin
I'm sure it's higher FPS than this one thoughhttps://twitter.com/marcan42/status/682239520314667008 …
Hector Martin added,
2 replies 0 retweets 5 likes -
lol pretty sure that looks worse than when I did it (unfortunately I don't remember exactly which year and I don't have the video on hand right now)
1 reply 0 retweets 1 like -
I don't think you could do much better with the hardware they had. The screen was divided into thirds, and you'll notice each third is pretty close to refreshing 100% of the time.
2 replies 0 retweets 1 like -
e-ink version when
1 reply 0 retweets 3 likes -
Of *course* someone already did it. https://www.youtube.com/watch?v=KS8M_MV3Xhw&vl=en … (cheating with 10x speedup though). Cute ghosting artifacts though!
1 reply 0 retweets 3 likes -
I just decided I'm doing this on a MicroView and what is this coincidence. 64px * 48px / 8 bits per byte * 30 fps * 10 bits per char = 115200 baud.
1 reply 0 retweets 0 likes
Hector Martin Retweeted Hector Martin
There. Took about 1 hour, most of which was fighting to recompile avr-gcc with C++ support (which apparently breaks with hardening USE flags) to make the Arduino IDE work. Actual firmware is just 10 lines of code to pump data from serial to the screen...https://twitter.com/marcan42/status/1043063673080569856 …
Hector Martin added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.