| |
Didi
Registered: Nov 2011
Posts: 488 |
Event id #2526 : Intro Creation Competition 2016
Sorry for skipping this event last year, but life is life and I simply would not have had the time to host this event in a proper way.
So finally X 2016 is over and the big productions are out. So maybe you are in the mood for a smaller project.
Competition runs from November 1st, 2016, until January 3rd, 2017. So you have a full 2 months to deliver your creations. This should be enough for an intro.
Please use this thread for questions, discussion and everything else concerning this competition.
THE RULES (same as in 2014, worked very well):
- Has to work on a plain stock C64 (PAL standard) without any extensions.
- Has to be a one-part intro. 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 contain music (not just a humming sound, please).
- Maximum RAM usage is $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.
- Has to be interruptable any time by pressing SPACE-key (exception are fade-in and fade-out).
- Graphics, charsets and music do not need to be exclusive, but the code should be! So no reuse of existing code with just exchanged graphics and music.
- Intros may not have been used before entering the competition.
- Entries must be handed in as executable format startable with RUN (.prg or embedded in .t64 or .d64).
- Max. 3 entries per participant. 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 January 3rd, 2017 at 23:59:59 (11:59:59 pm) CET.
Voting closes at Sunday January 8th, 2017 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! |
|
... 274 posts hidden. Click here to view all posts....
|
| |
Krill
Registered: Apr 2002
Posts: 2982 |
But you CAN only use 16 KB at run-time, because the linked program is 48 KB no matter what. Just that there is exactly no reason to have those 16 KB all in one contiguous memory area. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
I'm with Cruzer on this one. Sure, the restriction's artificial (like everything else on this ancient platform), but that just makes for a new set of challenges.
I wanted a half screen of FLI for Scharf, so I had to write an offline allocator that would fit my tables in around the bits of VM that were actually in use, instead of my usual "graphics goes there, code+data goes here" approach. |
| |
Scan
Registered: Dec 2015
Posts: 111 |
I agree to that, for some effects proper alignment in various memory segments is required (thinkinh FPP here). And I agree, maybe the rules of memory usage could be stated clearer, but then again, most intro's so far followed the rule and the ones that went out of memory bounds were notified by Didi in time so they had a chance to correct their code.
Yet still, I don't see the reason why you should complain when you don't participate in the event.
That being said, I admire your work on your loader. ;) |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
"Just that there is exactly no reason to have those 16 KB all in one contiguous memory area."
well there is, but that reason is "it's the in the rules for the competition"
Speaking of, currently revising my entry because i didn't realise I wasn't allowed to depack to d800 :-/ |
| |
ws
Registered: Apr 2012
Posts: 251 |
Krill, what up? The limitations are the actual fun of it. I find them even pretty flexible because they're not saying like "well you got fixed mem up to $3fff". I find it quite reasonably set. And still, some managed to overstep :-) What i personally find far worse is the voting system. If it was me, i would make anonymous votes optional per production (set by the uploader/author). Hell if i get no public votes, what gives. But Trollvoting anonymously just to avoid revenge, thats just plain cowardish. :-D |
| |
ws
Registered: Apr 2012
Posts: 251 |
And: no one hinders anyone from making a competition where you have to include a very large compressed file that you have to restore and jump into, after pressing space. That would actually be alot more helpful, since i am not sure that i could jump back to a working basic, for instance without requiring more space. |
| |
Krill
Registered: Apr 2002
Posts: 2982 |
Ah, anonymous voting, another pet peeve of mine. :)
But still, the rules are stricter than for actual intros for actual games, with that weird contiguous memory usage without touching the program blob. And the only way to really enforce that is to run an emulator and check all memory writes for illegal access. How sensible. |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
Krill: You're right of course, except that it would require that all participants linked the same 48K blob, which would make it harder to do a nice collection of the entries without taking up 4 times as many d64's. And I still like the limitation of 16K in one continuous area, since it means that I'm more impressed when people do something like what ChristopherJam did. |
| |
Krill
Registered: Apr 2002
Posts: 2982 |
ChristopherJam: The only sensible artificial rule is limiting executable size, as in space on disk (or wire, if your prefer). Anything else is pretty much given by Word of God, i.e., the limitations of the machine. Just my 2 cents. :) |
| |
Krill
Registered: Apr 2002
Posts: 2982 |
Quoting Cruzerit would require that all participants linked the same 48K blob Why? 1. Intro starts 2. Intro moves arbitrary program parts to a backup area included in its 16K 3. Intro writes data to original location of backed up program parts 4. Intro runs 5. Space 6. Intro restores program by copying back data from backup area to original locations 7. Program is the same as before intro started 8. Intro runs program.
No reason to actually link anything, not to say the very same blob for every intro. |
| Previous - 1 | ... | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | ... | 29 - Next |
