Forums / Community / Halo Insider

[Locked] MCC Dev Updates

OP Postums

Hey Friends,

It’s Friday which means we’re back with another mini-update to share the latest status on MCC PC development and where we are at for the next Halo Insider flight. If some of you have paid attention to my posts over on Twitter (1st and 2nd) and even last weeks news article, you have been gaining some insight into the process and where we have been tracking towards for flighting.

In case you are joining us for the first time, you can catch up on what has been going on over the past few months with these helpful articles:
Now that we are all caught up on what’s happened, let’s talk about where we are at right now.

Where are we at?
Currently, we have completed our Ring 2 testing and have verified that previous blocking bugs have been resolved. The Test Team received a new build yesterday and is currently working through a full verification of the build. If verification completes today, we will go to Ring 1 this weekend to verify the changes and assess readiness for the Ring 2. If all goes well there, we will continue in the following week moving through our rings. If no showstoppers are found – we will be able to move to Ring 3 soon once all previous Rings have been cleared. Below are a handful of bugs that have been resolved this week which were Ring 3 blockers.
  • Users were able to matchmake after editing various files
  • Soft Lock when pressing Alt + Tab while in full screen
  • Crash when loading into a match
  • Certain scenarios caused the Roster to disappear and not be accessible
  • Inviting a friend to play would cause the invitee to crash when accepting it
All of these are currently being verified by our internal team as being fixed now. We are looking good to go out to Ring 1 tonight and if verification that all critical bugs have been fixed and no new major issues present, this could be the build that goes out to Ring 3 soon barring no issues.

Looking Ahead!
Even though we are working on the FireFlight, we still have progress being made on the following flight to test out PvP. The key goals for the next one will be to validate Halo: Reach PvP networking within gameplay and through the matchmaking flow. This next flight is currently planned to be an Xbox One flight only. Below is the current spec for our first offerings for matchmaking we are working towards.

Social Games
  • Halo: Reach
    • 2v2 Matchmaking
      • Maps: Countdown, Powerhouse, and Zealot
      • Game Categories: Slayer
    • 4v4 Matchmaking
      • Maps: Countdown, Powerhouse, Zealot, and Tempest
      • Game Categories: Slayer, Flag and Bomb, Zone Control, Asset Denial, and Actionsack
    • 8v8 Matchmaking
      • Maps: Tempest, Breakpoint, and Ridgeline
      • Game Categories: Slayer, Flag and Bomb, Zone Control, and Asset Denial
Competitive Games
  • Halo: Reach
    • Reach Team Hardcore
      • Maps: Countdown and Zealot
      • Game Variants: Slayer and Capture the Flag
    • Invasion
      • Maps: Breakpoint
      • Game Variants: Invasion
We are excited for the future and are all hard at work bringing these games to all of you. Thanks for joining us and we look forward to chatting more with you in the following weeks!

Cheers,
Postums
Hello Halo Insiders,

Welcome back to another Friday mini update where we are going to discuss all the latest and greatest in MCC PC development as we march towards the next flight! The team has made a lot of progress this past week.

But before we begin, if you haven’t been following our previous updates, I highly encourage you to take a few minutes and get caught up on some important background info about the Halo Insider Program, public flighting, and the overall project itself. Consider this a pre-requisite and required reading before you get any further in today’s blog:
Now that you have gotten through all that light reading, let’s get into some new goodness.

Where are we at?
Yesterday, we shared our current proposed build for Ring 3 to our Ring 1 & 2 users. Testing went quite well over the evening with improvements being seen over past builds.

This is the same one that was streamed on Wednesday’s 343 Social Stream. If you missed that, please feel free to check out the VOD HERE. The Reach goodness starts around the 28-minute mark.

As it stands right now, all Ring 3 blockers are currently resolved, and we are very close to getting the build out to the Halo Insiders. The current snag we are working through involves how we support the flight roll-out. These issues were identified early in the day, and some have been resolved, but not all. The good news is that we are very close and once all our ducks are in a row, we will be able to get the party started!

Thank you everyone for waiting patiently. I know we can’t wait to get this out into your hands to try out shortly!

Cheers,
Postums
Good Morning Halo Insiders,

