Turbo Modes

The C64 Core has several Turbo Modes that will accelerate C64 programs. This page explains the difference between Warp and Turbo, speed gains and compatibility issues.

Turbo is not Warp

If you are using emulators like VICE you might have heard of “Warp” mode. This runs the whole emulation faster, but the emulated C64 inside still thinks it is running at standard speed. In Warp mode you get no or garbled sound and will not see every frame the C64 produces. But it is very compatible, because everything is sped up and still in synch with each other.

Turbo makes the CPU faster

The Turbo modes of the C64 Core make the 6510 CPU virtually faster. Usually it runs at approx. 1 MHz, Turbo increases that to 2, 3 or 4 MHz. The rest of the system stays at its standard speed. This would create problems with every software that is timing sensitive, for example floppy speeders that have exact cycle counts or any demo that tricks the VIC-II video chip into effects like sprites in border or very stable line colour changes.

Solution 1: C128 Mode

The Commodore 128 has the possibility to speed up the 6510 CPU to double speed, 2 MHz, at the price of losing sync with the VIC-II videochip. At 2 MHz (in C64 mode) the screen only shows the current background color. The C128 added an extra register at $D030 that allows turning the CPU to double speed (and the screen “off”) and back again. Some games use this mode by turning on 2Mhz as soon as the last line with content on the screen is displayed, and off again when the first line would be drawn. Basically the screen is “off” about 1/3rd of the time without you noticing it because it would have displayed only the background colour anyway. This gives you, on average, a 125% speed but actually even more in some games because you can bundle math-intensive code in the time you have the Turbo turned on, while interrupt-driven routines will not gain visible speed. Turning on C128 mode with the 2x, 3x or 4x multiplier is compatible with practically all software written for the C64 and gives you faster code with every C128-optimized game for free and faster than on a real C128. In theory, a maximized use of the “border time turbo” with the 4x mode gives you a 2x average: 2/3rd of the time the C64 runs at 1 MHz, 1/3rd at 4 MHz.

Solution 2: Smart Mode

Because the Core does not need to blank the screen when the 6510 is running at a higher speed (different to the C128), there is an additional Smart Mode which slows down the CPU only when you access disk drives. So it will not speed up loading (you still need JiffyDOS), but it will make everything run faster when the drives are not accessed. This mode breaks MANY games and demos. When their updates are not timed with the 50 Hz screen updates, the whole logic will run faster, making games sometimes unplayable. You will also see a lot of flickering and even crashes. Turn on this mode if you use utilities, applications (Print Shop, Geos) or 3D games that are tied to the 50 Hz clock (for example Driller).

The Turbo key (Caps Lock)

(Starting with Alpha 22X2) You can instantly turn Turbo on and off with the Caps Lock key. The LED indicates whether Turbo is on or not. With Caps Lock on you are in Smart 4x mode, the fastest mode available. With Caps Lock off you will be in the mode selected in the Turbo Menu, which could be a C128 mode or just Turbo off.

Recommendations

You usually can keep C128 mode with 4x on without compatibility issues and add the Turbo key whenever you need that extra speed.

Here are some Links to Games hacked to work well with Smart Mode:

Amaurote 64

Elite Compendium

Thrust Gold

Games you have to find yourself on the Internet, that had supported C128 mode already in the original release: Uridium+ (and later games by Andrew Braybrook), Test Drive II, Grand Prix Circuit, Project Stealth Fighter.

Finally on my private webpage I point out to my enhanced versions of some Lucasfilm Games stuff and intend to put more games there in the Winter.