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
And the only time I encounter the problem you mention is when talking to other mercenaries in Mike's Bar, and it isn't a big deal if you give them time to 'settle down'.
Still, better FC2 than the sequels.
Now I understand why this has been happening, since typical graphics cards didn't go that high in framerate when the game came out and therefore only a small amount of people could get this kind of error.
As far as I know the smaller the amount of data for the physics engine inbetween frames (less time in milliseconds to gather data), the more inacurate it gets - which explains what the framerate has to do with the movement glitches.
It's like pointing the direction with a stick - the shorter it is, the less you can tell the exact direction.