Show HN: Simple Gameboy Emulator
github.com
Show HN: Simple Gameboy Emulator
1–10 of 24 posts
Re: Show HN: Simple Gameboy Emulator
#2Here is some inspiration: https://github.com/dolphin-emu/dolphin
Re: Show HN: Simple Gameboy Emulator
#3Re: Show HN: Simple Gameboy Emulator
#4It would be really cool if someone web-assemblied the best of class game system emulators and exposed them all through a uniform web interface. All vintage game consoles accessible through a single site!
Re: Show HN: Simple Gameboy Emulator
#5I know nothing about emulators, so it would be nice if the README provided instructions for how to build and run the emulator. Here is some inspiration: https://github.com/dolphin-emu/dolphin
Re: Show HN: Simple Gameboy Emulator
#6It's worth noting that there was actual extra hardware built into the carts, so you need to implement certain features like extra RAM based on the cart ID in the ROM file.
Re: Show HN: Simple Gameboy Emulator
#7Re: Show HN: Simple Gameboy Emulator
#8Re: Show HN: Simple Gameboy Emulator
#9Making a Gameboy emulator was one of my favorite and most instructive personal projects. It's worth noting that there was actual extra hardware built into the carts, so you need to implement certain features like extra RAM based on the cart ID in the ROM file.
Re: Show HN: Simple Gameboy Emulator
#10Great! The CPU.c code is quite instructive since I'm writing a toy VM in my free time. Starring this :)
http://www.pastraiser.com/cpu/gameboy/gameboy_opcodes.html
The next step in emudev, with most compiled/systems languages at least, would be to create macros (such as OP_LD or OP_ADD) that generates static instructions at compilation. Another, cleanish method, in C is to generate a 256-length function pointer (void*) based static array and map those generated functions to that, to make the dispatch step simpler. Small trade off, performance-wise, but rarely matters for 8-bit CPU's (where you would usually use an opcode table over an instruction decoder).