Ak ste sa niekedy pokúšali získať moderný počítačový systém a vyskúšať si moderný systém, pravdepodobne ste boli šokovanírýchly Hra prebehla. Prečo staré hry nemajú kontrolu nad moderným hardvérom?
Dnes sme vám ukázali, ako spustiť starší softvér na moderných počítačoch; dnešná otázka a odpoveď je pekná kompliment, ktorý sa zaoberá tým, prečo niektoré staršie softvéry (konkrétne hry) nikdy nefungujú správne, keď sa pokúsite spustiť ich na moderný hardvér.
Dnešná relácia otázok a odpovedí sa k nám pridelí zdvorilosťou SuperUser - podskupiny Stack Exchange, skupín webových stránok týkajúcich sa otázok a odpovedí.
Otázka
Čítačka SuperUser TreyK chce vedieť, prečo staré počítačové hry rýchlo blázonia na nový hardvér:
I’ve got a few old programs I pulled off an early 90s-era Windows computer and tried to run them on a relatively modern computer. Interestingly enough, they ran at a blazing fast speed – no, not the 60 frames per second kind of fast, rather the oh-my-god-the-character-is-walking-at-the-speed-of-sound kind of fast. I would press an arrow key and the character’s sprite would zip across the screen much faster than normal. Time progression in the game was happening much faster than it should. There are even programs made to slow down your CPU so that these games are actually playable.
I’ve heard that this is related to the game depending on CPU cycles, or something like that. My questions are:
- Why do older games do this, and how did they get away with it?
- How do newer games not do this and run independently of the CPU frequency?
Takže aký je príbeh? Prečo presne skriptovia v starých hrách plávajú po obrazovke tak rýchlo, že hra sa stáva nehrateľnou?
Odpoveď
Príspevok SuperUser JourneymanGeek to rozdelí:
I believe they assumed the system clock would run at a specific rate, and tied in their internal timers to that clock rate. Most of these games probably ran on DOS, and were real mode (with complete, direct hardware access) and assumed you were running a iirc 4.77 MHz system for PCs and whatever standard processor that model ran for other systems like the Amiga.
They also took clever shortcuts based on those assumptions including saving a tiny bit of resources by not writing internal timing loops inside the program. They also took up as much processor power as they could – which was a decent idea in the days of slow, often passively cooled chips!
Initially one way to get around differing processor speed was the good old Turbo button (which slowed your system down). Modern applications are in protected mode and the OS tends to manage resources – they wouldn’t allow a DOS application (which is running in NTVDM on a 32-bit system anyway) to use up all of the processor in many cases. In short, OSes have gotten smarter, as have APIs.
Heavily based off this guide on Oldskool PC where logic and memory failed me – it’s a great read, and probably goes more in depth into the “why”.
Stuff like CPUkiller use up as many resources as possible to “slow” down your system, which is inefficient. You’d be better off using DOSBox to manage the clock speed your application sees.
Ak ste zvedaví, ako bol skutočný kód implementovaný v skorých počítačových hrách (a prečo sa tak veľmi zle prispôsobujú moderným systémom bez toho, aby boli v nejakom emulačnom programe), odporúčame tiež preskúmať toto zdĺhavé, ale zaujímavé rozdelenie proces v inej odpovedi služby SuperUser.
Máte niečo doplniť vysvetlenie? Zvuk vypnúť v komentároch. Chcete si prečítať viac odpovedí od iných používateľov technológie Stack Exchange? Pozrite sa na celý diskusný príspevok tu.
