Difference between revisions of "Frames per second"
(→Nintendo 64: This link doesn't work for me) |
m (; -> :) |
||
(21 intermediate revisions by 15 users not shown) | |||
Line 1: | Line 1: | ||
There are two kinds of "frames per second". | There are two kinds of "frames per second". | ||
− | The first is the virtual FPS | + | The first is the virtual/output FPS and the second is the '''real internal FPS''' which is whatever the game actually ran at. |
− | |||
− | |||
− | |||
− | With the move to 3D, however, it took much more CPU power to run games at 60FPS | + | Most consoles use the following output FPS based on region: |
+ | *[[wikipedia:NTSC|NTSC]] (USA, Japan): 60FPS | ||
+ | *[[wikipedia:PAL_region|PAL]] (Europe, Australia): 50FPS | ||
+ | Note that in more recent consoles, such as the [[GameCube emulators|GameCube]]/[[Wii emulators|Wii]], PAL can also run in 60FPS. | ||
+ | |||
+ | With the move to 3D, however, it took much more CPU power to run games at 60FPS internally, 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== | ==Slowdown== | ||
− | + | If you are experiencing a slowdown on emulation speed (lesser than 100%), it may be that the emulation is too intense for your system. When this happens, both the video and the sound experience slowdown. To counteract this, you can enable speed hacks, use a less intensive emulator/settings or get new hardware particularly the CPU. However, if the slowdown only affects the internal FPS (frames processed per second within the emulated system), it likely reflects the original game's behavior and accurately represents the limitations of the original hardware. In such cases, there is nothing can be really done for this, other than [[Overclocking|overclocking the '''virtual hardware''']] or [[Game_engine_recreations_and_source_ports|reprogramming the game itself]]. This type of slowdown often affects video while audio remains unaffected, and the displayed emulation speed will still be 100%. | |
− | If you are experiencing 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 | ||
==Overclocking== | ==Overclocking== | ||
{{Main|Overclocking}} | {{Main|Overclocking}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Speed Hacks== | ==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 | + | 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 30FPS/60VPS. Some speed hacks, however, can lower the internal FPS to raise the emulator's output 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 overclocked hardware. | 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 overclocked hardware. | ||
− | ==60 FPS | + | ==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 for example, making a mission impossible to beat in Metal Gear Solid: Peace Walker because the enemies are too fast. | |
− | : | + | [[Category:FAQs]] |
− | |||
− |
Latest revision as of 01:03, 9 May 2024
There are two kinds of "frames per second".
The first is the virtual/output FPS and the second is the real internal FPS which is whatever the game actually ran at.
Most consoles use the following output FPS based on region:
Note that in more recent consoles, such as the GameCube/Wii, PAL can also run in 60FPS.
With the move to 3D, however, it took much more CPU power to run games at 60FPS internally, 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.
Contents
Slowdown[edit]
If you are experiencing a slowdown on emulation speed (lesser than 100%), it may be that the emulation is too intense for your system. When this happens, both the video and the sound experience slowdown. To counteract this, you can enable speed hacks, use a less intensive emulator/settings or get new hardware particularly the CPU. However, if the slowdown only affects the internal FPS (frames processed per second within the emulated system), it likely reflects the original game's behavior and accurately represents the limitations of the original hardware. In such cases, there is nothing can be really done for this, other than overclocking the virtual hardware or reprogramming the game itself. This type of slowdown often affects video while audio remains unaffected, and the displayed emulation speed will still be 100%.
Overclocking[edit]
- Main article: Overclocking
Speed Hacks[edit]
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 30FPS/60VPS. Some speed hacks, however, can lower the internal FPS to raise the emulator's output 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 overclocked hardware.
60 FPS Cheat Codes[edit]
- Main article: 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 for example, making a mission impossible to beat in Metal Gear Solid: Peace Walker because the enemies are too fast.