In case you haven’t heard about it, you still can register for the Halo Insider program. Sign-ups are always available if you want to participate in future flighting for Halo titles. Currently flighting is focused on Halo: Reach as part of the Halo: The Master Chief Collection, but it will also serve as a testing ground for all titles that make up the Master Chief Collection.

What does the Halo Insider program entail? How does one sign-up (or opt-out)? Get the answers to these questions and many more on the Registration page HERE, or in the Insider forums HERE.

In addition, if you haven’t been following our previous updates, I highly encourage you to take a few minutes and get caught up on some important background info about the Halo Insider Program, public flighting, and the overall project itself. Consider this a pre-requisite and required reading before you get any further in today’s post:
Now that you have gotten through all that light reading, let’s get into some new goodness.

Flight Two – FireFlight
When undergoing major updates such as adding an entirely new game to MCC or bringing MCC to PC, a critical component in this process is to get community involvement early and often. This means you to get hands-on time to play, test, and provide feedback for our in-progress builds via the Xbox Insider app on console and via Steam on PC.
Since the conclusion of Flight One the team has been working on the next, affectionately dubbed FireFlight. Today we are happy to say that this flight number two will begin today!

Participants
Invites have started to roll out for the FireFlight participants that have been chosen. With this flight, the team has increased the size of the user pool to 10,000 invitees. Those who were invited to Flight One may have not received an invite again to this flight as the requirements the team has chosen for participants has changed.
However, even with this bigger group, most of the overall Halo Insider population will still not be included quite yet. For Flight Two we’re continuing to intentionally limit the number of users as we gradually ramp up in size and scope to appropriately test various hardware configurations, operating systems, and other various scenarios we are looking to test at scale. Should you not be invited this time, we sincerely appreciate your interest and eagerness to help. There is more to come.

Scope
In the Halo Insider MCC Flight One we focused entirely on the Halo: Reach campaign mission, Tip of the Spear. For the second PC flight we will be focusing on verifying Firefight and Firefight matchmaking at scale.

Maps
  • Beachhead
  • Corvette
  • Holdout

Firefight Playlists
During this flight we will rotate two different Firefight playlists throughout the duration with only one available at any given time.
  • 4-player Heroic standard Firefight
  • 4-player Normal grab bag Firefight
As with all flights, keep in mind that this represents a snapshot of an in-progress build at a specific moment in time – which is not as current as what’s being actively developed at this very moment. Flights are also clearly limited in scope which means many of MCC’s features and broader offerings are not included. Participants will want to check out the “Known Issues” post on Halo Support for the latest and greatest details to be aware of for this flight.

Feedback
In conjunction with the Halo Insider MCC flights, we are also beta testing the all new Halo Support site. This is a new site that allows you to learn about known issues and how to troubleshoot them. It also provides a forum to discuss feedback you have around the game, and lets you submit support tickets for technical issues that have not been previously reported. To learn more about the Halo Support site, please take a look at this post all about it HERE.

Those who are participating in the MCC flights will be granted access to the Halo Support site using that same account that they registered with for Halo Insider. If you have feedback during the flights, please take some time and post in the Community section over on the Halo Support site. Otherwise, we look forward to getting your thoughts as part of the survey that will come after the flight has concluded.

Dates & Play Sessions
  • August 24, 10:00 AM PT - 1:00 PM PT & 5:00 PM PT - 9:00 PM PT
  • August 25, 10:00 AM PT - 1:00 PM PT & 5:00 PM PT - 9:00 PM PT
  • August 26, 10:00 AM PT - 1:00 PM PT & 5:00 PM PT - 9:00 PM PT
This flight has gone live today, Saturday, 8/24, as we set our cruising altitude for the duration of the weekend. We will come in on our final approach on Tuesday, 8/27 before clearing all rows at 10 AM PT and sending out a survey in the following day or two asking users about their experience for the duration of the flight.

The FireFlight invites to all participants have begun rolling out at 10AM this morning. So, check those inboxes (spam folders included) and get ready! Thank you everyone who has registered to participate and to those who are invited. Your time and efforts along with your feedback are helping to shape MCC on PC! Next week, we will discuss how the flight went and start ramping up discussions around the next planned Xbox One PvP Flight the team will shift focus over to.

Cheers,
Postums
Hello Halo Insiders,

