![]() ![]() I touched on this in the original thread. This is an edge case exposed by the game Micro Machines. I'm going to give NEStopia 2 points for this, since IRQ timing and cycle stealing are two different things. Rather than emulating the buffered sample fetch, it runs the DMC ahead a bit, then backtracks after the IRQ fires:Ĭpu.StealCycles( cpu.GetClock(cpu.IsWriteCycle(clock) ? 2 : 3) ) ĭma.address = 0x8000 | ((dma.address + 1U) & 0x7FFF) In this post, I am comparing Win versions of FCEUX 2.2.2 and NEStopia 1.40, which to my knowledge is the latest official release of each emu.ĭMC timing is very tricky, and a handful of Camerica games rely on reasonably strict DMC IRQ timing for split screen effects in some games, specifically Fire Hawk and the dreaded Mig-29 Soviet Fighter (one of the harder games to get working)īoth emus run the games correctly, but looking at the source, FCEUX cheeses it with a hack. But this might be fun and interesting nonetheless. This is far from an exhaustive list, and I am grossly oversimplifying by just assigning points to individual aspects. So did FCEUX catch up? Was I talking out of my ass? I decided to take a look into a lot of "gotchas" that plague NES emus which try to cut corners on accuracy. ![]() In that time, FCEUX has been in active development, while NEStopia has largely been idle. ![]() In my reply I made some bold claims and pretty much said "zomg NEStopia is the greatest thing ever omgomgomg", but I realized that opinion came largely from the state of the emulators ~7 years ago. Obscurumlux01 in another thread was curious about accuracy comparisons between FCEUX and NEStopia. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |