[CSDb] - User Forums - Event id #3140 : Intro Creation Compo 2021

You are not logged in - nap

CSDb User Forums

Forums > CSDb Entries > Event id #3140 : Intro Creation Compo 2021

2021-12-04 18:42

Richard

Registered: Dec 2001
Posts: 619

Event id #3140 : Intro Creation Compo 2021

I am very happy to announce that The annual Intro Creation Compo is here once again. There will be an entry to kick off the competition from me some time later on this or next week.

Didi currently has no time, and has allowed me to step in as host for this year's competition.

The competition runs from December 4th, 2021, until January 31st, 2021. So you have just under 2 months to deliver your creations. This should be enough for an intro.

RULES for both categories: (Same as last year's compo)
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 the 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 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 31st January 2022 at 00:00:00 GMT+0 (UK).
Voting closes 28 February 2022 at 00:00:00 GMT+0 (UK)
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 prizes to win, all just for fun, and to share around the scene.

Have loads of fun.

PS: Please do not lock your entries on submission. This is because the problems I had with the CSDB Fun Compo 2021 when setting the results for each entry.

... 66 posts hidden. Click here to view all posts....

2022-10-05 10:18

Dwangi

Registered: Dec 2001
Posts: 129

I would like to see a DOTY 2022/2023 compo instead of ICC this year (or next year).
But this idea might be of self-interest.
I suck at putting stuff into 16K memory blocks :)

2022-10-05 19:55

Richard

Registered: Dec 2001
Posts: 619

Don't worry. I won't be hosting ICC 2022 this year. I only stepped in for Didi ;) - Too busy.

2022-10-06 07:33

ChristopherJam

Registered: Aug 2004
Posts: 1382

Getting in early with a request that ICC 2022 have a category that better reflects actual intro restrictions - whatever the size restriction on disk, demo must load to start of basic, then not trample any ram between end-of-load and $d000 unless it restores it on exit.

Eg, a 2k category that loads from 0801 to 0fff inclusive, then is free to use 0000-0fff and d000-ffff, leaving 50k for an appended payload that can be loaded with any fastload that can handle files up to the usual 51199 byte limit.

2022-10-06 08:19

Oswald

Registered: Apr 2002
Posts: 5031

not not trampling ram between end of load and d000 is unrealistic, as we all know game is crunched then intro is crunched with the game, so the first thing every intro does is trampling that ram while decrunching it so it is runable.

a typical intro would be something like

$0800-$1000 logo font
$1000-$2000 msx
$2000-$2800 scroller font
$2800-30000 code, text

$2800-$3000 bytes must be enough for everyone :) if we are more to see intros than single demo parts.

2022-10-06 09:11

iAN CooG

Registered: May 2002
Posts: 3138

@CJam: <$d000 is a restriction only for the final linked & crunched program. Once unpacked, an intro should not touch any RAM from end of intro to $ffff, to allow larger programs. The more RAM an intro clutters, the shorter a linked cracked game can be.

Also I don't understand what you mean with "that can be loaded with any fastload", an intro shouldn't load anything with any fastload, everything must be in memory, else there wouldn't be any memory restrictions =)

2022-10-06 09:11

ChristopherJam

Registered: Aug 2004
Posts: 1382

OK, so, then modify that to "once the demo is uncrunched, don't touch RAM from X to $d000" where X is the start of where the once-crunched game goes. X is $3000 in your example, but I'd love to see what people can do with lower ceilings, but not the usual 'don't touch RAM outside a 4k window' rule.

I get that most games will compress to well under 40kb, but presumably there was the occasional exception? Particularly as 20th century crunchers didn't have ratios as good as are available now.

2022-10-06 09:18

ChristopherJam

Registered: Aug 2004
Posts: 1382

Quoting iAN CooG

@CJam: <$d000 is a restriction only for the final linked & crunched program. Once unpacked, an intro should not touch any RAM from end of intro to $ffff, to allow larger programs. The more RAM an intro clutters, the shorter a linked cracked game can be.

Ok, yes this. I forgot that the decrunch before the intro starts can itself push the crunched game past $d000.

Revised rule: intro cannot touch any RAM above X aside from interrupt vectors, IO, and color RAM. But I'd love to see a couple of different values of X to allow for extra large games, or cracks that show docs or other extras before decrunching the game itself. Oswald suggested $3000, but $2000 or $1800 would be more interesting IMO

Quote:

Also I don't understand what you mean with "that can be loaded with any fastload", an intro shouldn't load anything with any fastload, everything must be in memory, else there wouldn't be any memory restrictions =)

Oh I just meant that the final linked and crunched program should be loadable with any fastload, not that the intro should be doing any loading.

2022-10-06 09:22

iAN CooG

Registered: May 2002
Posts: 3138

The better way to link and crunch was always to link the UNPACKED game if it fits, or if it doesn't, only charpack it (rle) so there will be only a final crunch that gets smaller than having a payload already crunched, and it also unpacks faster. This would lead to needing more free RAM, hence needing also $d000-ffff occupied by the payload.

This is probably not anymore true with modern cross crunchers that don't get worse crunch results when you recrunch already crunched files (exomizer 1.x for example still had this problem, solved in 2.x with better handling of literal sequences) but it's still an habit by the oldtimers to avoid having to crunch the payload and then crunch again the linked intro+payload.

2022-10-06 09:43

Krill

Registered: Apr 2002
Posts: 2855

Not the first to suggest this, but...

Just have differently-sized dummy payloads made of random bitsalad, that can be checked after intro with binary compare, and will be replaced with secret bitsalad and checked again. =)

2022-10-06 09:49

ChristopherJam

Registered: Aug 2004
Posts: 1382

Ah, but how do you replace the bitsalad with a different bitsalad while still maintaining the old school workflow of the payload getting crunched along with the intro?

I am once again forced to conclude that Groepaz Is Right - compo should just specify a nominal payload, and everyone gets to use the same one.

Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 - Next

Refresh

Subscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search for in
All times are CET.

Search CSDb

Advanced

Users Online

MaD ][/Starship
psych
Dr. Doom/RAD
MAT64
taper/ΤRIΛD
void256
Angel of Death/Wiseg..
Guests online: 114

Top Demos

1 Next Level  (9.7)
2 Mojo  (9.7)
3 13:37  (9.7)
4 Coma Light 13  (9.7)
5 Edge of Disgrace  (9.7)
6 Aliens in Wonderland  (9.6)
7 Comaland 100%  (9.6)
8 Uncensored  (9.6)
9 No Bounds  (9.6)
10 Wonderland XIV  (9.6)

Top onefile Demos

1 Layers  (9.6)
2 Cubic Dream  (9.6)
3 Party Elk 2  (9.6)
4 Copper Booze  (9.6)
5 TRSAC, Gabber & Pebe..  (9.5)
6 Rainbow Connection  (9.5)
7 Dawnfall V1.1  (9.5)
8 It's More Fun to Com..  (9.5)
9 Daah, Those Acid Pil..  (9.5)
10 Birth of a Flower  (9.5)

Top Groups

1 Nostalgia  (9.4)
2 Oxyron  (9.3)
3 Booze Design  (9.3)
4 Censor Design  (9.3)
5 SHAPE  (9.3)

Top Original Suppliers

1 Black Beard  (9.7)
2 Derbyshire Ram  (9.5)
3 hedning  (9.2)
4 Baracuda  (9.1)
5 Jazzcat  (8.6)

Page generated in: 0.046 sec.