Accuracy: Difference between revisions
No edit summary |
(effect of use of inaccurate emulators) |
||
| Line 1: | Line 1: | ||
'''Compatibility''' is how well an emulator produces the same output as the original system when running a particular known program. | '''Compatibility''' is how well an emulator produces the same output as the original system when running a particular known program. | ||
'''Accuracy''' refers to how well an emulator produces the same output as the original system when running an arbitrary unknown program. | '''Accuracy''' refers to how well an emulator produces the same output as the original system when running an arbitrary unknown program. | ||
An emulator can be highly compatible without being very accurate; Nesticle was this way back in the 1990s. | An emulator can be highly compatible without being very accurate; Nesticle was this way back in the 1990s, running a wide selection of popular North American commercial games. | ||
Accuracy cannot be measured directly. Compatibility with [[Emulator tests|ROMs designed to test obscure behaviors]] and [[Tricky-to-emulate games|games relying on obscure behaviors]] is a good (though not perfect) predictor of accuracy. | Accuracy cannot be measured directly. Compatibility with [[Emulator tests|ROMs designed to test obscure behaviors]] and [[Tricky-to-emulate games|games relying on obscure behaviors]] is a good (though not perfect) predictor of accuracy. | ||
| Line 8: | Line 8: | ||
Nesticle, for instance, allowed writes to [[PPU registers|$2007]] at any time, when the NES allows it only on or after line 241 of each frame (vertical blanking) or when $2001 & $1E == 0 (forced blanking). | Nesticle, for instance, allowed writes to [[PPU registers|$2007]] at any time, when the NES allows it only on or after line 241 of each frame (vertical blanking) or when $2001 & $1E == 0 (forced blanking). | ||
Most emulators allow the program to twiddle PPU registers immediately, while the NES PPU [[PPU power up state|ignores most writes for the first frame after a reset]]. | Most emulators allow the program to twiddle PPU registers immediately, while the NES PPU [[PPU power up state|ignores most writes for the first frame after a reset]]. | ||
Inaccuracies like these led to inadvertent development of [[Program compatibility|programs that the NES itself cannot run]] during the early years of NES homebrew. | |||
Whenever you discover a difference in behavior between the NES and best-of-breed emulators (like Nintendulator and Nestopia), you can help emulators become more accurate. | Whenever you discover a difference in behavior between the NES and best-of-breed emulators (like Nintendulator and Nestopia), you can help emulators become more accurate. | ||
First reduce your program to a minimal test case: keep removing things while the program continues to exhibit this difference. | First reduce your program to a minimal test case: keep removing things while the program continues to exhibit this difference. | ||
Then characterize the behavior difference as best you can and add it to the [[Emulator | Then characterize the behavior difference as best you can and add it to the [[Emulator tests|test suite]]. | ||
Some emulators attempt to [[enhancement|enhance]] the games to make them appear more appealing than they did on the original NES. | Some emulators attempt to [[enhancement|enhance]] the games to make them appear more appealing than they did on the original NES. | ||
Revision as of 18:33, 15 December 2013
Compatibility is how well an emulator produces the same output as the original system when running a particular known program. Accuracy refers to how well an emulator produces the same output as the original system when running an arbitrary unknown program. An emulator can be highly compatible without being very accurate; Nesticle was this way back in the 1990s, running a wide selection of popular North American commercial games.
Accuracy cannot be measured directly. Compatibility with ROMs designed to test obscure behaviors and games relying on obscure behaviors is a good (though not perfect) predictor of accuracy.
In many cases, an emulator is more forgiving than the hardware, especially in when a program is allowed to write to a register. Nesticle, for instance, allowed writes to $2007 at any time, when the NES allows it only on or after line 241 of each frame (vertical blanking) or when $2001 & $1E == 0 (forced blanking). Most emulators allow the program to twiddle PPU registers immediately, while the NES PPU ignores most writes for the first frame after a reset. Inaccuracies like these led to inadvertent development of programs that the NES itself cannot run during the early years of NES homebrew.
Whenever you discover a difference in behavior between the NES and best-of-breed emulators (like Nintendulator and Nestopia), you can help emulators become more accurate. First reduce your program to a minimal test case: keep removing things while the program continues to exhibit this difference. Then characterize the behavior difference as best you can and add it to the test suite.
Some emulators attempt to enhance the games to make them appear more appealing than they did on the original NES.
References
- Topic on BBS
- Different grades of accuracy on BBS
- How to make a minimal test case (focuses on HTML, but applies to any virtual machine)
