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
https://steamcommunity.com/app/548570/discussions/0/1651044588035155801/
That would make sense, this is exactly how I got the issue.
I wouldn't hear Marshall after so my first reflex was to reload and play the sequence again. Jokes on me.
Now I'll just wait for a fix I presume.
This is a mission scripting issue, can't say who is at fault here but I know this:
Just Cause 4 had a much worse release... Avalanche has a tradition to rush games out with playthrough stoppers or savegame corruption (which I had, crash whenever I'd load in again).