| |
Released At :
X'2008
Achievements :
C64 Demo Competition at X'2008 : #1
User rating: | 9.6/10 (317 votes) See votestatistics | | 9.8/10 (134 votes) - Public votes only. |
Credits :
SIDs used in this release :
Download :
Look for downloads on external sites:
Pokefinder.org
Goof Info Submitted by DeeKay on 21 December 2008
There's this bug with the scrolling grey dots on the overlay at the top right in the Terminator part (just where it goes into the border) that was visible on any real c64 I've tried it on. And then there's a bit of flicker in the gfx in certain lines in the dot-plotter part on the 40th column on the very right, but that only seems to happen on old c64s, didn't have that on my new one!... | Goof Info Submitted by HCL on 2 November 2008
@GRG: That sounds rather possible, yes, i'm using $0200-02fd. I had a problem first that i wrote to $02fe-02ff (step-motor sequence something). That worked totally fine in Vice, but on real 1541.. Naaah :P. | Goof Info Submitted by 6R6 on 2 November 2008
Is it possible the 1571 bugs because the loader is ovewriting the 1571 irq vectors located at $02a9/$02aa in the drive. ?
| Goof Info Submitted by Mr. Mouse on 2 November 2008 Goof Info Submitted by assiduous on 31 October 2008
verifying with an emulator is a contradiction only if the results dont match a real machine that is emulated. but then again i think we can live with EoD flickering in this part on all C64Cs ;) | Goof Info Submitted by HCL on 31 October 2008
I checked my c128 has a 8563R9 (VDC) and a 8566R3 (VIC).. well, according to the number is should be newer than the 8565, but who knows? Don't know what my "breadbox"-c64 has, but probably 6569 then, since it doesn't show the bug either..
I have no intentions to fix that "bug" since i have no easy way of verifying it. Verifying with an emulator is like a contradiction.
So there you all go, another feature ;). | Goof Info Submitted by assiduous on 29 October 2008
@HCL: hint- the new VIC. Hoxs64 emulates the 8565 and yes its much more advanced in reproducing numerous internal quirks as seen on a C64C(except the infamous grey dot). the glitch in EoD was verified to be stable down to a single pixel(it was looked up frame by frame on the C64) and reproducible on 3 C64C machines i have tested on so a faulty chip or a rare occurence of the bug are out of the question. | Goof Info Submitted by Clarence on 29 October 2008
Running the demo note on my c128dcr freezes so badly, even the video signal is going blank. Seems like the note is writing to the test bit of the c128. The same d64 runs fine in vice c64 emu though... Strange. | Goof Info Submitted by HCL on 29 October 2008
@assiduous: Yepp, that's the bug i saw on the compo-machine. I went home, tried it on both my c64 and my c128, and there was (is still) no bug. I tried it on WVL's computer at X just before the compo -> no bug. So, this is truly some fishy shit here.. Don't just do the mis-assumption that Hox64 is more accurate because of this. The bug seems to be visible only on *certain* machines. | Goof Info Submitted by assiduous on 29 October 2008 Goof Info Submitted by Jammer on 29 October 2008
told ya! :P always listen to the elders :P | Goof Info Submitted by null on 29 October 2008
ok jailbird, if you say so, I believe you... still can't help but think that it's not supposed to be like that, though.. :/ | Goof Info Submitted by cavey on 29 October 2008
Actually, knoeki, if you look very closely, you can see the three parts shifted to the right by 1 'pixel' at least (the top part is slightly more to the right than the center part, and the center part is obviously not centered with respect to the lower part :P)
Verdict: intentional. | Goof Info Submitted by jailbird on 29 October 2008
Knoeki: well we had this idea about planting in obvious bugs into the demo so people would post screendumps (yeah) of EoD while talking about it, thus making the shit even more popular. Seems our plan is working quite fine. *evil laughter*
No really man, it's definitely intentional (and I'm the one to blame for making it look like a bug, sorry). :) | Goof Info Submitted by Frantic on 29 October 2008
I can assure you that this "misalignment" is not a bug. :) What proof do I have? I don't need any, because I am certain. ;) | Goof Info Submitted by grasstust on 29 October 2008
I think the stone looks cool, and it doesn't look like a misalignment; the stone is broken, and has been pushed to the side. If it would be more to the left the design would have looked worse because then the stones wouldn't have been aligned to the far right, looking very weird. | Goof Info Submitted by TDJ on 29 October 2008
@Style: did you try by changing the disk before running? That worked for me .. | Goof Info Submitted by null on 29 October 2008
ksubi: I've seen the demo about 10 times now.. sorry, to me it looks like a bug still, but whatever... I'll wait for a reply from HCL ( PM'd him yesterday.. ) | Goof Info Submitted by Style on 29 October 2008
Doesnt work on my c128/1571 combo. Fails at "insert disk 1 side a", in that once you put the disk in it just sits there........ | Goof Info Submitted by Ksubi on 29 October 2008
Knoeki: its meant to look as if its shifted, out of alignment is the design. Watch the part again :-) | Goof Info Submitted by Oswald on 29 October 2008
another nitpicking: there's a rasterbug on the left side of the 1st chessboard effect, both on top&bottom... | Goof Info Submitted by null on 29 October 2008
don't blame rambones for that. I was the one who came up for it, and sorry to say, but I can't look at it as broken stones, only as "why the fuck did they put that 3 pixels too far to the right?!"
this miss-alignment has nothing to do with the broken stone effect if you ask me...
| Goof Info Submitted by Jammer on 29 October 2008
rambones >> look harder. it's supposed to be that way - like a broken stone. what is more, it's broken i two places :P | Goof Info Submitted by SIDWAVE on 29 October 2008
On the screen with the plotter heart: the lower right gfx is different/not aligned to the part it connects to.. | Goof Info Submitted by Mr. Mouse on 29 October 2008
I had it random crash on me twice. Hmm... | Goof Info Submitted by Steppe on 29 October 2008
Roger that, doesn't seem to like the 1571. | Goof Info Submitted by Shaun_B aka C02 on 29 October 2008
Won't seem to work on the built-in 1571 on a German-made Commodore 128D-Cr. | Goof Info Submitted by HCL on 28 October 2008
Three dots is just a bloody waste of memory in cyber space. Everyone knows that two dots is not the same as one, so why use three?
Goof on the turn disk shit.. there's something fishy with the flip-disk routine, it sometimes seem to fail(!). I did some updates on the loader, so i might have left a bug there. | Goof Info Submitted by grasstust on 28 October 2008
In the zoomscroller, most of the sentences end with "..". This is grammatically incorrect as you can only write one or three dots, never two. Lots of dots at the end of something can be considered "slang", but two is bad form. Although, after seeing this demo, I'd be tempted to say we should make two the new standard! :) | Goof Info Submitted by Dane on 26 October 2008
There are a couple of music glitches during transitions between different parts. For a more seamless version of the music, have a listen to the soundtrack file on disk 0. |
|
|
|
| Search CSDb |
| Navigate | |
|
| Detailed Info | |
|
| Fun Stuff | |
|
| Forum | |
|
| Info on other sites | |
|
| Support CSDb | |
|
| |
|