Editing Frames per second

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
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/output FPS and the second is the '''real internal FPS''' which is whatever the game actually ran at.
+
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 at on real hardware. Most consoles use the following internal FPS based on region:
 
 
Most consoles use the following output FPS based on region;
 
 
*[[wikipedia:NTSC|NTSC]] (USA, Japan): 60FPS
 
*[[wikipedia:NTSC|NTSC]] (USA, Japan): 60FPS
 
*[[wikipedia:PAL_region|PAL]] (Europe, Australia): 50FPS
 
*[[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.
 
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.
+
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==
 
==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 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 counteract this, you can enable speed hacks, use a less intensive emulator/settings or get a new CPU. 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 slow down but the audio will often continue at full speed.
  
 
==Overclocking==
 
==Overclocking==
 
{{Main|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 of course. 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==
 
==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 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.  
+
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 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.

Please note that all contributions to Emulation General Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Emulation General Wiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: