Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user Ysyry ! (Registered 2017-02-19) You are not logged in 
CSDb User Forums


Forums > CSDb Entries > Event id #2526 : Intro Creation Competition 2016
2016-11-01 16:20
Didi

Registered: Nov 2011
Posts: 234
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!
 
... 209 posts hidden. Click here to view all posts....
 
2017-01-04 00:20
Krill

Registered: Apr 2002
Posts: 809
Quoting Didi
Usually an intro will be linked infront of some other program, so it should leave the rest of the memory untouched for the other program.
No. As i said, the intro may touch anything it likes, move program data around and put display or other data anywhere it likes, AS LONG AS it restores the original program blob after it has run. And yes, i've done that with some of my intros.

And yes yes, being linked in front of other programs is the very definition of "intro" aka introduction.
2017-01-04 00:35
Scan

Registered: Dec 2015
Posts: 36
I interpreted the $4000 block rule as "$4000 consecutive bytes" just to be on the safe side. It's also easier for Didi to check whether an intro sticks to the rule(s). For that sole reason I've posted the output of the memory map of kick assembler as summary in my intro, to give the man some slack.

And to be honest, isn't it a tad late to complain about the rules when it's just 20 minutes past the deadline of the competition? You had a full 2 months of time to complain.
2017-01-04 00:49
Krill

Registered: Apr 2002
Posts: 809
I never intended to participate. I'm merely saying that such a rule is bonkers, because it doesn't make the slightest difference to the linked program and only limits what you can do in the intro.
2017-01-04 00:59
Cruzer

Registered: Dec 2001
Posts: 866
I actually like this limitation, since it means that you can't just do the usual FLI and speedcode tricks that are common in normal size-restricted categories, where it's only the file size that counts. I.e. it makes you think in new ways when you can only use 16K at runtime.
2017-01-04 01:03
Krill

Registered: Apr 2002
Posts: 809
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.
2017-01-04 01:04
ChristopherJam

Registered: Aug 2004
Posts: 509
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.
2017-01-04 01:04
Scan

Registered: Dec 2015
Posts: 36
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. ;)
2017-01-04 01:06
ChristopherJam

Registered: Aug 2004
Posts: 509
"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 :-/
2017-01-04 01:06
wertstahl

Registered: Apr 2012
Posts: 6
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
2017-01-04 01:11
wertstahl

Registered: Apr 2012
Posts: 6
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.
Previous - 1 | ... | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | ... | 23 - Next
RefreshSubscribe 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
Zyron/GeNos¤ProjecTary
Acidchild/Padua
v3to/Oxyron^PriorArt
The Dark Judge/Focus
Bob/Censor Design
Sith
Zamdee/Topaz Beerline
Hoild/Ultimate Newco..
gryf/Elysium
ccr/TNSP
Carrion/SHAPE
Guests online: 36
Top Demos
1 Uncensored  (9.7)
2 The Shores of Reflec..  (9.7)
3 Edge of Disgrace  (9.7)
4 Coma Light 13  (9.6)
5 Lunatico  (9.6)
6 Comaland 100%  (9.6)
7 Neon  (9.6)
8 Incoherent Nightmare  (9.5)
9 Wonderland XII  (9.5)
10 Comaland  (9.5)
Top onefile Demos
1 Globe 2016 [reu]  (9.6)
2 Dawnfall V1.1  (9.5)
3 Daah, Those Acid Pil..  (9.5)
4 Treu Love [reu]  (9.4)
5 Dawnfall  (9.3)
6 Tunnel Vision  (9.3)
7 One-Der  (9.2)
8 Goatbeard  (9.2)
9 Hardware Accelerated..  (9.2)
10 Safe VSP  (9.1)
Top Groups
1 Booze Design  (9.4)
2 Censor Design  (9.4)
3 Oxyron  (9.4)
4 Arsenic  (9.3)
5 Crest  (9.3)
Top Graphicians
1 Mirage  (9.8)
2 Carrion  (9.8)
3 Veto  (9.7)
4 Archmage  (9.7)
5 Pal  (9.7)

Home - Disclaimer
Copyright © No Name 2001-2017
Page generated in: 0.212 sec.