pouët.net

Go to bottom
Simpletro by Flood (c64/.fr)
screenshot added by stf on 2013-09-24 17:29:35
platform :
type :
release date : september 2013
  • rulez 8
  • is ok 5
  • sucks 1
popularity : 0%
 0%
  • rulez 0.50
alltime top: #15988
added on the 2013-09-24 17:29:35 by stf stf

popularity helper

increase the popularity of this prod by spreading this URL:

or via: facebook twitter pinterest tumblr

comments

:|
sucks added on the 2013-09-24 18:39:33 by CHEF-KOCH CHEF-KOCH
Quite OK for a firstie!
added on the 2013-09-24 18:54:07 by StingRay StingRay
Cool :)
rulez added on the 2013-09-24 19:38:52 by Buckethead Buckethead
+1 for the beginner´s effort.
-1 for the fact that you´re lucky that it works.

you have an idle loop jmp c0c1 at c0c1 but you never reach it.

infact, i really wonder where your idle loop is going after all.

since after the cli, you´re normally in the idle loop. but you continue straight into the interrupt routines (see c055 --> this jsr returns (possibly just an init) and then continues into the irq routine!)

you are lucky that somehow the idle strain (the line of operation, that you interrupt by your interrupts) seemingly never reaches your jmp $ea7e!
because else you would end up with a nice crash.

what i find really interesting is how it can get lost. the idle loop must be stuck somewhere in your interrupt routines which is then constantly interrupted by the irq and just just reaches a dead end.

to see what i mean, write in line c055 JMP $c132
ask yourself: where does the rts go, that then returns from $c132?
--> that is your idle loop.
added on the 2013-09-24 22:05:56 by wertstahl wertstahl
and you may ask your self...why does this work? And you may tell yourself...

I'm jealous. I wish I could even have an idle loop at C055.

SYS 8675309
rulez added on the 2013-09-24 22:32:23 by tonyrocks tonyrocks
Werstahl : Perhaps it works because the real main loop is the IRQ (who do directly the raster splits and launch every routines in it) ? I don't know if i'm lucky or if i am an idiot who found a bright idea, i don't code for a long time and for a simple intro like this one (and another one i did for another group that will be released soon) i did that. I tried to kill the main loop on this program and it works well too. This loop is useless... I'm a newbie, i saw in all sources i studied a main loop, i put a main loop. In all case, thanks for this information, i'll try to investigate to see what i'm doing wrong (or right :D ).
added on the 2013-09-24 22:55:09 by stf stf
don´t get me wrong, i intended to be encouraging. you can actually use the the idle/main loop to do alot of things that are not time critical and usually you would interrupt whatever the main loop is doing with things that need to happen at a certain time. therefore irqs.
if you have found many productions using an useless main loop, you are right: thats not an optimal way.
i am very interested in what you come up with, next :-)
added on the 2013-09-24 23:03:40 by wertstahl wertstahl
no offence taken, seriously. Your comment was really instructive. I just tried to answer with a bit of humor, but i'm french and the world hates us when we try to be funny ;)
added on the 2013-09-24 23:13:29 by stf stf
:)
rulez added on the 2013-09-25 09:19:39 by mermaid mermaid
I don't usually do encouraging first-prod thumb-ups,
but when I do it's because the prod pleased me and its french creator didn't go apeshit from the comments in the pouet-thread! :D
rulez added on the 2013-09-25 09:36:36 by Korvkiosken Korvkiosken
Nice and clean.
rulez added on the 2013-09-25 10:01:38 by raizor raizor
hahahaha what slummy said
rulez added on the 2013-09-25 10:39:51 by ferris ferris
yeah simple but cute, thumb up for doing demo on C64 as first prod!
rulez added on the 2013-09-25 20:05:10 by rez rez
this code is fucked up on so many levels, that I have no idea how you have managed to get it even to work.

- you set up your irq vector to the start of your code instead of pointing it to the irq routine, thus every frame at rasterline $58 your code restarts from the very beginning (answer why main loop never crashes on an RTI caused by invalid return address)
- "main" "thread" goes right into the irq routine instead of idling on a jmp *
- Your irq fires at rasterline $58, then it busy waits for $100 and then for $5c, in the meanwhile passing the vertical blank, including the points where it should change border colors, instead of busy waiting... (starting at $58 -> waiting for $100, then you should miss colorchange at $5c)

maybe its that while your '"raster"' '"irq"' runs, its possibly re-interrupted, and you somehow get VERRY lucky and get out of the -busy-wait-self-interrupting-irq-also-main-loop- AND- init routine - fucked up diarrhera bullshit mess correctly.
added on the 2013-09-26 14:06:17 by Oswald Oswald
guess you mixed up your shit, because $58 seems to be a good LObyte value for your IRQ entry point, and you wanted your irq start at rline $00, but it didnt so you busy waited for $00?


consider lda blah sta bleh style instead of ldx ldy lda stx sty sta.
added on the 2013-09-26 14:11:54 by Oswald Oswald
and insert jmp * after cli, if you dont want to do anything in the "main", also use inc / dec d020 so you can clearly see where are your raster irqs happening.
added on the 2013-09-26 14:16:21 by Oswald Oswald
It seems i 'm a very lucky MF :D
added on the 2013-09-26 14:42:38 by stf stf
For a firstro, clean little try. The music is really good and the design is ok. As I am not a C64 coder, I can't find in your prod weird bugs, sorry :-).
rulez added on the 2013-11-07 20:55:54 by tometjerry tometjerry
Clean for the firstie.
added on the 2015-06-09 11:06:28 by sim sim

submit changes

if this prod is a fake, some info is false or the download link is broken,

do not post about it in the comments, it will get lost.

instead, click here !

[previous edits]

add a comment

Go to top