Overclocking: Difference between revisions
mNo edit summary |
Ilyagredasov (talk | contribs) →Chart: Ymir changelog on github now lists a commit adding support for SH-2 overclock Tags: Mobile edit Mobile web edit Advanced mobile edit |
||
| (14 intermediate revisions by 6 users not shown) | |||
| Line 9: | Line 9: | ||
! scope="col"|Emulation Overclock | ! scope="col"|Emulation Overclock | ||
! scope="col"|Overclock levels | ! scope="col"|Overclock levels | ||
|- | |||
|[[Atari Jaguar emulators|Atari Jaguar]] | |||
|13.295 MHz/26.59 MHz | |||
|{{✓}} | |||
|{{✓}} | |||
|{{na}} | |||
|- | |- | ||
|[[Nintendo Entertainment System emulators|NES]] | |[[Nintendo Entertainment System emulators|NES]] | ||
| Line 48: | Line 54: | ||
|[[PlayStation emulators|PlayStation]] | |[[PlayStation emulators|PlayStation]] | ||
|33.8 MHz | |33.8 MHz | ||
|{{✓}}<ref name="kraut"> | |{{✓}}<ref name="kraut">See {{YouTubeVideo|HapnSOseDfw|here}}</ref> | ||
|{{✓}} | |{{✓}} | ||
|66Mhz<ref name="kraut"/> | |66Mhz<ref name="kraut"/> | ||
| Line 55: | Line 61: | ||
|28.6 MHz* | |28.6 MHz* | ||
|{{✗}} | |{{✗}} | ||
|{{ | |{{Y}} | ||
|{{ | |{{?}} | ||
|- | |- | ||
|[[Nintendo 64 emulators|Nintendo 64]] | |[[Nintendo 64 emulators|Nintendo 64]] | ||
| Line 75: | Line 81: | ||
|{{✓}} | |{{✓}} | ||
|{{na}} | |{{na}} | ||
|- | |||
|[[Nintendo Switch emulators|Switch]] | |||
|1020 MHz (CPU), 768 MHz (GPU), 1600 MHz (RAM) | |||
|{{Y}} | |||
|{{Y}} | |||
|1785 MHz (CPU), 921 MHz (GPU), 2133 MHz (RAM) | |||
|- | |- | ||
|} | |} | ||
| Line 81: | Line 93: | ||
==MAME== | ==MAME== | ||
By default [[MAME]] allows you to change the clock speed of the systems it emulates (including consoles) to anything between 50% to 250% of the original clock speed, the only requirement is that you enable cheats for that game/system. | By default [[MAME]] allows you to change the clock speed of the systems it emulates (including consoles) to anything between 50% to 250% of the original clock speed, the only requirement is that you enable cheats for that game/system. | ||
==Atari Jaguar== | |||
Overclocking is [https://forums.atariage.com/topic/109944-overclocked-jaguar/ possible on real hardware]. [[BigPEmu]] supports the clock scale and Blitter speed changing under speed settings. | |||
==NES== | ==NES== | ||
Overclocking is possible on real hardware, but doing so also speeds up the audio unless you're using a special hardware mod like the HiDefNES which does allow for overclocking without changing the audio pitch<ref name="HiDefNESoverclock"> | Overclocking is possible on real hardware, but doing so also speeds up the audio unless you're using a special hardware mod like the HiDefNES which does allow for overclocking without changing the audio pitch<ref name="HiDefNESoverclock">See {{YouTubeVideoTime|QnQuBN3iYVA|248|here}}</ref>. | ||
[[FCEUX]] as of 2.2.3 includes an overclocking option which works by adding additional scanlines to the PPU loop. This method doesn't cause audio distortion. It is found under Config > Timing. | [[FCEUX]] as of 2.2.3 includes an overclocking option which works by adding additional scanlines to the PPU loop. This method doesn't cause audio distortion. It is found under Config > Timing. | ||
| Line 111: | Line 126: | ||
The first version of the chip, commonly referred to as simply "Super FX", is clocked with a 21 MHz signal, but an internal clock speed divider halves it to 10.5 MHz. Later on, the design was revised to become the Super FX GSU-2; this, unlike the first Super FX chip revision, is able to reach 21 MHz. | The first version of the chip, commonly referred to as simply "Super FX", is clocked with a 21 MHz signal, but an internal clock speed divider halves it to 10.5 MHz. Later on, the design was revised to become the Super FX GSU-2; this, unlike the first Super FX chip revision, is able to reach 21 MHz. | ||
The SFX chip can be overclocked on real hardware or emulation with fewer issues than overclocking the CPU. However, tests have shown that overclocking can increase the speed of the game, in addition to increasing the frame rate and removing slowdown.<ref name="Dragon50hztest"> | The SFX chip can be overclocked on real hardware or emulation with fewer issues than overclocking the CPU. However, tests have shown that overclocking can increase the speed of the game, in addition to increasing the frame rate and removing slowdown.<ref name="Dragon50hztest">See {{YouTubeVideo|tfNI3HpUt-4|here}}</ref> | ||
{| class="wikitable" style="text-align:center;" | {| class="wikitable" style="text-align:center;" | ||
| Line 216: | Line 231: | ||
==Sega Genesis== | ==Sega Genesis== | ||
The original hardware can be overclocked leading to faster/smoother gameplay. | The original hardware can be overclocked leading to {{YouTubeVideo|SVrElANZg2M|faster/smoother gameplay}}. | ||
Most Genesis emulators don't allow overclocking. The [[Genesis Plus GX]] developer, for instance, says that implementing overclocking is "not easy to add without potentially break other things. <ref>https://code.google.com/p/genplus-gx/issues/detail?id=223</ref> | Most Genesis emulators don't allow overclocking. The [[Genesis Plus GX]] developer, for instance, says that implementing overclocking is "not easy to add without potentially break other things. <ref>https://code.google.com/p/genplus-gx/issues/detail?id=223</ref> | ||
But recently, Genesis-Plus GX libretro core now supports CPU overclocking by up to 500%. <ref>https://docs.libretro.com/library/genesis_plus_gx/#emulation-hacks</ref> | |||
[http://aamirm.hacking-cult.org/www/regen.html Regen] allows overclocking in the dev build version.<ref>http://segaretro.org/Regen</ref> Games with sprite flicker, like Altered Beast, and games with some slowdown, like Rambo III or Mega Man: The Wily Wars, play perfectly with Regen's "Overclock M68000" setting at 732 (1.5x original speed). The game speed and audio are unaffected by overclocking. | [http://aamirm.hacking-cult.org/www/regen.html Regen] allows overclocking in the dev build version.<ref>http://segaretro.org/Regen</ref> Games with sprite flicker, like Altered Beast, and games with some slowdown, like Rambo III or Mega Man: The Wily Wars, play perfectly with Regen's "Overclock M68000" setting at 732 (1.5x original speed). The game speed and audio are unaffected by overclocking. | ||
| Line 228: | Line 244: | ||
==3DO== | ==3DO== | ||
[[Phoenix (emulator)|Phoenix]] and standalone Windows version of [[4DO]] allows up to 4.0/400% of the original 3DO clock speed, making some low frame rate titles such as [[wikipedia:Doctor_Hauzer|Doctor Hauzer]] and [[wikipedia:Killing_Time_(video_game)|Killing Time]] more playable. Also possible to overclock CPU in [[ | [[Phoenix (emulator)|Phoenix]] and standalone Windows version of [[4DO]] allows up to 4.0/400% of the original 3DO clock speed, making some low frame rate titles such as [[wikipedia:Doctor_Hauzer|Doctor Hauzer]] and [[wikipedia:Killing_Time_(video_game)|Killing Time]] more playable. Also possible to overclock CPU in [[Opera]]<ref>https://docs.libretro.com/library/opera/#core-options</ref> - a [[libretro]] fork of 4DO (in options in core's quick menu after game launch, up to 4.0/50.00Mhz). | ||
The possibility of this function to break games (like incorrect physic and unplayable speed) is unknown. | The possibility of this function to break games (like incorrect physic and unplayable speed) is unknown. | ||
| Line 237: | Line 253: | ||
==Xbox== | ==Xbox== | ||
On real hardware some people | On real hardware some people change Xbox CPU with Tualatin Pentium III and upgrade RAM to 128MB (just like [[Development Kits]]) for {{YouTubeVideoTime|c66hfqw4SKc|456|low frame rate games like Half-Life 2}}. | ||
For emulators, it's possible to use 128MB RAM and also overclock emulated CPU thanks to this [https://github.com/xemu-project/xemu/pull/1467 pull request] for xemu. | |||
==See also== | |||
* [[Modding consoles/flashcarts]] | |||
==References== | ==References== | ||