| |
Didi
Registered: Nov 2011
Posts: 485 |
Event id #2889 : Intro Creation Competition 2019
Preface: Please use this thread for questions, discussion and everything else concerning this competition.
Many people were asking about the competition being held this year. It turned out to be a good place to have it after the big X party each second year. But why not give it a try in between?
This time I decided to add a second category to the well known rules: 4kB intro! It is different to the 4kB intro category you know from demo parties. There the executable file has the limit of 4096 bytes and may allocate as much as you like during runtime. Rules here only allow to use 4kB overall for a different challenge. Please check the rules for more details. Result will show if that was a good idea.
Here you go...
Competition runs from November 4th, 2019, until January 5th, 2020. So you have a full 2 months to deliver your creations. This should be enough for an intro.
RULES for both categories:
Your intro entry...
- has to work on a plain stock C64 (PAL standard) without any extensions.
- has to be a one-part intro. Short fade-ins and fade-outs are OK.
- has to contain at least one Logo at whatever size you like.
- has to contain a changing or moving text message (e.g. scrolling text, different lines fading in & out, etc.)
- has to be interruptable any time by pressing SPACE-key (exception are short fade-in and fade-out).
- does not need to have exclusive graphics, charsets or music. But the code should be exclusive, so reuse of existing code with just exchanged graphics and music is not allowed.
- has not been publicly used before entering the competition.
- has to be handed in as executable format startable with RUN (.prg or embedded in .t64 or .d64).
Your 16kB intro...
- has a maximum RAM footprint of $4000 bytes at one block, at whatever location you like. Screen RAM counts as used memory. Exclusions are system addresses like VIC (inkl. Color RAM), SID, CIA, Stack, Zero-page, IRQ vectors. This means RAM besides chosen $4000 bytes area and exceptions has to be the same before and after running the intro. What happens during runtime is up to you.
- has to contain music (not just a humming sound, please).
- is linked to this competition as "C64 Demo" entry (sorry, no other fitting entry exists).
Your 4kB intro...
- has a maximum RAM footprint of $1000 bytes at one block, at whatever location you like. Screen RAM counts as used memory. Exclusions are system addresses like VIC (inkl. Color RAM), SID, CIA, Stack, Zero-page, IRQ vectors. This means RAM besides chosen $1000 bytes area and exceptions has to be the same before and after running the intro. What happens during runtime is up to you.
- does not have to contain any sound, but feel free to add some.
- is linked to this competition as "C64 4k Intro" entry.
You are allowed to enter maximum 3 entries per participant and category, so you are can enter 6 entries at best. Entries might be taken back from the compo until deadline. That means if you want to remove one of your works from the compo to make space for another entry from you, this can be done until deadline.
Deadline for entry submission is Sunday January 5th, 2020 at 23:59:59 (11:59:59 pm) CET.
Voting closes at Sunday January 12th, 2020 at 23:59:59 (11:59:59 pm) CET.
Voting platform is CSDb (with all disadvantages it may have), therefore entries have to be posted here.
Entries will be ranked by weighted average of CSDb votes. Entries with the same weighted average are ranked by their percentages of 10s, 9s, etc.
No prices to win, just the fame. May the best creation win! |
|
... 173 posts hidden. Click here to view all posts....
|
| |
Krill
Registered: Apr 2002
Posts: 2953 |
Take a look at Tiny Sid 2 C64 Music Competition for some inspiration, as did i when i made the player in music.s from Artefacts source code and Fanta proceeded to compose a tune in it. :) Player is heavily based on GRG's work in Plaster (thanks mate!) but probably bears little resemblance now. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Thanks for the hints! I think Plaster has already been used in an entry for the current compo.
I'll check the Tiny SID (2) compo entries, see what can be implemented/ignored while still having some proper sound.
By the way, there's a lot of trailing whitespace in the Artifacts source code, when using VIM, do this (in ~/.vimrc):
set list listchars=tab:>-,trail:~
Sorry, I'm a little pedantic at times =) |
| |
Krill
Registered: Apr 2002
Posts: 2953 |
Dude, that was made more than 13 years ago. Tell this to my younger self! :) (I've since switched OSes and editors, and use to have a keen eye on avoiding superfluous whitespace at line ends. :D) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Haha, well please do not look at my old code, I absolutely did not use CamelCase in C code (or asm) and such things. |
| |
0xDB
Registered: Aug 2015
Posts: 27 |
My 4096 and a few bytes intro is basically done...got rasterbars, scrolltext, some sprites, still need to add music and I already squeezed some code and data hidden into the screen, so I have 299 bytes left in my code segment, 36 in my data segment and 86 in ZP. Think I'm going to read up on SID programming. :] |
| |
Krill
Registered: Apr 2002
Posts: 2953 |
Quoting CompyxI'm working on a mini player for this, but it's been ~25 years since I wrote a player. I do have "Die Kunst der Fuge", so perhaps come clever reuse/alteration of melodies/themes will do the trick.
But I'll probably reuse some SID :( Oh, also https://codebase64.org/doku.php?id=base:256_bytes_tune_player =) |
| |
Golara
Account closed
Registered: Jan 2018
Posts: 212 |
If I use some KERNAL or BASIC function and it changes some of it's ram (that area after the stack) does that count as used memory ? |
| |
Didi
Registered: Nov 2011
Posts: 485 |
Sorry for the late reply:
You are allowed to use kernel routines and as you do not have control of what addresse they modify, I would not mind as they will not set any adresses to invalid values what custom code probably would to. |
| |
TheRyk
Registered: Mar 2009
Posts: 2203 |
been there, tried that. only problem is there are just few useful routines in ROMs and the most useful (KERNAL CLRSCR) fills ColRAM differently on older ROM revs. ATM I'm not desperate enough yet to seek through ROM listings *knocks on wood*.
of course some might use JSR $EA31 or better $EA81 to end IRQs |
| |
Krill
Registered: Apr 2002
Posts: 2953 |
I found the float routines extremely helpful here and there. Especially POLYX ($e043). =) |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | ... | 20 - Next |
