Legendary Dante

I don't believe I've ever seen a console game go broken and unplayable for a complete YEAR! For this to be a Halo game (which are normally of the utmost quality)..... this is especially unacceptable. Just an FYI, I contacted Amazon for a return and was given a full refund (gotta love Amazon's Customer Service Department), and also reported the defective product. It will likely not make a difference, but it is the right thing to do. I have played every Halo FPS game since Combat Evolved, and they have always been amazing with Bungie running it. Unparalleled quality of storyline, visuals and audio, as well as such a memorable soundtrack. While Halo 4 wasn't exactly up-to-par in my opinion, 343 earned my respect in seeming competent enough to handle such an established franchise. My gut instinct tells me M$ is the one to blame for this abomination of a release. To get it out by the end of the year, I have all ideas that it was not 343's choice to go with its current state at the time. 343 likely reported it as not ready, but M$ probably threatened legal action based on their contract, instead of understanding the issues at hand. Having said that, I DO place the onus on 343 to make it right and fix the glaring issues in the forefront, and to fix them quickly. To that end, both M$ and 343 have lost my respect and trust as a long-time customer, and I will no longer continue to support either of them in the future. It is the only logical conclusion that I can come up with. I can only hope that others will uphold the same standard of morals and values. However, in today's day-and-age, it is not something I will expect.

Thanks, y'all. That's good to know that the Achievement is still obtainable. However, I still cannot view cutscenes in "Classic". I have tried pressing the Back button both before the cutscene as well as during. Pressing it before the cutscene will change graphics to "Classic", but it reverts to "Remastered" as soon as the cutscene starts. Pressing it during the cutscene does absolutely nothing. Perhaps it has to do with Co-Op?? I will have to try single player later...

Thanks for the response. While that is true, there's a couple of problems with that: 1) Pressing the back button does not effect cutscenes. They just stay with the remastered graphics regardless of whether or not if I have toggled to Classic graphics during gameplay before the cutscene. 2) There is also an achievement tied to experiencing the campaign in both Classic and Remastered visuals. If the game continues to default in Remastered (meaning all the cutscenes will only play Remastered), won't this disable the ability to receive the achievement?

I just noticed this pinned topic from approximately 1 year ago. Confirming that there are apparently still matchmaking random disconnect issues while attempting campaign missions. Just got this game and took 5 tries (4 disconnects) to get through 1 mission in Halo:CE (Pillar of Autumn). I will give it about a week or two and, if it continues to be problematic, I will be seeking a complete refund and reporting it to the retailer as still a defective product.

Just came up on another issue. After finally getting through the Pillar of Autumn mission for Halo:CE after many disconnects, I went to go re-do the mission, but this time selecting the default as "Classic" for Visuals and Audio options. Starting the mission, it would still start with Remastered Visuals and Audio in the cutscene as well as gameplay. I quit and tried again, thinking I had fudged it up somehow, and confirmed 3 or 4 times that the option was selected by going to the difficulty options and back again to see "Classic" still selected. Yet, it would not work. I am starting to think that maybe I'm misunderstanding what that option is supposed to do??? If it is not for selecting the default graphics and audio for the game (cutscenes included), then the option appears to be sorely mislabeled....

Hi, guys. Just got the MCC Beta today and me and my friend are having disconnect issues. We started a campaign mission in Halo:CE and it disconnected a total of 4 times, forcing a restart of the mission each time (it was almost like it was on a timer and you had to complete the mission under a certain amount of time in order to finish it). We both had mics at the time and confirmed it was happening to both of us at the exact same time. Went troubleshooting to ensure there were no network issues and neither of us had problems. It also seemed to happen when things got hot-and-heavy. For example, when I was blown up off the planet from an Elite-thrown Plasma onto a colorful pile of mixed grenades, the game would pause for a second to process the nuclear explosion, then disconnect us both. After its initial release, I had read countless articles of the complete flop that is MCC day after day, and had hoped I had weathered the storm long enough that it was time to take the plunge. It's sad... I just want to Finish the Fight!