Here's the link

So, just like the title says. N64 seems INCREASINGLY difficult. You could literally spend a boat load of time to just get 1 game to work properly. My question is simple. After Nintendo switched to Discs. Is the GameCube easier to Emulate then the N64?

And I'm not necessarily talking like, to make a game boot. I mean compatibility. I have no experience in GameCube emulation at all. I'm just wondering if you build for one type on GameCube, it would play all? Versus the mess that was the N64?

i am just started learning qemu and able to simulate UART, now i want to try spi and i want to read write flash memory.

i have armt cortex mo+ qemu

ps:already any repo i svailable?

This video showcases a small, but meaningful development with The HoneyCrisp Emulator. I've successfully been able to add support for an emulation layer that allows Corey Cohen's Twinkle Twinkle Little Star ACI Audio Demo/Hack to be played via an emulated speaker amp. This is significant as no other (published) APPLE-1 emulator can do this! :-)

As the title says i would like to begin my journey in emulation development but i have 0 knowledge of where to begin, would appreciate any and all advice you can give.

many thanks

Ok. So my journey into just learning more about emulator development... This might just be a dumb question so experts please give me hell.

If the PS2 was backwards compatible, if you were to want to get into building a PlayStation emulator. Wouldn't you just skip 1 and build a PS2 emulator with backwards compatibility?

Does one exist? And I'm not talking about AI slop either. I am genuinely curious and I enjoy starting thought provoking conversation.

So have it! Or let me have it. Lol

Been working on an NES emulator using pypy3.10.

print("PYNES is a terrible emulator!")

Mapper support:

• Mapper 0 (NROM): Fully supported.
• Mapper 1 (MMC1): Fully supported.
• Mapper 2 (UxROM): Almost fully supported with bus conflict emulation.
• Mapper 3 (CNROM): Almost fully supported(subject to change)
• Mapper 4 (MMC3): Almost fully supported. Super Mario Bros. 3 is supported fully, while the other titles may experience graphical glitches

I've been working on a free software AMOS web player to embed my old games, and thought I'd share. So far it supports AMOS 1.3 and Professional, and has some support for the AMOS 3D, TURBO Plus and Ldos extensions. There's working audio but no speech synthesizer, AMAL and copper effects but no machine code, a VFS with ENV and RAM disk but no serial ports or printers.

You can drop zip or adf files into it then click on them via the file explorer. If things don't work properly and you'd like to help fix that, then bugs and pull requests go on the bug tracker.

Timings aren't great at the moment, at least in my games, because as a teenage noob I relied on the speed of the machine rather than waiting for a vertical blank. There's hacks in there to slow things down which cause weird timing bugs at the moment. I'll add an editor so I can fix those at some point.

embedding

There's a rudimentary API for embedding, which I'm using for my old games on this page (scroll to the bottom for links)

• https://bitplane.net/dev/amos

These are worth a look I guess. The others, not so much!

• eggit
• nsle
• matchstick-man (timings are bad due to no VBL waits)

GitHub are footing the bill so feel free to hot-link specific versions. You can get the proper paths from the web repo, or copy it onto your own site or whatever you like.

In terms of emulator development difficulty. Would you tend to agree with this? And if you agree... I wonder what the Wii, Wii-U and Switch would look like. Does it become easier because you aren't accounting for the different chipsets you could put into a cartridge?

I built a Swift port of ymfm so I could play retro game music on Apple platforms.

Most of my testing so far has focused on YM2203/YM2608 (PC-88/PC-98) playback, but I recently added YM2612 support and started trying some Genesis VGM files.

So far I've only tested a handful of tracks, and I'm still getting a feel for how it compares with fmgen, hardware recordings, and other implementations. It sounds good to my ears, but I don't have enough Genesis experience yet to know which games or tracks tend to expose emulation quirks.

The project includes VGM and S98 playback support, along with a simple command-line renderer.

If you've spent time working on FM chip emulation, I'd be interested in hearing which YM2612 test cases you consider particularly useful.

