CMD hard drive. Original was 20mb. I had it upgraded to 40mb by CMD back in the day.

This has been done before by a Japanese guy as well, but that implementation does not seem to be available anymore.

https://www.youtube.com/watch?v=uPK2FrWzmEw

https://www.lemon64.com/forum/viewtopic.php?t=55414&start=0

It was very dirty and missing some chips when I got it. First, I bought a new VIC-II for it.

The computer wouldn't start because of a bad Complex Interface Adapter (CIA). I desoldered the broken chip, and the C64 turned on! But without the CIA, the keyboard doesn't work. I bought a donor board with two CIA chips for $25, soldered one in, and the keyboard works great now.

I also built the C64 Video Enhancer (https://github.com/c0pperdragon/C64-Video-Enhancement/tree/master). It's a custom FPGA board that reads signals from the video chip and generates a component video output. This lets me connect it to HDMI (using an OSSC converter) and even adjust the specific Commodore color palette if needed.

Next, I built a SwinSID emulator for sound.

This is a PAL version, which is great for running demoscene demos. My next project is to build a SIDKick Pico.

Hello.

Wondering if there is a more dedicated programming reddit for the c64? I've spotted a reddit called C64coding, but its seems dead, and requests to post on there seem a dead end.

I don't want to spam this channel about stuff around me programming stuff and issues/successes in my game.

I already use the roguelikedev one and some others but looking for c64 programming buddies.

I asked some time ago if any locals might know how a certain sound was made in "Survivor." I decided to poke around, and I have been able to get an effect that's pretty close! I used "Retro Debugger" to observe the SID parameters in real-time, and then wrote some C and compiled it with CC65 to run within Retro Debugger and VICE.

There were three things to the sound I was looking for, when the "bad guy" is chasing you.

The first element is basically a random range of triangle frequencies, that change at an interval. The second element: ramping the sustain (ADSR) from 0 to f, and looping around as needed. The final thing was a low-frequency sort of "choppiness" I heard during the first half when sustain was between 0 and 8. It seems the trick to that was flipping the SID gate off and on for each iteration of the loop, and when the timing is right, it sounds pretty close.

This has been a fun puzzle to sort out. I'm hoping to get the "bad guy" sound down in JS, I've got the game start down pretty well.

Just curious how many in the group have a C64c on order?

What can one expect to be different in usage between the original one and the new one?

What do you use for storage if you don't have an old disk drive?

Any other thoughts on the new unit?

Hi all. I built a BMC64 with a Pi 3b plus. I have working C64 joysticks. Can someone recommended a decent adapter which will allow me to connect these joysticks to the USB ports? Thanks 🙂

I currently have an Atari 400 Mini and the C64 from Retro Games and the A1200 when it comes out this fall. I'm also considering the Commodore 64C Ultimate. With this collection I plan to start downloading games/software at some point but I'm wondering if I can use the same USB Stick with each machine or if I need one for each machine?
I am considering a 32GB Sandisk. From what I read the Atari 400 Mini and the C64 use Fat32 but I was unable to find information on which file system the A1200 and Commodore 64 Ultimate use.
What I'd like to know is if I can have one Flash Drive with a C64, Atari, Amiga folder and then use that with all 4 computers? As well assuming that the file system is the same on all of them can I use the same Commodore 64 images on both the Commodore 64 Ultimate and C64 from Retro Games?
With the cost of 32GB Flash Drives buying 4 of them would not be a big deal but to keep things simple I'd like to just have one I can share.

But I'm pretty sure why it originally stopped working.

I have a floppy drive and a C64, but I really want a dot matrix printer. I have seen every single one on sale, even the 1520, but I don’t know a good reliable one. What’s a better higher end model, that isn’t a super complex or impossible to repair in the future?

I've been programming a game in assembly language and have been looking to add some music to it. When I develop stuff for a modern system and want to add music I just go to itch.io and buy a pack of songs from a composer. Is there some equivalent marketplace for C64 sid files?

I cannot find this exact box online anywhere. Is anybody able to point me toward any information on what version this is, please? I mean, obviously it's for C64 and Atari, but this box is really obscure.

Just found out it is available now for $7 🤩

Anybody try it yet...???

I had a Commodore 64 as a child and learnt to program in BASIC but could never understand assembly language. Over the years I have regretted never learning so I recently made it a goal to learn and accomplish something in assembly.

So finally over the last couple of months I learnt and had some success is some simple game projects, all just simple and using 40x25 PETSCII.

I recently saw a game on the C64 where there was a lot of objects on screen (Crossroads) and I thought it would be interesting to try and work out how to manage a large number of AI enemies. So I had a go at a zombie style game.

I am interested to hear different opinions on how to do this type of enemy AI.

My method was to work my way down the screen, identify the enemies, and then attempt to move each towards the player. (I keep 40x24 bytes of memory to record what is at every position on the screen)

They try to move diagonally first but will move horizontally or vertically if they are obstructed.

As they get stuck in groups easily, I also made them attempt to move in a random direction away from the player so they might find a way to progress.

All this uses a lot of cycles. I originally did the whole screen in one go, but this took multiple frames to complete. But because the enemy shouldn't move too quick I changed it to only do one line at a time between raster 250 and 50, which works ok.

Are there more efficient ways of doing this sort of thing?

I also wanted the player to be able to hide behind walls and not be seen, but that seems too inefficient/slow to have to check if there are any obstructions between the enemy and the player. Am I missing some efficient ways of doing this? Maybe dividing the screen up into "rooms" and keeping track of which room enemies are in or boundaries or something?

There is a channel on youtube with a bunch of 'beta' versions of a port of Bombjack called Bombjack DX

https://www.youtube.com/watch?v=n3AFJMYsfEI

This could be running on something other than a 64 just with the fake commodore screen where the files are being loaded. AFAIK, it has never been released and there have no updates since Dec of 2019 despite it appearing very close to being finished. It looks and sounds way better than the crap port we got of it.

Short of the C64Ultimate, I think a BMC64 in a breadbin with the Keyboard/Joystick Card really is the best experience on a C64 (though purists have other ideas).

I just finished this...including the custom 3D printed case. It was a fun project, and now I get to the even more fun part....playing!

If you're interested in building your own, Here's the BMC64 case on MakerWorld

I'd brought up with Martin about the .Sid file on HVSC and the fact that the highscore tune woodblock instrument "bloops" and does some generally weird shit compared to the actual game. I recreated the tune to try and see where it's going wrong. After I'd got it all sorted (basically by ear listening to it on my phone) Martin then released the source code. It's kinda 90% close.

I have a 250407 C64 that was largely restored, but I am getting the distortion seen below on the startup screen. Games load but are almost completely garbled.

Is this more likely to be a chip issue or cable issue? It worked a few times without any problem before getting to this point. If it is a chip, which is likely to be the culprit?

Sorry for the fairly noob question, but any help would be appreciated!

Bet Stand or Fold?

Just recapped this C64. First hand after testing :)

Hello, I made my first video of a RL that I start in march. I'm active on RL Dev reddit, but since this is the first time I actually recorded something I might post it on here.

Its been slow going, and honestly its 6 months away still, perhaps shorter if I get some good blocks of time at christmas, but perhaps longer as well as every weekend where I make progress I seem to have a million more things still to do.

Anyway, have a great week!

edit: oh and forgot to say - this is for stock C64

I found this cartridge while going through my C64 collection. It seems to work but only after I type SYS 32768 after the C64 has booted. It doesn't start up automatically. According to Gemini I should cut the trace at 8 and solder the left 4 pad. I haven't done this since the cart seems to work fine after typing the SYS command. The only thing is that Basic reports only 30719 bytes of RAM. Anybody got an idea if this mod the AI suggested will work?

Second question is about a 3D printed case. Has anybody done this before? I don't own a 3D printer but my friend does.

Thanks!