Time Stretching is DxWnd’s Timing-tab feature for games that run at the wrong speed: it applies a multiplier to the clock the game reads, so a classic that sprints on a modern CPU can be slowed to its designed pace, and a dragging one can be hurried up. Our troubleshooting guide to games running too fast covers the symptom and the first checks; this deep-dive explains the mechanism properly — why old games lose time in the first place, why some respond to time stretching and others do not, and how to dial in a value without fooling yourself.
Why Old Games Tie Speed to Hardware
A game needs a clock: something that tells it how much time passed since the last frame so it can move the world by the right amount. Classic games answered that need in two broad ways. Timer-based games read the system clock — they ask Windows what time it is and pace themselves by the answer. Frame-locked games skip the clock and simply run one step of logic per frame drawn, assuming frames arrive at the rate of the era’s hardware and displays.
Modern PCs break both contracts differently. A timer-based game on a fast machine is fine in principle — the clock still works — until its timing code meets timer behaviour that changed underneath it. A frame-locked game is in worse trouble: asked to draw as fast as possible, a modern GPU happily produces several times the intended frames per second, and the game world advances with every single one of them. The result is the famous fast-forward effect. Neither game is buggy; both are faithfully executing timing assumptions from a vanished hardware world.
What Time Stretching Actually Does
DxWnd sits between the game and the system, and among the things it can intercept are the calls by which the game learns the time. Time Stretching exploits that position: it presents the game with a scaled clock. Conceptually it is a multiplier — at a factor below 1.0, the game’s clock advances more slowly than real time, so a timer-based game that was racing now believes less time has passed and settles down; above 1.0, the game’s clock runs ahead, rescuing titles that crawl. The rest of your system keeps real time; only the game’s perception is stretched.
This is why time stretching is a Timing-tab matter and not a display option. It changes nothing about how frames are drawn — that is the video settings — it changes what the game thinks, which is the layer where timer-based speed actually lives.
Frame-Locked Games: The Ones That Shrug
Here is the honest limit every guide should state up front: a purely frame-locked game has no clock to stretch. If the world advances one step per rendered frame and the game never asks the time, scaling the clock changes nothing it cares about. For those titles the lever is the frame rate itself — pacing presentation so frames arrive at a sane rate — which is why the too-fast checklist sends you to check which kind of game you have before prescribing. Many real games are hybrids: logic on a timer, animation on frames, cutscenes on a third scheme entirely. Those respond partially — gameplay slows while a cutscene refuses to — and partial response is itself diagnostic information about how the game is built.
Dialling In a Value: Small Steps, Same Scene
There is no universal correct factor, because the right correction depends on how far the game’s speed has drifted, and that varies by title and machine. The reliable method is boring and works: pick a repeatable scene — a character crossing a room, a timer counting down, a patrol walking its route. Start from no stretching and confirm the symptom. Apply a modest correction, retest the same scene, and compare against your memory of the intended pace or a known reference such as a one-minute timer. Adjust in small steps. Menus deserve a separate check from gameplay: menu animations are often frame-driven while the game world is timer-driven, so a factor that perfects one can leave the other odd, and you want to know which trade-off you are accepting.
Two cautions. First, more correction is not more better: overshooting below the true pace produces a game that wades, and the temptation to keep nudging is how profiles end up at strange values nobody can explain. Second, save the profile once a value works — per-game tuning is per-game, and the Timing settings live in the profile like everything else in the settings dialog.
A reference beats an impression. If the game has any real-time element — a mission timer, a countdown, a day cycle — time it against your phone’s stopwatch over a full minute at your candidate setting. A game that should take sixty real seconds and takes fifty-two is still running roughly fifteen percent fast, whatever your eyes told you, and now your next adjustment has a direction and a size. Two or three measured iterations usually land closer than ten unmeasured ones, and the measurements become part of the profile’s story when you share it.
The Audio Problem, Stated Honestly
Stretching the game’s clock does not stretch physics the game does not route through that clock — and audio is the usual casualty. Music and sound effects are often driven by their own playback machinery, untouched by the game’s sense of time. Slow the game and the soundtrack may keep its original tempo, drifting out of sync with the action; in cutscenes timed against their audio, voices can finish while lips keep moving, or the scene can wait in silence for a track that ended. This is not a defect in your settings and not always fixable from the Timing tab: it is the genuine limit of clock-level intervention. Many players accept slightly detached audio as the price of a playable pace; in cutscene-heavy games it is worth weighing before you commit to heavy stretching.
Where This Fits
Speed complaints arrive at the troubleshooting hub and split by mechanism: frame-driven speed goes to presentation pacing, clock-driven speed comes here. If you are unsure which you have, the symptom-first walkthrough is our too-fast guide. And when the pace is finally right, note the factor in your head as part of the game’s recipe — it belongs to this title on this machine, and it is one of the first things worth recording when you export the profile for safekeeping.