Changes

The first is the virtual FPS. If this is running at 60/60 then the emulator is running at full speed. The second is the real internal FPS, which is whatever the game actually ran aton real hardware. Older consoels ran at 60 fps Most consoles use the following internal FPS based on region:*[[wikipedia:NTSC|NTSC]] (ntsc anywaysUSA, Japan). With the move to 3D: 60FPS*[[wikipedia:PAL_region|PAL]] (Europe, however, it took much Australia): 50FPSNote that in more cpu power to run games at 60fps. So few games actually ran at that. Most ran at 30fpsrecent consoles, and some at 20fpssuch as the [[GameCube emulators|GameCube]]/[[Wii emulators|Wii]], or even lower. Zelda Ocarina of Time for instance runs at 20fps. Star Fox ran below thatPAL can also run in 60FPS.

With the move to 3D, however, it took much more CPU power to run games at 60FPS. Most early 3D games run at 30FPS. Some run at even lower frame rates. The Legend of Zelda: Ocarina of Time, for instance, runs at 20FPS in NTSC regions, or 17 FPS in PAL regions. Star Fox runs below that. ==Slowdown== If you are experiencing a slowdown, it may be that the emulation is too intense for your system. When this happens, both the video and the sound experience slowdown. To counter act counteract this, you can enable speed hacks, use a less intensive emulator/settings or get a new CPUhardware. However, the slowdown may be part of the original game, and will be emulated. As such there is nothing that can be really done, short of reprogramming the game itself or emulating an overclock. When this slowdown occurs, the video will slowdown slow down but the audio will often continue at full speed. An  ==Overclocking=={{Main|Overclocking}}A way to counter real internal slowdown is to overclock the CPU of the emulated system. This, of course, requires a faster CPU to run the emulator. It may result in a smoother frame rate or unintended effects such as speeding up the entire game. It is very game and system dependent. Emulators that support this:*[[FinalBurn Alpha]]*[[RetroArch|Snes9x-Next]]*[[blueMSX]]*[[Mupen64Plus]] libretro core*[[Dolphin]]*bsnes-mercury*[[1964]] ==Speed Hacks==Using speed hacks can affect '''both''' types of FPS in emulators. Most of these are used to alter emulation, sacrificing accuracy for speed to help achieve 60/60FPS. Some speed hacks, however, can lower the internal FPS to raise the emulator's FPS; an example of this is in [[PCSX2]], known as EE cycle stealing, which reduces the clock speed of the virtual CPU used, the Emotion Engine.  There are a few game hacks that optimize game code in order to remove possible instances of in-game slowdown. There also exist a few speed hacks that increase a game's internal frame rate. They only function properly in emulators with real slowdown overclocked hardware. ==60 FPS Cheat Codes=={{Main|60 FPS Cheat Codes}} These are speed hacks in the form of cheat codes affecting the game's internal FPS for games running at 30 FPS to get them to play at 60 FPS. However, these are often game-specific and very prone to bugs considering many of the games weren't made with 60 FPS in mind. Notably, the walking speed and animations might play at double speed, which can cause some gameplay problems like this is for example, making a mission impossible to beat in Metal Gear Solid (ps1): Peace Walker because the enemies are too fast. [[Category:FAQs]]