Frame: Difference between revisions
m (The options menu runs at 60FPS too.) |
mNo edit summary |
||
| Line 6: | Line 6: | ||
==Framerate== | ==Framerate== | ||
The ''Pikmin'' games contain complex areas and several objects, more notably, the [[Pikmin family|Pikmin]] themselves, with 100 of them being able to stay on-screen at once. In order for the console to process the world's logic and render all of its elements at a steady speed, it cannot render at a large framerate. ''[[Pikmin (game)|Pikmin]]'' and ''Pikmin 2'' run at 30 frames per second, as do their [[New Play Control!|remakes]]. The exception to this is the European [[region|version]] of ''Pikmin'', which runs at 25. ''Pikmin 3'' | The ''Pikmin'' games contain complex areas and several objects, more notably, the [[Pikmin family|Pikmin]] themselves, with 100 of them being able to stay on-screen at once. In order for the console to process the world's logic and render all of its elements at a steady speed, it cannot render at a large framerate. ''[[Pikmin (game)|Pikmin]]'' and ''[[Pikmin 2]]'' run at 30 frames per second, as do their [[New Play Control!|remakes]]. The exception to this is the European [[region|version]] of ''Pikmin'', which runs at 25. The more advanced [[Wii U]] allows ''[[Pikmin 3]]'' to run at 60 frames per second. Strangely, the [[Menu#Options|options menu]] in ''Pikmin 2'' runs at 60 frames per second as well. | ||
Should the console have to process a large amount of instructions, it may fail to do all of them in a single frame, needing to extend the duration of the frame until everything is concluded. If this happens over a large amount of time, it can be noticed by the player. An example would be the landing sequence in ''Pikmin 3'', which oftentimes slows down the [[cutscene]], but not in a way that negatively impacts gameplay. | Should the console have to process a large amount of instructions, it may fail to do all of them in a single frame, needing to extend the duration of the frame until everything is concluded. If this happens over a large amount of time, it can be noticed by the player. An example would be the landing sequence in ''Pikmin 3'', which oftentimes slows down the [[cutscene]] visibly, but not in a way that negatively impacts gameplay. | ||
==See also== | ==See also== | ||
Revision as of 16:20, April 9, 2015
|
This article or section is in need of more images. Particularly: |
A frame is the primary unit of time in a Pikmin game's logic routine. Every frame, the game's world is updated, and the screen is redrawn to reflect the current state of the game. Frames "tick" at a regular interval, in order to provide a seamless stream of images that form the game's video. Processing cannot happen between two frames, meaning that an object's state can only be updated once per frame. Hence, the interval between two frames needs to be low enough to provide a smooth transition between an object's states over time (such as the position in the world map of a moving object), but high enough that the console can keep up with the speed.
In tool-assisted superplays, some tricks or glitches need to be "frame-perfect", meaning there is a one-frame window in which an outcome can happen. This makes them quite hard or impossible to perform consistently in real time.
Framerate
The Pikmin games contain complex areas and several objects, more notably, the Pikmin themselves, with 100 of them being able to stay on-screen at once. In order for the console to process the world's logic and render all of its elements at a steady speed, it cannot render at a large framerate. Pikmin and Pikmin 2 run at 30 frames per second, as do their remakes. The exception to this is the European version of Pikmin, which runs at 25. The more advanced Wii U allows Pikmin 3 to run at 60 frames per second. Strangely, the options menu in Pikmin 2 runs at 60 frames per second as well.
Should the console have to process a large amount of instructions, it may fail to do all of them in a single frame, needing to extend the duration of the frame until everything is concluded. If this happens over a large amount of time, it can be noticed by the player. An example would be the landing sequence in Pikmin 3, which oftentimes slows down the cutscene visibly, but not in a way that negatively impacts gameplay.