pouët.net

no he's not

He's integer.

Oh, and there was no breakpoint in 2002.

shadez may not know, that these many overlays just take 5.12kB and that the fire is the fastest (faked - half framed - but who can see that???) of this resolution ever on C=64. It was c0ded in three weeks in summer '02 and all overlays were hand-huffman-packed. Maybe some ppl should start hitting the freeze-key before judging hardcore-hand-code like this ...
It was just released as a demo, as those 5.12kB could not at all be crunched smaller - we added the good old 'Felony'-music and the endscreen to make it some kind of demo.
And 4th place 4 something that should never be released ... well ... hmmm ...

St0fF / NPL - the creator of this shit ;)

so basicly this is an unreleased 4k intro that takes up more than 4k and never attended breakpoint nor did it place 4th at any party? :)

RA5MUS! It got 4th Place in DemoCompetition because of the few bytes above 4k. And therefor not a bad result while challenging with real demos, I think. The only mistake I made is to announce it for Breakpoint 2002, there was no breakpoint. It belongs of course to MekkaSymposium. Damn. Added late at night on high level... ;)

Well, the MS2002 C64-Demo-Compo was definately not a glory part of C64 history. Don't forget that. And for my taste, it's too chuncky...

That's true, it was no challenge in 2002 but that's even not the fault of the ones who competed in. We could compete at Primary Star or Devotion to get 1st, don't we? ;) But we did never a demo just to win a compo. I just wanted to add the fact that a (meant to be) 4k has normally no chance at all in a democompo. Don't blame it, beat it.

this still looks like shit and is totally unimpressive.

Ok, I have no idea how those 4x4 overlays can be 5.12kB in size... Technically this not-so-4k wasn't very impressive...

fixed the party

oh, whoops, I misread and thought he meant the overlays take 5.12kB each... Well, doesn't make this intro any more impressive though...

well, and some ppl can only do code they already saw and reversely engineered. This is what really sucks - guess why npl never released and never will release a graham-scaler? Because we do code and some ppl can't think stuff like this up. And for the fire: dudes, before telling it ain't look cool, look at the code and try to understand - I doubt for some reason that any of you thumb-downers will be able to do it better ...
and not to forget: ninja can't see code, he only sees design - this thingy was about code tho - so as VisciD said: don't blame, beat!

Sorry, but why bother to look at the code if what's on the screen looks dull? And come on, you weren't able to fit a 4k-intro in 4k's, that says something about your "hardcore"-coding ;)

not really ... if you looked at the code you'd know - and hit dogs start barking - guess that goes for both of us ;)

Heh, no, I won't look at your code as I can see by what's on the screen that it's not worth watching

look, he's so hardcore, that his code won't even fit! NOW THAT'S FUCKING HARDCORE

The Parts were planned for something bigger than a 4k Intro. St0ff decided live on the party to do something for the 4k Compo out of the box, in 1.5 Days. He didn't manage it in time so he released it in the democompetion. There is no "not able" or "does not fit", there was just a deadline. I think some of you know what I mean. Try to do something last minute on a party with funny smoke in your brain. There is even a Picture after the Intro trying to explain the facts.I'm not in the mood to start any giggling after 2 years now... try to understand it or not. I remember the intro was below 4k without music and the decision was hard how to go on. Time was too short for a music which fits into memory, the code wasn't the problem, it was already below 4k. So we included any music and even a full Endpicture because if you fail 4k, you can fail full ;) The code is really something not reengineered but you can't see that on the first look. P.S. Britelight... there can be a difference between "nice to watch" and "good code", compare your fire at BP04, 2 year later, with (40*25) with the one from st0ff (60*47). It's at least 1.4 times faster in the case that your's is fullframe. But as mentioned before... that's old crap, childish behaviour and not worth the C64scene. Await more soon. ~8]

"ninja can't see code, he only sees design"

Hehe, if Darwin does not prove the straight opposite, I dunno what :)

Atleast my whole intro fit in 4k's with music and more than two effects ;)
And the "original" version supplied with this demo is 21 blocks without music, quite a bit more than 4k's, eh?
But anyway, I wasn't impressed with this intro and no matter how you claim the code is hardcore, I don't buy it...

why even bother trying to defend one ugly plasma and one ugly fire? and dont you usually watch the demo itself instead of the code, or have i totally misunderstood something?

well, I looked at the code of the fire, and there's nothing special about it. Except that it calcs only of the half of the pixels in one go if I guess right.

I am all for coder porn, but yet another ugly 4x4 plasma and fire doesnt makes me horny. It's not only should be hard coded, it should also look cool, sorry.

All excuses aside, this still sucks ass.

I think the whole story is far too long told for this small release ;). Just a word to britelight,there were 21 blocks before the party, out of the dusty diskbox. Fittet in 4k before deadline without musik as told. Now let's smile 'bout... we never wanted to make it better than it deserves, just read the whole story again and you'll notice.

Oswald: the tricks of the fire are:
1.) that this doesn't fit into mem if you completely hardcode it as speedcode
2.) that for the many calculations it has to do, we change the screen each frame and do not see any update-bugs, although it is calculated in two frames

Goddamnit this is good stuff!

Sorry, I don't see anything extraordinary in the fire effect and it doesn't even really look good. The plasma looks even worse. The messages are funny though :)