I've put together a 6502 emulator, not really thinking about cycle accuracy. I read an instruction, execute it, then wait the required number of cycles before running the next instruction (let's call this "burst") Then, I started reading about cycle accuracy, how emulators perform the cycle-by-cycle actions as described in https://www.nesdev.org/6502_cpu.txt. Clearly, a burst-style emulator would run faster and be simpler to write (mine's running at 600MHz on a i7-1165G7), but if it fails with many games, there's no point. I couldn't find any articles that discuss the implications of this.
How important is it, practically, to be cycle accurate? What games work with a cycle-accurate emulator but fail with one that runs instructions in a burst fashion?
Trying to get a gauge on whether I should restart or continue with what I have.
How important is it, practically, to be cycle accurate? What games work with a cycle-accurate emulator but fail with one that runs instructions in a burst fashion?
Trying to get a gauge on whether I should restart or continue with what I have.
Statistics: Posted by hurry-civic-elixir — Tue Dec 03, 2024 3:44 pm — Replies 1 — Views 93