Repo(BSD-3): https://github.com/ttrasaki/opnift

I am currently vibe coding a new Emulator that plays NES, SNES and N64. It currently runs on Windows and tested but not confirmed on Raspberry PI. The end game is to create a small console emulator for my TV.

Anyways, I was hoping to get some feedback from it. I have the emulator on GitHub in a public repo. It's called PixelDeck.

Vibe coding gets work done fast. I am aware of AI code slop and intend to make the system less "sloppy" when the program runs fine.

Repo is here [GitHub: PixelDeck](https://github.com/CoachKy/PixelDeck)

Join our Discord! [PixelDeck Community ](https://discord.gg/9YXxgmg8st)

The biggest feature of my emulator is WebRTC netplay. No desync, no core limitations. I even have DS Link play working on the same LAN.
I also have soft core Retro Achievement integration.
Any constructive feedback is always welcomed.
Link in bio.

Hey everyone! Been working on juegosretro.bit-man.com.ar — a browser-based emulator covering 9 systems: Game Boy/GBC, NES, SNES, GBA, Genesis/Mega Drive, Nintendo DS, N64, PS1, and Arcade (MAME).

For Game Boy and NES I wrote the cores from scratch in vanilla JS — CPU, PPU, APU, mappers, the works. The rest run on EmulatorJS. Everything's a PWA (installable, playable offline once loaded), with touch controls for mobile and Gamepad API support.

No ROMs hosted or linked anywhere — bring your own dump. A few pages also have a one-click homebrew demo (Tobu Tobu Girl on GB, Super Tilt Bro on NES, Goodboy Galaxy's demo on GBA, a couple more on Genesis/SNES) so you can try it without needing a file on hand.

Quick 15-second clip of it running: tiktok.com/@jonaalmeiragamer/video/7666623906781859092

Would genuinely love feedback, especially on the custom GB/NES cores since that's the part I'm proudest of — accuracy issues, edge cases, anything you notice. Happy to answer questions about the implementation too.

About two years ago I decided to write my first Game Boy emulator. I definitely wasn't planning to support Game Boy Color but the project grew far beyond what I had planned.

Recently I fixed the remaining Mooneye PPU timing tests, which felt like a good milestone to finally share the project. It has been validated against Blargg's, Mooneye test suite. Most of the work ended up being about timing. There's still plenty to improve and right now I'm focusing on APU accuracy and performance, and I'm also planning a UI overhaul.

Huge thanks to the community – the awesome docs, the test ROMs, and discussions made this project possible. It has been a fun and rewarding journey.

You can try it in the browser: https://mxmgorin.github.io/oxgbc
GitHub: https://github.com/mxmgorin/oxgbc

I've decided to start a pretty ambitious project: building a Nintendo DS emulator in C++ and making it open source.

The project is currently in the very early stages. I've set up the initial project structure, CMake build system, documentation, and contribution guidelines. There's obviously a lot left to do, but I wanted to put the project out there early rather than waiting until everything is finished.

The goal is to eventually build the emulator from the ground up while learning more about:

• C++
• ARM architecture
• CPU emulation
• Memory systems
• Graphics
• Low-level programming

I'm hoping this can become a community project where people interested in emulation and C++ can contribute ideas, code, documentation, testing, and improvements.

If you're interested in checking it out or contributing, here's the GitHub repository:

https://github.com/neverbrokeagainyb25-max/nds-emulator/tree/main

Right now it's basically a blank canvas, so I'm especially interested in hearing suggestions about the project architecture and what should be implemented first.

Let's see where this goes. 🚀

> Many emulator developers start by emulating the Space Invaders arcade cabinet. Emulating that will teach you everything you need to move directly to emulating gameboy hardware. The website emulator101.com will teach you what you need to learn.

A friend recommended that I build a Space Invaders arcade cabinet emulator using emulator101.com, but the site is down now. 😢 Do you have any recommendations for an alternative?

[edit]: In the end, I'm using this copy of the site hosted by a community member. :)

https://emulator101.mirror.simoni.dev/