Skip to main content

Homebrew game for C64 part 7 - revival

R
evival of the project, that is. It's not a resurrection-based game.

Following a hiatus due to realising that my original concept was rubbish, I had a different idea. It's nothing particularly original; sideways scrolling, and the sheep following one another like a snake. There will be things to collect, and things to avoid.

Avoiding the enemies will be more difficult, the more sheep are following the one you're controlling. The idea is that you start with one, and accumulate friends as you go along.  They may be dispatched by enemies, and there will be a maximum of four because of the way I've used two sprites to get hi-res with multicolour effect.

There are no collectibles or enemies yet, but here's the basic action, which I'm really happy with.



The sound you hear on the video is being played by a breadbin 64. It's my most recent tune for this game. The video is captured from VICE

It was my first go with the 64's scrolling capability. I cut my teeth on Vic20, and later spent some time with z80 machine code on a Spectrum +2.

It was straightforward, and it's very effective. The bulk of the work to actually move screen data only has to be done once in 8 frames. And limiting the actual scrolling images to half a dozen rows on the screen means that it doesn't take long, and I can use the character set, simply rotating 240 characters in screen memory.

I plan to make sets of sprites scaled to slightly different sizes, to give a better perspective effect - they'll get smaller the higher up the screen they are (ie further away).

So for the scrolling hills in the background,  did I generate them by algorithm? Or draw them electronically and write routines to pack and unpack the data? Did I heck.
I got out graph paper and coloured pens. Oldschool!

Each screen-width of data packs to 3-4 hundred bytes. I've made three screen-widths before it repeats. If that's  good enough for Fred Flintstone.....






Comments

Popular posts from this blog

ZX81 reversible internal 16k upgrade

T his post is an upvote for Tynemouth Software's  ZX81 reversible Internal 16K RAM upgrade . Their instructions are easy enough for even me to follow and don't involve cutting tracks. This is the ZX81 I've had out on display and used whenever I wanted to. It's an issue 1 and was probably a kit judging by some very untidy assembly. It has a ZX8-CCB  composite video mod and an external keyboard fitted. On board it has two 1k x 4-bit chips.  The ZX81 originally came with 1k on board. Thanks to a trick with compressing the display in ram, that was enough to type and run a small program but you soon felt the limitations. Back in the early 80s, the solution was a 16k ram pack which plugged into the back[1] and this is the way I've been using this particular machine. These ram packs are notorious for 'ram pack wobble'. Even if fastened into place, you can still randomly find your work disappearing. This is a very reliable solution using a more modern 32k chip (half

Driving NeoPixels with Z80

I 've long been thinking about a version two   RC2014 LED matrix module . I've had a matrix with a MAX 7219 on a module. It's a nice enhancement. But there's only so much you can do with a single-colour LED array right? Wouldn't it be cool to have RGB LEDs?  At Liverpool MakeFest I saw a wall-sized ping-pong ball NeoPixel display and picked up some NeoPixels with the intention of making one. Possibly driven by my RC2014.  I enjoy learning about protocols and have had some SPI devices working with the RC2014 - bit-banging SPI works really well because it doesn't care about timing. NeoPixels really do care about timing though. From Adafruit's web page about their 8x8  NeoPixel matrix: If there's one thing I want to get across in this blog post, it's don't just accept what you're told . Question everything. Learn about what's going on and find out why you're being told something isn't possible. Get creative with workarounds. I'

Making new ROMs for the Vic20 / Vicky Twenty

M y Vicky Twenty is very nearly complete.  As things stand, the board and every single component is new*. The processor and VIAs are newly-manufactured (W65C02 and W65C22).  Obviously the Vic1 chip isn't manufactured today, but there is 'new old' stock about. I have been able to buy a Vic 1, date code 1987 (which seems very late). It obviously hasn't been in a computer before, passes the acetone test and works. The same goes for two of the ROMs - character and BASIC. But I haven't been able to buy a new-old Kernal ROM (901486-07). I am able to borrow one - all of the boards I have, have this particular ROM socketed. I don't know whether all of this indicates that the Kernal has proved less reliable than the other two. I recently bought a TL866 for another project. Of all the retro-computing hardware things I've had to learn to do, making ROMs has been one of the simplest. So far, everything has been very easy and worked first time.  I'm not sure that it&