| |
Didi
Registered: Nov 2011
Posts: 486 |
4k intro compo?
I found myself coding quite a lot of small intros lately because many current releases to link them are rather small and we do not want to bloat them too much with a giant intro.
Anyone interested to join a challenge creating mini-intros? Different to the 4k category at demo parties 4k would not be the limit for the executable but for memory usage overall at one block. Rules would be similar to Event id #2757 : Intro Creation Competition 2018 just with a lower memory limit and without the requirement for music. |
|
... 17 posts hidden. Click here to view all posts....
|
| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
Hurrah for a new smaller category!
However, I'm puzzled as to the motivation for the working memory limit; surely if the idea is to pretend you're linking to a small release, there should be plenty of free space in high memory, and it's only the file size that needs to be small? Perhaps the compo just needs a different name, perhaps 4k RAM intro?
I'll watch this space with interest :) |
| |
Dwangi
Registered: Dec 2001
Posts: 130 |
Quote: @TMR: I am currently thinking about to add 4k as a second category to the usual 16k.
Multicompos is a good idea.
These 2 cathegories + demo of the year:) |
| |
Didi
Registered: Nov 2011
Posts: 486 |
It seems there is enough support for a 4k category. So stay tuned for the compo start. |
| |
DKT
Registered: Aug 2004
Posts: 99 |
Thumbs up! |
| |
Axis/Oxyron
Account closed
Registered: Apr 2007
Posts: 91 |
Sounds like fun. |
| |
Raistlin
Registered: Mar 2007
Posts: 659 |
Quote: Hurrah for a new smaller category!
However, I'm puzzled as to the motivation for the working memory limit; surely if the idea is to pretend you're linking to a small release, there should be plenty of free space in high memory, and it's only the file size that needs to be small? Perhaps the compo just needs a different name, perhaps 4k RAM intro?
I'll watch this space with interest :)
^^ that's exactly my argument.
But, yeah, fitting everything in 4k and sticking to the 4k is a different ball game. Needs more definition though:-
- presumably writing to VIC is ok (D000-DFFF)
- Zero page?
- can the stack be used? If so, how?
- etc..
Restricting it to 4k means the rules need to be better defined - rather than just saying "link this 4k release to your 4k intro". |
| |
Didi
Registered: Nov 2011
Posts: 486 |
Example from last year's 16k compo (modified):
Quote:- 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. |
| |
Pitcher
Registered: Aug 2006
Posts: 61 |
Yeah, why not, count me in |
| |
Jammer
Registered: Nov 2002
Posts: 1335 |
If I use bank 0 and want to modify ghostbyte, do I have to place everything at $3000-$3fff? |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Nope, just store the ghostbyte and restore on 'exit'. At least that is how I read the rules.
Quote: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. |
| Previous - 1 | 2 | 3 - Next |
