Make please game name: Chicky

Don't feel bad. I live in the USA and I had a C64 in the early 80's and since there was no internet back then, it was nearly impossible for me to study this as well. C64 programming books and tutorials were not very easy to find, even in the USA, and when you could find them, they were fairly expensive. I could barely afford to buy any games let alone programming books.

@@ferrellsl brothers in misfortune :)

CBM Prg Studio is very nice, but lately I've started using C64Studio.

😃 I've never heard of 24x24 pixel sprites. May I ask you to elaborate a bit on that? 😃

@@BikeArea From memory (eek! 😃) the hack effectively halved the number of sprite pointers available for use as the additional three rows used the data that would have been the top 3 rows of the next sprite in the bank, offset by one byte (so only 2 2/3 rows). This meant that one could only use alternate sprite pointers which was a massive waste of limited RAM. As for the actual hack itself, it was enabled through setting some bit in some barely documented VIC register and while I can visualise the pages that this information is on, finding it all these years later hasn't happened yet. I suspect that as a result it's support by emulators is not great.

@@nickryan3417 That sounds like a very deep rabbit hole. Holy moly! :D Thanks a lot for the details!

Thanks, I'm glad you enjoyed it.

Yeah, I think it's really helpful to have a tool to do sprites and background graphics, so much easier to play around with colors and making little changes. Cheers, Jake

Thanks for sharing.

Same here. I changed back to 1 second and it still works !

Yeah, it was kind of my goal to make things as easy and approachable as possible with this series. I remember back in the day drawing sprites on paper and then calculating the binary values and converting to hex values followed by entering all the values into a machine code monitor. Sure is a lot easier with good tools. Cheers, Jake

Thanks, much appreciated.

Yeah tool like these really do make development a lot easier. I understand some people like to keep it "pure" and do everything on the C64 itself, but even back in the day it was common to run tools on other machines. But I understand for some the journey is most important. I didn't notice the color dropdown thing until I was nearly done recording the episode. It's caused by scaling. I always try to scale everything in these videos to make it easier to watch, not a fan of tutorial videos where everything is recorded in high resolution with tiny text that is nearly impossible to read unless you watch on a PC monitor in full screen. Cheers, Jake

The NES got the same limitation of max 8 sprites per line (that's why you often see sprite flickering in NES games) and the NES sprites are much smaller 8x8 or 8x16 compared to 24x21 or 12x21 on the C64. The NES does allow for more colors though. You can do more than 8 sprites on the C64, but you will have to implement a multiplexor, like I did for the intro to this episode with 32 sprites on screen at the same time. For a more in depth comparison, I recommend watching this video: kzfaq.info/get/bejne/gttjiqiX2dnGoZ8.html Cheers, Jake

Hi FD, it's very easy to use the C64's hardware sprite collision detection, it will give you pixel perfect collision detection. All you need to do is read the register $D01E, it will tell you if 2 or more sprites have collided, the bits corresponds to the sprite numbers (1 to 8) and if you want to check for sprite to background collision you can read the register $D01F, it will set the bits corresponding to which sprite collided with the background. I will cover music and sound effects in a future episode. Hope this helps. Cheers, Jake

@@TheStuffMade Hi Jake Do you have any projects that I can download? If not, I'm hoping to find something on the internet that is explained well! Unfortunately many youtubers make videos but don't know assembly well! It would be easier for me to understand.... Anyway thank you so much for your quick response! Sorry for my bad English... Frank

@@FD-ze1xg I don't have a project covering these topics for download yet. I will cover them in the future, the collision detection is quite easy, but music and sound effects gets a bit complex. Cheers, Jake

I've never used the bitmap import feature in the Petscii Editor, but I believe it requires the size to be 320x200. You might want to have a look at CharPad for this instead. Cheers, Jake

Not at this time, but it's likely I'll do one at some point. It can get quite complex to write an efficient sprite multiplexer and sorting the sprites by y position can take quite a lot of cycles when you have many sprites. Cheers, Jake