Sinclair ZX80 / ZX81 / Z88 Forums

Thanks to Shaun B I started BREAKOUT.

My thought about BREAKOUT. Why is it called BREAKOUT when you never break out.

So my version will be where you break through a wall and get bonus for remaining bricks.

Working on displayroutine right now.

That's a neat twist. The 'reaction' break-out that I spoke about, I think I'll give that a go.

Thanks,

Shaun.

This will take some calculation to fit it all in 207 tstates for all linepossibilities and display timing at same moment.

1) is there a ball
2) is there a bat
3) display bricks

adjust pointers for next brick
test on end of screen

All in 207 tstates.

It looks nothing, but it is a great first step. Especially the timing was hard to get in 207 Tstates.

The display of bat (only 2 pixels in size now) and the bricks (graphics still to be made) is working.
There is a test for the ball already, but the screen is not visible yet.
So next step: add the ball.

A bit altered to make the balldisplay fit 207 Tstates.

Calculation is now ok, next is coding the balldisplay.

Yes, ballscreen now added.

This is a selfmade display.
Next thing:
Screen is built by the game
Also to add: top and bottom bounce line.

You see up to 4 lines in a brick. Each hit will take of 1 line until break through..

Amazing - good work Dr!

dr beep wrote: ↑Thu Aug 31, 2017 10:42 pm Also to add: top and bottom bounce line.

Hi Johan, is it possible to invert the border instead of adding bounce lines?
Might save some bytes?

Paul,

It is not possible.

You could also invert the display.
However over the screen code is run and run code will always display as normal.

Still 2 lines added to the screen will cost about 40 bytes and I still have about 550 bytes free.

Now it is time to code the game....
ATM 435 bytes free, but when I move the screen to another location I will get app 100 bytes free.