5 replies to this topic

[yuppicide]

Sorry.. edited post. I got it to work. I wasn't indenting my if then statement for collision.

Edited by yuppicide, Tue Jul 29, 2008 2:18 PM.

[yuppicide]

Alright since I've opened this post up I actually do need help with collision..

I can't figure out how to get it to work.

I have tried several things with no luck.

One of the things I've tried

 if collision(playfield,player0) then reboot

I put this right after my joystick routine. This causes garbled image on the screen and the game just sits there.

I've also tried putting t=1 in the beginning of my game. Then I wrote

 if collision(playfield,player0) then t=t-1

 if t=0 then reboot

Same garbled output.

The next thing I've tried is

if collision(playfield,player0) then goto deaths

then later on

deaths
 reboot

All three freeze game with same garbled output. What am I doing wrong?

Attached Files

•  test2.bas   2.88K   21 downloads

Edited by yuppicide, Tue Jul 29, 2008 2:19 PM.

[Random Terrain]

Can you post your .bas file?

Oops. I see you just did that.

Edited by Random Terrain, Tue Jul 29, 2008 2:22 PM.

[Random Terrain]

After playing around with your code, I get the same result. It seems Superchip games don't like reboot. I guess you'll have to reboot the way we used to before we had reboot, where you jump to the beginning of the program with a goto and start the game over that way.

I haven't used Superchip RAM or gone over 4k so far, so I don't know a whole lot about this area yet.

[batari]

The problem is that Superchip RAM is not cleared at boot, and you'll get a screen of random data if you do a drawscreen before you do any playfield drawing commands. What seems to be happening is you're constantly rebooting. Try a pfclear at the beginning of the code or make sure one of your playfield: commands gets executed before the first drawscreen.

[yuppicide]

Thanks guys that PFCLEAR did the trick. Things are coming along nicely and I'm learning some things good.