In 2014 343i/Halo Studios released Halo: The Master Chief Collection in a completely broken state.
If those most actively on the web (and seemingly least active in game) are to be believed the MCC has been fixed and now actually works. That is not the case as there are many outstanding issues that I will remind you of.
Unfortunately I don't have any good clips of the client crashing on my Xbox. The usual symptom is the video will freeze and the audio will continue for a few seconds. I can still talk to people in voice chat and I can still hear them. Then the audio fifo will stop being filled at the correct rate and it will start repeating snippets of audio, and the the audio fifo will stop getting new data and a fraction of a second of audio is looped until the Xbox returns to dashboard (until around 2023 the Xbox would actually power off instead of returning to dashboard, I suspect that the Xbox kernel team managed to figure out how to reset the state of whatever was causing the “solution” to be a poweroff). If the match ends before you can open the game and get into matchmaking and rejoin you will be banned from matchmaking. Before they added the rejoin option a matchmaking ban was guaranteed! It's an improvement, but it's still shit
Since the Xbox kernel/OS team managed to fix the poweroff problem I have tried to record a few clips of the client crashing, however these clips do not capture what you experience at the time, and the files at the point of the game crashing are usually corrupted/broken in some way. To actually capture what a client crash looks like correctly I think you need external capture equipment rather that relying on the Xbox's built in clip recording ability.
I do have a clip of attempting to rejoin a match, where you can see the beautifully and competently made network model of the 343i/Halo Studios as the game struggles and takes a long time to “[Connect] to the transport service”. Because in the age of multi-megabit (and even multi-gigabit!) residential internet connections and fast computers these wirth's law/jevon's paradox enthusiasts have managed to make a software/network model that takes several seconds to connect.
Due to how effectivily cheaters are able to break the game, and the fact that this started after PC support was added: I have often wondered if this is not the game crashing on it's own, but a crash triggered by a malicious player that sends a magic death packet or something.
I have so many examples of server crashes I broke it out into it's own page
Server crashes have been becoming more and more frequent, sometimes it feels like literally every game results in a server crash.
Again, like client crashes, due to how effectivily cheaters are able to break the game, and the fact that this started after PC support was added: I have often wondered if this is not the server crashing on it's own, but a crash triggered by a malicious player that sends a magic death packet or something.
H2a has numerous severe issues. Unfortunately I don't have clips of many of them. I have recorded clips, and have my Xbox set to save them locally only, however after updates sometimes the Xbox will delete the local clips without warning (very competent design!) and I have lost many. I have included clips of things I do have
This clip is from 2015, BUT THIS STILL HAPPENS (usually just for me, not the entire team). Ten fucking years and they have not been able to fix this. Not only does this happen, sometimes you respawn as the only player on the map, with apparently the match still going on, I just can't see it. I can walk around and sometimes explosions go off and you hear something and then I suddenly die. The networking is totally fucked!
Killcams in H2a are totally fucked as seen above.
I don't have many good clips for this, but you can kind of see it in the broken killcams clip but the sound in H2a is frequently very broken. I don't know if that is the network model's fault or the sound programmers. But sometimes you only hear a portion of the effects that should be playing e.g. you only hear light objects hitting the ground when a major explosion goes off silently.
This is very frequent, but I don't have the energy to go hunting through my clips to find an example right now. When you are playing a multi-round game (e.g. 1 flag CTF) very frequently the end of round music that plays near the end of the first round will never stop playing. Sometimes in hour+ long CGB games the music will seemingly start playing for no reason and just keep going.
When 343i/Halo Studios decided to add AUTOMATIC betrayal booting to Halo 1 it totally broke the game. If you are driving a vehicle and accidentally betray a teamate the teammate you betray has no option of forgiving you, you are just automatically kicked from the game! (provided you betray 2 or 3 over the course of the match). But that is not the worst part.
The worst part is this has enabled griefers that abuse you by shooting you (without killing you) getting you more easily killed when you encounter the enemy team. If you shoot them back and draing their shields/health sufficiently they will kill themselves with a grenade, and since you gave them sufficient damage, it counts as a betrayal and you get booted. I don't have any easily accessible clips of this. But it gets worse.
There are groups of people that know about this betrayal booting and the matchmaking ban in h1 and will co-operate together to get you trapped and bait you into betraying them
Fucking degenerates.
If you follow Halo Studios closely you may remember the now deleted blog where they announced that they were updating MCC and licensing Unreal to remake the menus. Ever since then the menus have been incredibly slow, especially the pause menu, taking up to a second to open up sometimes. There are numerous ways that the menus can break. Here is one clip that happened relatively recently. I opened up the Xbox's side menu thing (hit the Xbox button on the controller) and Halo Studios in their infinite wisdom decided that should open up the pause menu. And they are very competent and understand multithreading/race conditions! Anyways this lead to the game (not pause) menu breaking once the match ended.
It's is admitedly not as bad at launch, with random broken strings showing up. But it still sucks ass and is incredibly slow even when it is working at it's best. In that blog post I mentioned earlier the developers were talking about how hard it was to get it to run on a console with 8 FUCKING GIGABYTES OF RAM. THE FUCKING MENU! DEAR FUCKING GOD!
Also I don't have a clip of it right now, but the Custom Game Browser (CGB) list is totally fucked. Say you sort by latency, then you either trigger a manual refresh, or you fail to enter the game and it automatically refreshes when you leave the entry queue. After the refresh the game list will be randomly sorted and you need to navigate the cursor up to the header and move it over to latency (which is the last (FURTHEST AWAY) column) and select it TWICE (once to sort by highest latency, then again to sort with the lowest latency). After the refresh the UI shows that it is sorted by latency BUT IT IS NOT and you have to smash the sort thing again.
This is rare and has not happended to me in a while, but sometimes when the match begins in Halo 2 when you first spawn you are unable to move until you die. It effects almost my entire team in this clip.
Sometimes in matchmaking you will get stuck in an infinite loading screen.
Sometimes in reach the textures would be fucked. This hasn't happened to me in a while, but I rarely play reach so maybe it still happens.