u/Jazzlike_Cod_8001

▲ 52 r/badapple+1 crossposts

Bad Apple but in Desmos

This has been done before, but previous showcases of Bad Apple in Desmos were either not in real-time, did not include audio, or were very pixelated. Here, it's in real-time, without any external image storage sites, and of decent quality instead of being very pixelated.

Find a link to the graph here: https://www.desmos.com/calculator/xo4rl3tbyb

u/Jazzlike_Cod_8001 — 1 day ago
▲ 12 r/desmos

2,373,341 notes play "Faded" by Alan Walker in Desmos

So one thing led to another, and I decided to test the limitations of Desmos itself. ~2.4 Million Data points is mind boggling for any web-based application, let alone Desmos, and perhaps 192 concurrent tones may have actually been overkill.

Once I remake the source code for the frequency-gain extraction (it tragically got lost), I'll get that published as well (along with lower-resolution versions). But for now, here's the graph link (don't expect it to run that fast):

https://www.desmos.com/calculator/r6mix4kj7f

u/Jazzlike_Cod_8001 — 1 month ago
▲ 86 r/desmos+1 crossposts

Limbo Keys but there's 200 of them, and it's in Desmos.

So I wondered what Limbo would look like if it weren't constrained to 4 rows and 2 columns. I thought this would be easy, but little did I know...

I tried to match it up as closely as possible to the original Limbo ending, but I had to make some assumptions about what the possible shuffles were. The psuedotranspositions in particular were not so straightforward to derive (the one where the keys move diagonally).

Note that this is coming to Reddit (here!) before YouTube (assuming moderation is reasonably fast), so consider this to be a first look!

Link to graph: https://www.desmos.com/calculator/viixjsbwcg

  • Some strange things do happen when you try to push for a super high number of keys, but it will do its best to render it.
  • On abnormal screen resolutions, it may not render as well (or properly). It looks fine on a 1920x1080 monitor (and 2560x1600 display), but don't expect it to look decent on a strange resolution/aspect ratio.
  • Currently assumes the entire shuffle sequence is 8 seconds (which is what I timed the original to be), but with a bit of math I'm sure you could generalize that too.
  • The ending transitions are kind of hardcoded, but they get the job done.

Playable real-time version hopefully coming soon

u/Jazzlike_Cod_8001 — 3 months ago