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
In theory, what MIGHT work to fix it temporarly is: 1) use only the mission's save system and avoid user saves; 2) reloading the game as soon as the problem occurs.
It might have something to do with the game's engine, it might be that this mission stresses the engine to much, who knows, BIS was not exactly forthcoming with the explanations.
The other option is that there is something wrong with the mission' scripting. Anyway, it would seem that the author himself doesn't have a clue so I would not count on a fix anytime soon. Sadly, I might add as it's the best mission outthere, minus the bugs.