Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
http://30vs60.com/
So this is like a game from the 90s where the game clock was directly tied with the cpu frequency? (if you had double the frequency of the cpu it was made for - the in game time is twice as quick.)
This is absurd, why would the rendering engine have anything to do with the in-game clock?
Really bad coding on the developers' side.
Most C&C got NO FPS limit.
TW got one since the EA devs overtook the engine from Westwood and replaced code with theire own so they can work with already existing libarys and so on.
Meaning TW is some hybrid of EA and Westwood code.
Such things lead to problems, one of it seemed to slow/speed the game.
I guess because of money reasons they decided to take the easy way and bound game speed to FPS.
That means.
15 FPS = 50% game speed
30 FPS = 100% game speed
60 FPS = 200% game speed
and so on
Thanks m8