Difference between revisions of "Talk:Higan"
| Line 7: | Line 7: | ||
Due to this, cycle accurate emulators are almost never perfect, regardless of the fact that some of them can pass 100% of accuracy tests or can run all released games. Accuracy tests don't always show 100% of what the system can do, and in some cases, such as the 6502, has completely unpredictable opcodes even on real hardware that cannot reasonably be emulated outside of an FPGA. higan's SNES core, for example, has issues with some Super Mario World ROM hacks, where bugs show up in real hardware, but not with higan. --[[User:Syboxez|Syboxez]] ([[User talk:Syboxez|talk]]) 19:39, 12 October 2017 (EDT) | Due to this, cycle accurate emulators are almost never perfect, regardless of the fact that some of them can pass 100% of accuracy tests or can run all released games. Accuracy tests don't always show 100% of what the system can do, and in some cases, such as the 6502, has completely unpredictable opcodes even on real hardware that cannot reasonably be emulated outside of an FPGA. higan's SNES core, for example, has issues with some Super Mario World ROM hacks, where bugs show up in real hardware, but not with higan. --[[User:Syboxez|Syboxez]] ([[User talk:Syboxez|talk]]) 19:39, 12 October 2017 (EDT) | ||
| + | :I once read a passage from a textbook emphasizing the difference between the terms "accuracy" and "precision". Accuracy is defined as being as close as possible, while precision is to be exact, not 99.999% or something. Of course, cycle accuracy isn't perfect, no matter how byuu and company strive for it. [[User:Blakegripling ph|Blakegripling ph]] ([[User talk:Blakegripling ph|talk]]) 22:21, 13 October 2017 (EDT) | ||
Revision as of 02:21, 14 October 2017
Can we create an Template:HiganVer page ? I don't find where to do it. Thanks
Don't feel like starting an editor war, so accuracy classification discussion of bgba probably should be here.
Cycle accuracy is all about emulating the timing of the system perfectly. Cycle accuracy doesn't mean perfect emulation by any means. Not even FPGA emulation (or as it's called in the Emulation Accuracy page, chip accurate emulation) is always perfect, as unless each proprietary chip in the system is decapped and perfectly implemented, the developer has to take some liberties and guesses as to how something works. This applies even moreso to software based emulation since trying to achieve chip accurate emulation on modern hardware is simply not feasible. If you'd like to see why, just try simulating FPGANES on a computer and see how fast it is.
Due to this, cycle accurate emulators are almost never perfect, regardless of the fact that some of them can pass 100% of accuracy tests or can run all released games. Accuracy tests don't always show 100% of what the system can do, and in some cases, such as the 6502, has completely unpredictable opcodes even on real hardware that cannot reasonably be emulated outside of an FPGA. higan's SNES core, for example, has issues with some Super Mario World ROM hacks, where bugs show up in real hardware, but not with higan. --Syboxez (talk) 19:39, 12 October 2017 (EDT)
- I once read a passage from a textbook emphasizing the difference between the terms "accuracy" and "precision". Accuracy is defined as being as close as possible, while precision is to be exact, not 99.999% or something. Of course, cycle accuracy isn't perfect, no matter how byuu and company strive for it. Blakegripling ph (talk) 22:21, 13 October 2017 (EDT)
