Just a guess. i honestly think the game was originally to plan on releasing on May 5th but it received a delay a few weeks back. Probably was a communication error.Reasoning for this is that the trailer that they uploaded originally said Available Now, which was a mistake and it was replaced. As well, a Mouse pad was released today to celebrate H2A PC release.
Link to Mousepad: https://www.microsoft.com/en-us/p/halo-2-anniversary-mousepad/8w3whql533vp
The game was actually never going to release today - it was always May 12. Sorry folks got jebaited somewhat - I don't disagree that Twitter interaction was a little misleading (esp given that we did release HCEA out of the blue with little notice, so I don't blame folks for thinking that was the case again). As soon as I saw the tweets I knew what the outcome expectation would be (and I tried to course correct this AM). And that trailer wasn't actually meant to be published today - that trailer is for launch on 5/12. There was a brief issue where it went live on the Steam page, I believe it was rectified.
Basically none of the problems from the Reach flight were fixed before release, even after months of delays. Safe to say the game is going to release with a ton of bugs whether they do it today or in a week, so might as well just shove it out now.
That's just not true. Many "problems from the Reach flight" were indeed addressed by launch. Others were not - some were addressed in later updates, and still others are still in progress (audio, for example). The scope and severity of the current known issues vary and the team continues to do work and we do our best to provide transparency into status and expectations - while they also have to keep moving forward with four more games owed to customers who've purchased the bundle.
Honestly though they should just fix all the issues with Reach and CE before continuing to release more. Piling bugs ontop of bugs just to "fix them later" is what caused the issues with MCC in the first place. What ever happened to "Its ready when its ready".
We'd love to do that - trust me, the team doesn't feel great or enjoy a growing backlog of issues/feedback areas. It's complicated - there are different workstreams and different partners doing different things. Not all things are equal in terms of time/resources/complexity. Based on player feedback early on, the decision was made to offer the 'bundle' so we now have many, many customers who have paid up front for products we promised this year. The team has to continue moving forward on the remaining four titles and unfortunately this has meant that some backlog items have ended up taking longer than hoped (particularly as the entire studio shifted to an indefinite work-from-home situation - which has had a real impact).
H2 will have 'issues' at launch - all games do. The team has done their best to attack critical issues raised during flighting and get to what they feel is a solid foundation for release. Most players will have a good experience w/ H2 come next week. We will publish the known issues up front as we have in the past - and we will continue to work on issues and areas of feedback ongoing but the team's priority has to be the remaining releases and they're realistically limited in their ability to turn around constant patches and updates at this time. We'll get there, it's just going to take a bit longer than any of us would ideally like.
Wonder how many of the known issues from the flight will remain on the 12th. Playing with 500+ fps and having heavy input (buttons, not camera movement) delay felt awful.
There are definitely known issues at launch. Some of those are persisting from flighting (though some of the feedback areas from flighting were never validated / repro'd / deemed a true 'issue' outside of a one-off case). We'll hopefully get the known issues list posted before release.
Hell yea. I’m pumped. Haven’t plays MCC PC since reach. Did they fix the screen tearing?
VFR implementation in MCC on PC is still considered 'experimental' and is generally at parity w/ Reach and HCEA. I suspect some players who enabled uncapped will still encounter screen tearing in situations where framerates dont match up to their monitor refresh rate. The team wants to dig back into that down the road and has some ideas to make the experience better but it's going to take time.
Seriously, it's been months since MCC was released on PC. Where's the file share too?
File share has regrettably been a pretty big challenge on numerous fronts. The April MCC Dev blog touches on it a bit. Without a File Share, Forge is incredibly limited thus hasn't been released yet. The good news is all the UI and PC control work is generally done now, so the team has made progress since Reach. Now just need a bit more time on File Share stuff. We'll share more info as soon as we have it.
FWIW, I get really bad screen tearing even when capped at 60 fps with a GTX 1060 (6 GB) at 1440p. Not sure if this is something I should report on the Halo Support site. I do not have V-sync enabled, though, due to the input lag - but even in other games like CSGO, I get much less screen tearing with V-sync disabled. I don't know if there's a way to reduce the excessive screen tearing outside of enabling V-sync (in the case where the GPU can render >= the number of frames supported by the monitor).
If you'd be willing to file a support ticket, it would be helpful. The more tickets we get around and issue helps the team better assess the scope of impact. And often new tickets include new info and insights for the team as they work to investigate and resolve issues.
So all this stuff saying that it was gonna come out today just happened to occur at the same time?
Damn forgot questions weren't allowed
Nothing said it was "going to come out today" that I'm aware of, minus the official launch trailer that briefly appeared on Steam a week early.
Is there any chance we'll get server browser?
Without that multiplayer is hell with that slow and clunky old school matchmaking.
a custom game browser was something the team shared intentions for a long, long time ago. it's still on the list and I'm pretty hopeful we'll get there but it's going to take more time. As the whole project became more challenging and time consuming than originally anticipated, several quality of life improvements and community-requested-features had to get moved to the backlog until more time/resources can be devoted to it.
devtrackers.gg