devtrackers.gg
Lol same here. Hopefully the flight is more than a few days.
Lol same here. Hopefully the flight is more than a few days.
Sorry to say it will most likely indeed only be a few days. We need to get in, get as much data as we can, and get out. Then it takes time to analyze and act on the data and hopefully get ready for another tech preview (all while still closing out the game itself on the road to launch). Really excited to get this going and it's invaluable to the team but everything involved with flighting can also be really time consuming for the same folks who are working hard to finish the game itself. Always a tricky balance.
I reallllllly hope so. But the lack of exact date feels like they still have a little bit of doubt, hopefully they are just being cautious in case anything major goes wrong.
It's a progressive process that goes through a few gates from the time the build is cut to the time it eventually gets released. Folks who were part of the MCC journey probably remember very similarly. You put the build into a small closed test, evaluate and check against goals. If it passes, on to the next ring which is usually larger / somewhat different conditions. Then, check again to see how the data compares to the targets the team has set. If it's good, then we're ready to go to the public ring. If there are issues or something isn't on target, it then goes back to square one (or sometimes, like square 1.5 and some spot testing / smaller targeted scenarios take place). More work is done and the process resumes.
So, in that regard, it's not truly an exact science. But, we are working through that last gate before it would go public now, so assuming we don't have unexpected issues arise...
With MCC we got burned a few times over-committing publicly only to have a blocker pop up in the last step so we're not going to officially call it until the data is in.
[removed]
Gee, that's annoying! And, it's a hyperlink behind an empty pixel, nothing. Kudos for finding that because I sure didn't. Some copy was pulled over from the doc the team was using to review and leave comments and it usually pulls over associated comments with it, which we then delete. In this case, ONE PIXEL was not selected and it stuck around. That's a first for me!
I can't wait to see some of you get out played by the bots.