News for hackers. Stuff that matters.
Re:Porting a NES Emulator from Go to Nim by mhd on Friday May 01, 2015 @04:54PM (#9474449)
I'm quite impressed about the small amount of code required for a NES emulator. I thought they'd have to do all kinds of special casing for cartridge-specific stuff…
Re:Porting a NES Emulator from Go to Nim by masklinn on Friday May 01, 2015 @05:04PM (#9474515)
The more accurate the emulator is, the less special casing there's a need for: special cases/hacks are necessary when the emulator takes shortcuts and doesn't implement the hardware features the game relied on. If the hardware features are fully implemented all games ought work without hacks. Hence bsnes (as far as I know) not needing game-specific hacks but requiring a hefty config to run.
Re:Porting a NES Emulator from Go to Nim by chongli on Friday May 01, 2015 @05:07PM (#9474540)
The problem with the NES is that games have all kinds of different hardware inside the cartridges. In order to achieve high compatibility you need to emulate all of these chips. It's not nearly enough to accurately emulate just the NES itself.
Re:Porting a NES Emulator from Go to Nim by def- on Friday May 01, 2015 @05:17PM (#9474585)
Not all games work. Only the most popular mappers are implemented, which covers about 85% of games.
Re:Porting a NES Emulator from Go to Nim by mreiland on Friday May 01, 2015 @05:26PM (#9474624)
Many cartridges came with custom hardware, you have to implement them specifically, which implies special casing for the hardware, which sometimes implies special casing for the individual game.
Re:Porting a NES Emulator from Go to Nim by esaym on Friday May 01, 2015 @11:09PM (#9475714)
Indeed, I didn't think it could be so simple either. Figured "what the hey" and thought about writing one in perl, but a few already beat me to it looks like: https://metacpan.org/pod/Games::NES::Emulator