Now, @lovebyteparty New Talent Competition!
A personal highlight. Good luck to all those taking part, especially ##LovebyteTCC grads. And obvs, good luck with scoreboard placement, but that can be a bit arbitrary - participation and enjoyment of the art in itself is the real prize!
Since our son Emil was born last summer I did not have much time for personal creative practice, but during the Christmas holidays I had some fun getting into a virtual game console called TIC-80 thanks to #lovebytetcc.
So I did my first 256 byte demoscene production for the @lovebyteparty new-talent competition.
A huge THANK YOU to everyone who participated in (or supported, or spectacted) Tiny Code Chistmas! We warmly invite you to join the Lovebyte 2024 new talent compo.
One year ago (thanks photo memories!) I was noodling around with these guys.
I decided I could remove an eye for artistic and sizecode purposes, and mess around with the music seed. They're iconic for me, and still make me smile.
Anyone (including those who did #lovebytetcc) fancy showcasing in a competition?
Lovebyte got me started, and it's a big part of this wonderful hobby - find out how you can give it a go here... 🙂 https://graphics.social/@lovebyteparty/111801429921014077 #TIC80#demoscene#creativeCoding
A small retrospective piece on the fun had taking part in #lovebytetcc this year, with my attempts to learn #ocaml, and now I learned TCC was really functional programming all along :)
Tiny Code Christmas Day 12 - I decided to do something else.
Tried to do the voxeltree but couldn't figure out how to do it properly . #pico8
Instead of doing nothing I decided to make something else out of the things learned during tiny Christmas coding. Now I wait for tiny easter coding or similar and try to learn a little more pico-8 coding till then.
Thank you #lovebytetcc for the nice series of tiny Christmas coding videos!
Time for a 2D vector graphics entry I think. This is Tiny Code Christmas day 7 extra: a snowflake. It comes in at a neat 350 characters. I use a fair number of those on the colour gradient, but I really like the look of it. I am abusing the Flitter language appallingly in the code for this.
there is a whole scene of #mathart#mathsart out there in the fediverse, more oriented to mathematicians with a little bit of demoscene crossover! a nice thing to discover post-#lovebytetcc
My entry for day 10 extra of Tiny Code Challenge is a minimised version of something I wrote earlier this year for an upcoming interactive digital artwork and comes in at 468 characters. I could have got it under 400 if I'd gone for less complicated lighting, but the colour makes this for me. I originally had it zoomed in to hide the edges, but then decided that I enjoy the fuzzy outline more. It uses 3-octave simplex noise for the waves.
It's been lovely watching people play on the #LovebyteTCC hashtag... but double-lovely to see some folks' timelines getting consumed by the challenges. Wholesome creativity!
I hope some of you folks will be putting in for Lovebyte's newcomer competition/showcase in early Feb. It's a very fulfilling hobby and welcoming community to be involved with! 🌟
For @mdales then, Lovebyte Tiny Code Challenge day 11 using a minimised variant of code I wrote earlier in the year for a live gig. This is 8000 cube voxels varied in size with 3D noise. The code is <400 bytes again, which seems to be the general limit for an interesting program in Flitter (I actually deliberately designed the language to be verbose…).
And also for @mdales, Lovebyte Tiny Code Challenge day 11 extra using a minimised version of code from my live AV gig with @feralfive this year. For the original, these were stamped gold bars, but that would require an external model so I've switched to just using shiny obloids. I got this in at exactly 400 bytes but only by switching to 2-space block indentation.
Day 10 extra of #lovebytetcc in #ocaml - the prompt for this one was just "grass", and so I took yesterday's code, and repurposed it: the height of the sphere became the angle of the grass line, and colours just got mapped to another palette.
In OCaml learning I made the palette a proper ADT. I definitely feel the tension now between having my fantasy console library and the flexibility to be fully creative.
OK. Last one of these and then I really need to go make my dinner!
This is the Tiny Code Challenge day 12 extra. I couldn't resist doing the candy cane, though it took me a moment to figure out a neat solution. This uses 2400 squashed spheres and a mass of transformations to warp them into twisted worms. It was surprisingly satisfying to do and again comes in under 400 bytes!