> 2533274832149749;125:
> > 2533274913424309;2:
> > I like the new name. Halo: The Master Bugs Collection. Sounds just about right.
> >
> > Here’s what I have so far:
> > - HCEA: The objective markers doesn’t always appear in campaign, solo or co-op. Especially in earlier levels.
> > - HCEA: When using Plasma pistol, you can usually hear the gun charging sound when you didn’t even shoot the gun. Not game breaking, but annoying nonetheless.
> > - HCEA: Constant disconnection issue in co-op. If you and your co-op partner cannot move, that means the game lost it’s connection to server. Restarting checkpoint/mission doesn’t help. Had to quit.
> > - HCEA: Dead co-op partner could not respawn even though there’s no enemies/he’s not in combat. The only fix is to restart checkpoint.
> > - HCEA: Random controller disconnection. This is by far the worst, game-breaking glitch I found. If your controller disconnect 3-4 times during your co-op session, next time you reconnect, the party chat sound won’t be coming through the headset (it’ll be on TV instead). If it disconnect one more time, you will lose all control over your Xbox. The game won’t respond to any button presses on the controller. The game also will register whatever button you pressed last before the disconnection, and continuously doing that. In my case, it register the LS down, so my character is moving backward forever. Since we’re doing co-op and the progress is not save everytime we quit, my partner had to finish the level all by himself while I can only watch.
> > - HCEA: No progress saved when playing co-op. Not even for the host, which means we need to complete at least that level we’re on or we have to restart the whole level from beginning.
> > - HCEA: Difficulty getting into friend’s game session for co-op. Most of the time it’ll just say “Unable to connect to host” but sometimes it’ll say “Session full.”
> > - HCEA: When I was playing co-op Legendary on Two Betrayal, suddenly my Xbox is silent. There’s no sound coming from the game. After finishing that level, I force quit the game, launch again and it have sound back.
> > - H2A: Co-op session ended before we can even get into the game. You can join a session, see the loading screen for a few seconds, then you will see the blue Halo MCC loading screen, back to the main menu with the “Unable to connect to host” error message.
> > - H2A: There’s a bug when playing Legendary where the Iron skull is activated even though you didn’t manually activate it through the skull screen before starting the game. This make the game unnecessarily difficult as the skull will restart the whole mission if you die playing solo, or restart the checkpoint if you play co-op.
> > - H2A: The IWHBYD skull is bugged. Even after correctly following the “7 checkpoints” guide, there’s a fair amount of time it won’t appear, or in my case it’s there but not visible. So you need to just go to there the location of the skull is and hold RB while hoping you can pick it up. Works for me the second time I tried. Some peoples reporting you need to fight 7 waves of Elites before getting the achievement for the skull, but I personally get the achievement right after I picked it up.
> > - H2A: Game crashed occasionally after viewing a cutscene.
> > - H2A: When switching from the remastered cutscene to the classic one, the audio won’t come up until one seconds later.
> > - H2A: The game doesn’t properly hide your HUD, reticule etc before start playing a cutscene, so in most cases, you can sometime see your health bar, or reticule, or score (if you have it turned on) when viewing the cutscenes.
> > - H2A: Same glitch as HCEA where you cannot respawn properly even when there’s no enemy nearby.
> > - MP: After a match finish in Custom Game, there’s high chance your game will crash when it get to the lobby.
> > - MP: The UI would lag immensely when getting to the lobby after a match.
> > - MP: Just stuck at the matchmaking menu. No game found for any MP playlist I selected.
> > - Achievements: Some weren’t unlocking properly. Some unlock late (when it should unlock immediately) and some just stay at the “Done. Unlocking…” (which should be Xbox issue where it couldn’t sync your unlocked achievement(s) to XBL server.
> > - Playlists: The “Master Chief Saga” playlist is buggy. When I was playing HCEA on that playlist, the game just skip the “343 Guilty Spark” completely and just put me on “Two Betrayal”. When I go to the main menu and check, the game said I’ve completed “343 Guilty Spark”, but no achievement awarded for supposedly “completing” the level.
> > - Terminals: When unlocking the terminal in the game (in my case it’s HCEA and H2A), the Halo Channel app just froze. Sometimes it just stay on the loading screen forever, and when it does work, the video streamed in SD for around 10-20 seconds before going HD.
> > - Nightfall: Whenever I tried to watch the first episodes of Nightfall, it will just skip the episode and just give me the “Halo 2 Anniversary Documentary” instead.
> > That’s the bugs/glitches I’ve found so far and I’m not even in H3 or H4 yet. Or in the actual matchmaking. Who knows how much piles of it I could find.
>
>
> Several of those aren’t bugs.
> In CE objective markers, particularly in early levels, often don’t appear until a certain amount of time has passed. The intent is for you to find your own way, with the eventual waypoints essentially being automated help. This is as designed, and has been this way since the original release.
> CE co-op respawning has always been the least liberal of the series. While it’s possible there is some glitch here, I doubt it, and you’re probably just used to the co-op respawning in later Halos.
> Level progress has never been saved for co-op levels when exiting mid-mission. Never, in any Halo. By design, not a glitch.
> Regarding Iron, sounds like you’re playing Halo 2 co-op. Halo 2 Legendary has always acted as if Iron was enabled when playing co-op. By design, not a glitch.
> H2 IWHBYD has always been finicky, and no one’s sure exactly how it works. It’s always been down to luck. May have been a glitch in Halo 2, but Bungie never treated it as such and thus in MCC it is by design.
> Not sure about Halo 2 co-op respawning, but like with CE I doubt it’s actually a glitch.
Fair enough for the level progress on co-op, though I remember it saved for the host on 360.
The respawn problem is real, there’s basically no enemies at all around the area. I even goes and explore to see if there’s somehow a hidden enemy or what but no, no one is left other than me.
The mission markers are from the mission Halo. First time we played co-op on Legendary, it does not appear, we played it the second time on same difficulty and it appear. How is that by design? So the design is to randomly turn off the mission markers?
Does Iron get turned on only in co-op? I read that peoples are experiencing the same problem playing solo, which make it much more worse, dying will restart the whole mission. I never played Halo 2 on Legendary before back in the day so I don’t know if it is indeed by design. Seems a lot of peoples complaining about the same thing.
The IWHBYD skull is probably by design, still, I’m posting it up so other people can know what need to be done if they’ve followed all the steps but cannot visually see the skull. That’s all.
Why you doubted someone that have personally experienced these bugs? Because you haven’t experienced them?
Seriously.