Working on a new 1K hires game

[dr beep]

I am working on a new 1K game: PONG.

This classic needs a 1K hires version!
My first idea wasn't working, but my alternative approach seems to make a 17*8 by 192 pixels screen possible.

The game will allow 2 players with their bats moving up and down while the ball will move over the screen between the bats.

The classical battle between small memory and 207 Tstates for a line is really addictive!

This new approach will also make a game of Western Duel possible where 2 bullets will be fired upon 2 cowboys

[sirmorris]

Wow! I'm looking forward to this! I love seeing what the machine can be made to do.

[dr beep]

I am working on a new 1K game: PONG.

This classic needs a 1K hires version!
My first idea wasn't working, but my alternative approach seems to make a 17*8 by 192 pixels screen possible.

The game will allow 2 players with their bats moving up and down while the ball will move over the screen between the bats.

The classical battle between small memory and 207 Tstates for a line is really addictive!

This new approach will also make a game of Western Duel possible where 2 bullets will be fired upon 2 cowboys

I altered the code for the display of the ball making it a 168 * 192 pixels screen (21 columns not 17, so 4x4 T States won in the code).
By coding the batdisplay it came clear that I needed exactly that amount of time (21x4 T States) to determine if the right bat needed to be displayed. So a 17 columnscreen wouldn't have fit the batdisplay.

[dr beep]

Small alteration made go back to 19 columns.
Ball display is ok, bat display still needs a perfect timing.

[dr beep]

Ball display ok and bat display ok and back to 21 columns.

First demo screen looks great.

[dr beep]

New concept will cost me 8 bytes in tables, but will make the screen 232x192 pixels.
Here is a testscreen with 2 balls for test and smaller bats (will be larger in real)

[Andy Rea]

looking good

Fun isn't it rying to squeeze stuff into exactly 207 cycles... and the way that after deciding thats the fastest way you can do it and have to comprmise on available display width, you realise there is a way to do it quicker....

Keep up the good work Mr Beep, you are quite amazing with what you manage to squeeze into just 1K

Regards Andy

[dr beep]

looking good

Fun isn't it rying to squeeze stuff into exactly 207 cycles... and the way that after deciding thats the fastest way you can do it and have to compromise on available display width, you realise there is a way to do it quicker....

So true, and yet I had it coded in 206 T states, so I needed to add 1.
Due to sync between bats and ball I had to give up 1 column

Keep up the good work Dr Beep, you are quite amazing with what you manage to squeeze into just 1K
Regards Andy

Compression, self modifying code, reuse of memory when only used once, double use of linebuffers in upper and lower memory, everything is allowed to fit it into 1K.

[dr beep]

Question about 2 player controls:

What do YOU think are the best 2 player controls, please let me know!
For instance:
QZ and PM

or

QZ and joystick

or

whatever!

Right now I can built the right controls.

[dr beep]

Screen now ready

Also bat movement added

Time for ball movement

More than 256 bytes still usable!