138
edits
Changes
Jump to navigation
Jump to search
Updated N64 timing issues section to reflect new developments
* Game physics not working properly due to being tied to framerate. A good example is Donkey Kong 64, which is programmed to boost the character's speed and momentum proportional to in-game lag (most likely to make up for the game's frequent framerate drops), which can be exploited for certain glitches and sequence breaks on real hardware. Emulators currently run the game too well and with too little lag, making most of these tricks impossible to pull off.
* Possibly the most affected game is Knife's Edge, which runs like it's on permanent fast-forward, making it all but unplayable. Messing with timing-related settings such as CounterFactor can mitigate this somewhat, but nowhere near enough to fix the issue.
Fortunately, tackling these problems has recently become a core focus of development in some N64 emulators, and attempts are underway to improve the situation. Ares currently has the most accurate timings overall, and already runs Earthworm Jim 3D's demos much better than other emulators. Meanwhile, m64p has recently pushed various timing-related commits aimed at improving accuracy, and as a result it may now be the only emulator that runs Donkey Kong 64 properly. As these efforts progress, it should be noted that a side-effect of improved timings may be greater in-game lag. This should not be seen as the emulator becoming slower, but rather the emulator behaving exactly like real hardware does, as many N64 games were notorious for framerate drops.
==Peripherals==
