| |
Didi
Registered: Nov 2011
Posts: 479 |
Event id #2757 : Intro Creation Competition 2018
Preface: Please use this thread for questions, discussion and everything else concerning this competition.
After ChristopherJam had the chance to run a similar compo last year, this year I am back with the known ruleset, with only slight change.
Runnning the competition after X party turned out to be a great timeframe, so I stay there.
Competition runs from November 5th, 2018, until January 6th, 2019. So you have a full 2 months to deliver your creations. This should be enough for an intro.
THE RULES:
Your intro...
- 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 contain music (not just a humming sound, please).
- 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 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).
Maximum 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 Sunday January 6th, 2019 at 23:59:59 (11:59:59 pm) CET.
Voting closes at Sunday January 13th, 2019 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! |
|
... 155 posts hidden. Click here to view all posts....
|
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
What kind of gobbledygook is extended zeropage? |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: What kind of gobbledygook is extended zeropage?
Just a crap naming convention used by some references when talking about the KERNEL variable space, like: http://unusedino.de/ec64/technical/aay/c64/zpmain.htm |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Hmm, i use to refer to that as LOWMEM, which would be anything above zeropage but within hardware stack ($0100..$01ff) and below screen RAM ($0200..$03ff).
Thought i've seen that in some reference documents as well, but not sure now. :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11110 |
i have seen it often in books and articles. 64er used that term a lot.
hey, it makes more sense than IFFL afterall :) |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1378 |
Question about the rules:
If the decruncher I use installs itself in the stack, can the demo rely on it being still being present there when it starts up?
(I may need to decrunch a bit more after doing SID detection and deciding which digi table to discard). |
| |
Didi
Registered: Nov 2011
Posts: 479 |
No. You cannot rely on leftover code or addresses from the decruncher. Assume a normal reset being done before running your intro. So everything your intro needs to run should be part of it.
I remember an intro from a previous compo which changed parts of itself after initialization. I presume it was also done by depacking. It was one from Cruzer if I remember correctly. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1378 |
OK, so we're just to assume the 16k block has been loaded and SYSed into.
I remember I got into trouble with my first submission of Scharf for ICC 2016 by using the decruncher to initialize color memory. I'll learn my lesson one of these days :) |
| |
Digger
Registered: Mar 2005
Posts: 421 |
Does someone have a PRESS SPACE code handy (without using Kernal's $ffe4)? |
| |
Scan
Registered: Dec 2015
Posts: 110 |
Quoting DiggerDoes someone have a PRESS SPACE code handy (without using Kernal's $ffe4)?
I have this in an irq:
lda #%01111111
sta $dc00
lda $dc01
and #%00010000
bne !+
inc exit
!:
And this as exit routine in the code outside irq:
!:
.label exit = * + 1
lda #$00
beq !-
sei
lda #$37
sta $01
jmp 64738
Pretty crummy, but it does the job for me ;) |
| |
Zirias
Registered: Jan 2014
Posts: 48 |
Well, this will detect J#1 fire as well, just like the original kernal code... but apart from that, what's "crummy"? Just straight-forward code I'd say. |
| Previous - 1 | ... | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | ... | 17 - Next |