Today’s update on flighting is going to be quite brief.

Where are we at?
Well, a new blog dropped last week right HERE. In that blog we talked a little bit about three things as it related to flighting.
  • FireFlight had come to pass
  • There were some inner discussions of a FireFlight 2.0
  • Looking ahead to the first Xbox flight for Halo: Reach which would be PvP focused
We have some updates on these points today.

FireFlight 2.0
With bleeding edge transparency often comes pivots and changes on the drop of a dime. Prior to analyzing all the data of our Fireflight we thought we might end up needing to conduct a second one. However, after further investigation, we identified the information we needed to properly evaluate our goals from the results we had collected. This means, we have decided to not conduct a follow-up FireFlight and press onwards, to focus on PvP flighting.

Xbox PvP flight
I was in a meeting this week (Thursday 9/5) where we discussed the status of the Xbox build. Currently the team is working through determining which build they would like to branch with, to begin hardening for the next flight. QA runs daily tests and the team is reviewing reports on the most recent builds to assess which features/bug fixes they would like to be in before the first branch.

For those who are like, “why is he talking about trees?” that is a very fair thought, let me explain.

In the code world, you can create what is called a “branch” which at the time of its creation can be a carbon copy of the core code for a project. But after that branch happens, the code is isolated from your main project. This allows you to fine tune, to pick and choose, what pieces you want pulled into it. Branching for a flight is one of the core steps for each flight to lock everything down and work to more easily stabilize the code base. This concludes my Ted talk. Back to news!

Once a branch is successful, the team will do a full evaluation of the proposed candidate and begin gathering the top issues they would like to resolve in preparation for flighting! Currently, the team has only conducted tests internally to Ring 0. I look forward to discussing the Xbox PvP flight build more next week.

Until next time, we’ll see y’all online!

Cheers,
Postums
Hey Friends,

Back again with another update on how flighting is shaping up. I touched base with the QA team to be brought up to speed on all the issues that were submitted by those who participated in the FireFlight. As well, I talked to the team about the next planned flight for Xbox One which will be Halo: Reach Matchmaking. All the juicy details can be found below!

FireFlight Bugs Recap
From the last flight, we had over 400 issues get reported by the community. There were many duplicate reports of the same problem users were encountering so the unique was much smaller in comparison. Below are the top issues that were reported by count.
  • Stability issues on launch, match start, and match end
  • Settings not working as intended
  • Audio issues
  • Intermittent freezes and enemy display issues
All of these issues are being investigated by the test team and have bugs logged against them to have additional information entered to be fixed in the future.
Below is a full list of issues reported by the community that have already been fixed. Thank you for sharing all the information!
  • Exiting out of settings menu guns continue to fire
  • UI had multiple medal displays
  • Game incorrectly gives “host disconnected” message in certain network situations
  • Picture in picture on weapons like scopes do not match up with view
  • Players could get locked in menus after selecting various sub-menus
  • Death screen camera sensitivity is too slow
  • You could run faster running diagonally while holding the turret
  • Misspellings in the “Change Profile” description
  • Using an Xbox controller can cause crashes
  • When hovering over the roster it is in focus, but when moving away from it, it stays highlighted
  • Firefight Matchmaking menu had placeholder titles
  • Brutes seem to drop invisible armor lock pickups
  • Text sometimes appears as “Breadcrumb text Breadcrumb” instead of “Choose Game Type”
  • During match, UI offset on Ultrawide monitor is present.
Again, thank you so much for all the feedback that you have had! We are excited to hear about things you had issues with so we can put as much polish on the features we have as possible.

Xbox PvP Flight
Currently the team is still working to identify the best build to branch from right now. There are a handful of key bugs they are waiting to get fixed as well as pieces of content that may or may not make it into the flighting build. As bugs are fixed and additional work is happening, they may wait a little bit longer to get some key features in so more systems can be stressed and looked at by the community as they come online.

Currently the team has been having regular Ring 0 play test, which means internal testing only for feedback and stability checks so far. Once a branch build is identified, we will be able to move towards flighting and work through any bugs we have backlogged that are blockers. As we move into the following week, we will have more progress updates to share on the status of flighting as we get ready to push towards the PvP flighting.

Until next time, we will see y’all online!

Cheers,
Postums