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
Doesn't change the fact that its stupid. There just needs to be a system in place that waits for the other player to finish loading. all the games except halo 1 and 2 have this system.
Besides, odds are there's something in the programming of CE and 2 that makes forcing the host to pause before the mission start simply unfeasible. Odds are they tried and found that it causes something else to break, so rather than redo the entire code for CE and 2 Campaign - like they already did for the multiplayer maps - they just went "oh well" and moved on. Seriously, they didn't even bother to do cross-play for most of the Campaigns, so trying to fix an issue that has an easy workaround doesn't seem likely.
It's definitely an unfortunate problem, but because the solution only costs Microsoft more money they're not going to implement it, especially for a couple of 20+ year old games.