C64 Dev Machine: The Game You Never Got Around to Making

A visual approach to Commodore 64 development brings code, graphics and sound into one workshop, and gives that unfinished game idea somewhere to begin.

There is a particular kind of unfinished game that exists entirely in someone’s head. The main character is clear. The first level has been designed several times, usually while doing something unrelated. The music is probably ambitious. Development, however, has been waiting patiently for the owner to become the sort of person who understands assembly language.

For anyone drawn to the Commodore 64, that can be a long wait. Enjoying the machine and knowing how to make it do something new are different skills. A moving sprite looks wonderfully straightforward until you have to explain every part of its behaviour to a computer.

C64 Dev Machine, by Polytricity, offers a visual workspace for building C64 programs, with graphics and sound tools alongside the code. Its appeal is the opportunity to explore how a program works while assembling something you can actually run.

An old computer with a very current development tool

This is an actively changing project. Pro version 1.30 was uploaded for Windows on 5 October 2026, followed by the macOS builds on 6 October. A video update appeared the same day. Those dates make this a particularly good moment to look at what the tool has become.

The preceding weeks brought useful changes around the edges of development: starter projects, a closer view of memory usage, and a refreshed interface. The 25 September update introduced SHMUP.V and Zyrons Escape under its templates and ports, alongside improvements to the memory bar and asset previews.

On 1 October, the project announced that its intended feature set was complete, while acknowledging that bugs could still emerge. Further releases have already followed. For someone starting a project, the practical lesson is simple: keep track of the version you are using, particularly when following an older tutorial.

Assembly becomes something you can arrange

Assembly language describes relatively small operations: load a value, store it, compare it, branch somewhere else. On the C64, the processor is a 6510, a variant compatible with the 6502 instruction set. Knowing the instructions is only part of the job; you also need to understand where the machine keeps information and how its hardware responds to it.

C64 Dev Machine presents instructions and higher-level operations through nodes. That gives a program a spatial form. You can organise pieces of work on a canvas, inspect relationships and gradually build an understanding of the sequence behind the result.

The project’s node-to-code facilities make that relationship especially interesting. In Pro, selected instructions and some macros can become editable assembly blocks. A code panel also lets you inspect what is being produced. Some macros cannot be converted because they depend on relationships within the project.

That creates a useful learning opportunity: begin with an operation you can recognise, then examine how it is expressed closer to the processor. The important question becomes why a piece of code works. Moving a block is easy enough; understanding when to run it, what it changes and what happens afterwards is where programming begins.

The graphics belong in the same workshop

A game needs something to move, somewhere to move it and a reason for the player to care. The distance between drawing an object and getting it into a running program can swallow a surprising amount of enthusiasm.

The tool brings together sprite, character, map and bitmap editing, including PNG conversion and an integrated Spred64V2 sprite editor. That gives the visual side of a project a place alongside its behaviour.

Existing artwork can also enter the workflow. Documented SpritePad and CharPad support allows sprite files to use the layering and animation system, while character artwork and maps can feed the map and metatile tools. The Bitmap Builder has its own stamp selection and ordering features.

For a small project, the attraction is continuity. You can think about a character’s appearance and its movement as parts of the same experiment. A jump that feels wrong might need a different animation, a different movement routine or both. Keeping those decisions close together makes the development process easier to follow.

There is still craft involved. A drawing has to remain readable at its intended size. Animation needs convincing timing. A level needs enough information to guide the player. Convenient editors give you more room to work on those decisions.

Music can become part of the experiment

Music Maker extends that workshop to sound. Its development has included changes to preview playback and an editable music port associated with Zyrons Escape. The September update describes changing playback speed as one way to experiment with that material.

This is a useful way to approach a soundtrack when you are still learning. A short pattern gives you something manageable to change and listen to. You can explore what happens when the pace shifts, when a phrase repeats or when a sound leaves more space.

The broader lesson carries across the entire project: understandable examples invite questions. A finished effect can be impressive, but an editable one lets you investigate how its parts contribute. For a beginner, that can be the difference between admiring somebody else’s work and making a deliberate change of their own.

Getting from an idea to a running program

The development loop has clear shortcuts: F5 launches a test in VICE, F4 exports, and F6 is offered for testing on C64 Ultimate. VICE emulates Commodore computers, allowing the C64 program to run on a modern machine.

Exported PRG files are an important part of the proposition. They give the program a life beyond the editor, so a successful experiment can become something to share and run in a suitable C64 environment.

The value of a short testing loop is easiest to appreciate when something goes wrong. Make one change, run it and observe the result. If a character moves too far, you have a small question to answer. Change the movement, animation and collision logic together, and you have created a much more entertaining mystery.

For a first attempt, aim for one visible behaviour. Move an object. Make it respond to input. Stop it at a boundary. Each success gives the next experiment a firmer starting point. A modest working program teaches more than a large collection of unfinished intentions.

Choose which C64 you are building for

The project supports REU workflows, and its development notes describe testing byte data and bitmaps with both VICE and C64 Ultimate. The current feature list also includes support for Ultimate’s 64 MHz turbo mode.

Those options make the target configuration worth deciding early. A project that depends on extra memory or accelerated execution has different requirements from one intended for an ordinary, unexpanded C64. Test using the configuration you want other people to use.

Standard machines remain part of the picture. A 23 September update specifically reported improved metascrolling on a stock C64. That is a useful detail for anyone interested in working within the familiar machine’s limits.

There is creative value in choosing a boundary. It gives decisions a context: how much movement a scene needs, how elaborate an effect should be, which part deserves the available resources. Extra capability opens possibilities; a tighter target gives you a different design problem.

Lite gives you a starting point

As of 6 October 2026, the free Lite downloads are version 1.28 for Windows and macOS, while Pro is at 1.30 and costs a minimum of US$10. The two editions therefore have different current version numbers.

Editing assembly code blocks is a Pro feature, as is the custom IRQ handler. Pro also supports importing and exporting code blocks, allowing useful routines to be kept and reused.

Lite has a useful qualification: the September update expanded it to build projects containing Pro features. Being able to build an existing project does not mean every part of it becomes editable. That distinction matters when trying a shared example.

Download the supplementary files alongside the application. They collect examples, documentation and readme material. Before changing an example, get it running in the expected environment and save your own copy. You will then have something working to compare against when your first improvement produces a very unexpected result.

A reason to make something for the machine

The most interesting promise here is the chance to connect familiar C64 sights and sounds with the decisions that produce them. A sprite becomes a small collection of problems you can understand. A tune becomes something you can alter. The machine begins to feel approachable through the work you do with it.

A visual tool will suit some people better than others. Experienced assembly programmers may already have a workflow they prefer. Someone returning after years away may welcome a different way to organise a program. A newcomer may simply want to see an idea move before committing to a much larger learning project.

Start with the smallest part of that game in your head. Give the character a screen to stand on and one thing to do. The elaborate music and several decades of planned sequels can wait.

C64 Dev Machine is available on itch.io, with free Lite downloads and paid Pro builds.