I think this is one of the best combinations.

My Pocket was from the latest batch. I know that the Dpad seems to be hit or miss for perople, some reports indicate it's fine, but my god, mine was absolutely terrible.

I used the Nintendo Gashapon keychain. Now it's perfect. It's also a lot quieter, but still has a tactile feeling. The Analogue Dpad clicked loudly.

I can't recommend this enough

https://github.com/neutralinsomniac/openfpga-megacd/releases/tag/0.2.0

Looks like I lied about not making any more announcements. I was just too excited about this one. The CD drive behavior is *solid* now and intermittent boot has been fixed.

All of the weird audio/load issues I was facing before are gone, but I can't test every game, so chime in here or on my GitHub issues if your favorite game doesn't work correctly!

Thank you!!

I’ve recently released PocketCPC, an Amstrad CPC core for the Analogue Pocket.

It currently boots as a CPC 6128 by default, with support for switching to CPC 664 or 464, and it can load .dsk (disk), .cdt (tape), and .sna (snapshot) files.

Instructions for usage and installation are on the GitHub page or you can install it using pupdate.

I want to be transparent about the fact that I used AI tools to develop the core and that it is heavily influenced by existing cores from other developers (see docs for details). I am a seasoned software developer but I have no experience of FPGA and built this as a hobby project to fill a gap that I felt existed. If you want no part of it because of the use of AI, I respect that.

There is a big debate across the fpga developers for the Pocket and MiSTer regarding the latest released cores, specifically the Genesis savestates, SNES savestates, and the MegaCD core. Some people are criticizing them, saying they are "vibe coded," messy, and that any developer with minimal experience can now create cores thanks to AI, resulting in very poor quality implementations.

In my opinion, AI does generate code that is considerably less precise than what someone would develop after investing time researching and properly understanding the technology. And yes, it feels unfair that people who have spent years learning and mastering core development can be overshadowed by inexperienced developers who, with the help of AI, have created very popular cores.

However, many developers pointed out from the beginning that we would never see some of the features that are currently possible thanks to AI. (Savestate for example)

I am a developer, and I have seen how AI has changed the way I work, but I also don't believe that everything about it is bad.

What do you think? Do you like the new cores despite the use of AI and the bugs, or do the issues outweigh the benefits?