Answered Plainly
Display: Text size:

Leer esta guía en español

X-COM: UFO Defense Runs Too Fast in DOSBox? The Cycles Fix

Short answer: It is the cycles setting — DOSBox’s speed number. The documented setup for this game caps it: cycles=auto limit 10000 in your dosbox.conf file. The usual cap is 8000, and going much higher than 10000 makes the game clock and the animations run too fast. One more thing this game needs that most do not: its two screens (the world map and the ground battles) like different speeds, so fine-tune while you play with the keys Ctrl+F11 (slower) and Ctrl+F12 (faster).

Honest labels, up front. Every number on this page is a documented starting point copied from the public sources in the Sources box — including one old number that is printed only to show why old numbers do not travel. None of these settings has been tested by playing the game for this page: the DisBox settings collection this page belongs to holds 0 settings verified by actual play.

These settings are part of the DisBox collection. DisBox OS — the system being built to run games with settings like these — is in the works; its interface comes first, so there is no finished OS to download yet.

The documented setup

The fullest written setup for this game is an AnandTech forum guide from a player who walked through the whole job. For the picture, his configuration-file lines are:

output=overlay
aspect=true
scaler=none

(Overlay output so the full-screen resolution works, aspect set to true so the picture is not stretched on a widescreen, and scaler none because he likes “the original blocky look.”)

For the speed, he writes: “the default CPU settings are a bit slow when I run it. To get the game running smoothly, I set ‘cycles’ to ‘auto limit 10000’. Normally the limit is set to 8000. But you don’t want to set it too high because then the game clock and animations run too fast.”

cycles=auto limit 10000

That one line is the heart of the fix: DOSBox may speed up and slow down on its own (auto), but never past 10000 cycles. If your copy of the game feels fine at the stock 8000 cap and only the clock races, raise the cap in small steps rather than jumping — the gap between “smooth” and “too fast” on this game is not wide.

Why one perfect number does not exist for this game

X-COM players on GOG’s forum — writing about the GOG edition of the game, which ships with DOSBox — make a point most setup pages skip: the world-map screen (the Geoscape, where the clock ticks) and the ground-battle screen (the Battlescape, where the cursor and the animations live) do not want the same speed. One player’s summary: there is “no proper default except auto,” and the real answer is to adjust in the moment with the hotkeys — Ctrl+F12 to speed up, Ctrl+F11 to slow down. Another says plainly that with the defaults the speed is “too large by both dosbox default and gog default,” and that different limits are needed for the two modes.

So treat auto limit 10000 as your home base, then nudge with the keys when you switch screens. That is not a workaround — it is how the players who wrote this game’s guides actually play it.

The other number you will see — and why to leave it alone

Search long enough and you will find a much bigger figure: an AnandTech reader reported “I have my cycles set to 50000, and X-Com runs well with that.” Read the date and the machine before copying it: that post is from the era of a 1.6 GHz dual-core computer. Cycles are not a unit of real-world speed — the same number means different speeds on different computers, because DOSBox spends your real processor’s power to fake the old one. A fixed 50000 that felt right on a 2008 machine can be a runaway on a modern one. The capped auto form exists precisely so the ceiling moves with your hardware.

That disagreement — 10000 capped, working well, versus 50000 fixed, also working well on its own machine — is printed here the way the sources give it. It is not two people being wrong. It is the same game on different computers, and it is why this page leads with the cap and the hotkeys instead of one magic number.

Sound settings, briefly

No X-COM-specific sound fault is documented in the sources read for this page, so the page prints no special sound recipe. Use DOSBox’s standard Sound Blaster settings — sbtype=sb16, address 220, IRQ 7, DMA 1 — and set the game to match. The site’s guide Sound Blaster Settings in DOSBox: IRQ 7, DMA 1, Address 220 explains what those three numbers are.

The one-minute version: Set cycles=auto limit 10000. If a screen still feels wrong, adjust live — Ctrl+F11 slower, Ctrl+F12 faster. Ignore giant fixed numbers copied from old forum posts; they were tuned on old computers.

Sources

AnandTech Forums — “Setting up X-COM: UFO Defense” (2012) — the display block (output=overlay, aspect=true, scaler=none) and the cycles line, with the stock 8000 limit named and the too-fast warning. https://forums.anandtech.com/threads/setting-up-x-com-ufo-defense.2218181/

GOG.com forum (X-COM series) — “Framerate Problem in Dosbox” — GOG-edition players on the two screens wanting different limits, the hotkey answer (Ctrl+F11 / Ctrl+F12), and the complaint that shipped defaults run too large. https://www.gog.com/forum/xcom_series/framerate_problem_in_dosbox

AnandTech Forums — “Using DOSBox” — the fixed 50000 cycles report, printed above with its era and machine attached (a 1.6 GHz dual-core) so it is not copied out of context. https://forums.anandtech.com/threads/using-dosbox.222422/

DOSBox (dosbox.com) — “DOSBox v0.74-3 Manual” — what cycles, auto, and limit mean, and the Ctrl+F11 / Ctrl+F12 speed keys. https://www.dosbox.com/DOSBoxManual.html

Checked November 7, 2026

Related guides: Game Runs Too Fast in DOSBox? Fix the Cycles, DOSBox Mouse Too Fast? The Sensitivity Fix, Prince of Persia DOSBox Cycles and Ultima VII in DOSBox.