As it says, this is what has been ruining people's days for days. I made this video to help people like me before they destroy hours of campaign progress. This can happen on Xbox, Steam, and Windows. The "bug" that breaks the game is being signed in twice on the same account.

For Xbox users, be very careful with using the quick resume feature. If you have been playing a different game that is coop, and multiple people were signed in on the same account, when you load up Halo you will still be double signed in. If you load your save game at that point, it will break it. Also, make sure you're not remotely signed in somewhere else, I read earlier someone was signed in on their Xbox then started playing on their PC and signed in there, and ended up breaking their game.

Multiple users have been reporting that during some cutscenes, loading screens, and after the end credits scene, your game can crash or glitch out and it will also corrupt your save file. So I suppose I should have titled this "One of the Causes".

Possible fix for some players with corrupted save files: If you are playing the game across multiple devices, like Xbox and PC, two PCs, or two Xboxes, it is possible to recover your save files. If your game becomes corrupted on one of your devices, turn off cloud syncing or just disconnect from the internet on your other device and start the game offline (if you are using the Xbox app on PC just disconnect from the internet, and you will have to set that PC to be able to play offline). Then load the game in from local files. Then, connect to the internet or turn cloud syncing back on and sync. When you log back into the account on the originally corrupted device, it should sync to the cloud and overwrite the corrupted file. Shout out to Liam Downer in the comments for figuring this out.

Update: From what I have read elsewhere, this could also be what causes the bug in multi-player matches where you spawn in under the map, along with giving you other multi-player troubles. Just a bunch of fun bugs all around with this one
Updated Update: It does... [ Ссылка ]

A written description of the problem here -
So this seems to happen when a new input is detected, like a Bluetooth controller, or if your controller disconnects and you reconnect it. If you click on the sign-in when it pops up, you will be signed in twice on the same account. This is what breaks the game, and will ruin any campaign you are in, load, or start. Just closing the prompt will not ruin your game, and you can keep playing with a controller. This will happen if you are already double signed in when you start the game, as well. To check if you are double signed in, start a new campaign. When the loading bar pops up it should say CAMPAIGN 1(1). If it says CAMPAIGN 2(2), your campaign is fucked. If it doesn't even let you start a new campaign, like in the video, then you're probably double signed in. Also, this is what causes the flashing/strobing lights in campaigns, the floating camera/disappearing chief bug on load ins, and if you do this in game you may well enter an infinite death loop. So DONT SIGN IN AGAIN OR PRESS LET'S GO.

свернуть