Halo: Master Chief Collection

[007ELmO]

there is no denying that aiming with a mouse is more precise and easier.

but most people don't like and fear what they are not good at, especially when there is an alternative that they are better at, so they just cry about the controls on a pad rather than practice and get better.

It's not really that. For instance, GTA5 is delayed for PC, but in first person mode, I feel like I'd rather use a mouse and keyboard. For the rest of the game, the gamepad is probably better.

Another thing, Mass effect works pretty well with a gamepad, but I played it off steam recently on my PC and it was a little bit better in gun fights (which isn't really the focus of the game).

 

[Lil Frier]

a delay WOULD have fixed it if they delayed it long enough to fix it. i'm not saying that if they delayed it a week that it would automatically be fixed. i'm saying if they delayed it as long as necessary to get it fixed, it would have been fixed at launch. it's a pretty simple concept.

but your argument is basically a strawman argument at this point.

Based on what? Because you're calling my point unprovable, in defense of your OWN, also-improvable point?

Honestly, I'd MUCH rather have Microsoft release the game with broken multiplayer, find it easily, then patch it 9 days later, then have them delay it 1-2 months, then still have bugs needing to be patched. If they're not going to have a beta, I'd take a 9-day delay over a month-long one, simple as that.

However, claiming my argument is a "strawman," simply because you don't agree with it, doesn't make the claim so. You're saying I can't know my claim to be true, yet you hypocritically make a similarly unknowable claim (a delay would fix it) as your defense. Then, a vague phrase like, "delay until it's found," doesn't entail anything. Some of those bugs very well could have taken several months of internal testing.

If that was the case (again, no way of knowing), is that multi-month delay worth not having 9 days of this? I say not, but that's my opintion.

 

[Lil Frier]

It makes perfect sense. They could have easily delayed it telling fans "hey everyone the matchmaking isn't working like we had hoped right now. We are going to have to delay the game a bit to get it sorted." No, they rather release it broken to try to get ahead of the other huge games that will drag people away namely GTA.

Notice how games that have had a public beta and are online games generally turn out to work on day one? More companies need to do that. Do their testing before people are paying for the game.

I fully agree, a beta should have happened, not a point I'd ever argue against. However, I still wouldn't peg the release of Halo solely on GTA. I mean, I get it's a big-time game and all, but it's also a port/remake. If you wanted to maybe argue something like losing Christmas bonus sales and bundles (like what Wal-Mart is doing), or point out the general depth of big titles coming out, I could get with that. GTA, a re-release, on its own? I don't think that's the cause.

However, like I said, I feel like I would be happier with a 9-day delay for a patch over weeks or months where I can't do anything (I'm working through the campaign with a friend now).

 

[purbeast0]

Based on what? Because you're calling my point unprovable, in defense of your OWN, also-improvable point?

Honestly, I'd MUCH rather have Microsoft release the game with broken multiplayer, find it easily, then patch it 9 days later, then have them delay it 1-2 months, then still have bugs needing to be patched. If they're not going to have a beta, I'd take a 9-day delay over a month-long one, simple as that.

However, claiming my argument is a "strawman," simply because you don't agree with it, doesn't make the claim so. You're saying I can't know my claim to be true, yet you hypocritically make a similarly unknowable claim (a delay would fix it) as your defense. Then, a vague phrase like, "delay until it's found," doesn't entail anything. Some of those bugs very well could have taken several months of internal testing.

If that was the case (again, no way of knowing), is that multi-month delay worth not having 9 days of this? I say not, but that's my opintion.

based on the fact that they could simply not release the game until multiplayer was working, regardless of how long it took to fix it. whether it took a week, or 6 months. a delay would fix it because you have infinite amount of time to fix it. if it's not fixed in a week, then delay it longer. not finished in a month, delay it longer. and repeat. it's basic software development, which i've been part of for over 10 years now.

it really is a simple concept. kind of like how they can't release uncharted 4 tomorrow, because it's not finished. but once it's actually finished, no matter how long it takes, it will be released.

and your argument is a strawman. you made a point with no facts, i called you out, then you basically said "well you have no proof i'm wrong". that is the definition of it.

anyways, moot point now. releasing incomplete software is terrible practice and now a days with online patches, a lot of companies seem to think it's okay. i personally won't be supporting any of these games, until maybe they are 'ready'. had they came out and made a huge announcement that the multiplayer wasn't ready and working, BEFORE the game launched, then i'd have a different view on it. but they didn't.

EDIT:

also, being in software development for over 10 years, it's pretty easy to estimate how long it will take to build a feature or fix a bug, which is why and how they estimate release dates and stuff. and it's not like this is their first time at the rodeo, so i'm pretty confident they could EASILY give an estimate on how long they think it would take to fix the issue.

 

[Lil Frier]

Installed the patch, got the matchmaking going...nothing. I tried Team Slayer, Big Team Battle, Halo 2: Classic, and Halo Championship Series. I found nothing. I tried Halo 2: Anniversary (the ranked one), and it found 3 other people quickly, but as I didn't want to actually play that game type (just seeing if it did any better than the others), I quickly left. So, at least initially, this patch seems like a dud.

 

[purbeast0]

Installed the patch, got the matchmaking going...nothing. I tried Team Slayer, Big Team Battle, Halo 2: Classic, and Halo Championship Series. I found nothing. I tried Halo 2: Anniversary (the ranked one), and it found 3 other people quickly, but as I didn't want to actually play that game type (just seeing if it did any better than the others), I quickly left. So, at least initially, this patch seems like a dud.

it could be that not everyone has gotten the patch yet or something. i know with KI, usually the day of the patch, things don't seem quite right until the following day.

 

[Lil Frier]

It'd be nice, but the number one thing I've done with Microsoft is stop being optimistic. With all of the poor decisions they've made over the past year or so, I kind of hope for the best but expect the worst.

 

[Tweak155]

Ya I tried matchmaking after the patch and it didn't seem much different. I'll give it another shot tomorrow.

 

[dguy6789]

If matchmaking doesn't immediately work well after the patch I'd put my money on not many people having it yet since it just came out

 

[foghorn67]

Wahoo! I'm in matchmaking.

 

[Justinbaileyman]

I got the patch and 1 match making game worked then I havent been able to connect to another one since. I tried unplugging my xbone to reset it and still not able to connect to anyone. What is going on with this damn game?? every other game I own doesnt do this.. JUST THIS ONE!!

 

[purbeast0]

my brother texted me and said for him since the patch it's been really good.

 

[artemicion]

based on the fact that they could simply not release the game until multiplayer was working, regardless of how long it took to fix it. whether it took a week, or 6 months. a delay would fix it because you have infinite amount of time to fix it. if it's not fixed in a week, then delay it longer. not finished in a month, delay it longer. and repeat. it's basic software development, which i've been part of for over 10 years now.

it really is a simple concept. kind of like how they can't release uncharted 4 tomorrow, because it's not finished. but once it's actually finished, no matter how long it takes, it will be released.

and your argument is a strawman. you made a point with no facts, i called you out, then you basically said "well you have no proof i'm wrong". that is the definition of it.

anyways, moot point now. releasing incomplete software is terrible practice and now a days with online patches, a lot of companies seem to think it's okay. i personally won't be supporting any of these games, until maybe they are 'ready'. had they came out and made a huge announcement that the multiplayer wasn't ready and working, BEFORE the game launched, then i'd have a different view on it. but they didn't.

EDIT:

also, being in software development for over 10 years, it's pretty easy to estimate how long it will take to build a feature or fix a bug, which is why and how they estimate release dates and stuff. and it's not like this is their first time at the rodeo, so i'm pretty confident they could EASILY give an estimate on how long they think it would take to fix the issue.

OK, I'm going to try to explain this to you in one post. I don't care enough about either side of the argument to put any more effort than that. You may be right in assuming 343 did something wrong. Lil Frier may be right in assuming 343 acted reasonably. I don't really care. You are, however, completely wrong in dismissing his side of the argument.

First, a couple of premises.

1) Halo: MCC matchmaking was not completely broken. Sometimes it worked, other times it took a really long ass time to work.

2) There is no indication that the matchmaking issue was a known problem at launch. Maybe they knew about, but there's no report suggesting that they did, which to me makes it more than likely that they did not. Maybe they did not know about it because the bug in the code was something that didn't show up in their tests. Given fact #1, that matchmaking was never completely broken, it is entirely possible that matchmaking passed all the tests they threw at it during testing.

3) There is no proof that they would have discovered it in a reasonable amount of time with further testing. There is no proof that 343 was not diligent in the testing they did for matchmaking. Lots of problems lurk in the shadows pre-release that are difficult to impossible to discover in pre-release conditions. If you truly have been in software development for 10 years, you would know this. What if the issue was that the matchmaking algorithm goes bork when facing an extremely high load of requests? What if the issue is caused by some unique combination of matchmaking requests? Or from some unexpected combination of Halo score/level, matchmaking request type, connection type, etc.? It would be very easy to miss this during testing, and there's a very good chance it would NEVER be caught even if you went through YEARS of testing.

The issue at the heart of the matter is: was it reasonable for 343 to release Halo: MCC given the information known to them at release? Nobody here has an answer to that because nobody here knows what 343 knew at release and nobody here knows the details regarding how exactly matchmaking was broken.

Also, as to open beta testing. Yes, it is usually a superior method of testing software. However, it's also not a guarantee. It's entirely possible that the bug wouldn't have surfaced even in open beta if it were related to a certain load level for matchmaking requests that is > the open beta pool and < release pool. Also, there's lots of good (profit related) reasons not to open beta test. Not all software is tested in open beta and not all software should be tested in an open beta. Maybe the rationale was that they thought that since it the game was a re-release and half the value is the nostalgia, open beta would cut into sales figures as people got the nostalgia for free during open beta and did not buy the final product. Who knows.

 

[cmdrdredd]

Doesn't matter what you say. The game's matchmaking WAS broken. No question. It's still half broken. No excuses. Bungie had it working in their original versions. 343 broke it. End of story

 

[artemicion]

Doesn't matter what you say. The game's matchmaking WAS broken. No question. It's still half broken. No excuses. Bungie had it working in their original versions. 343 broke it. End of story

I wasn't making excuses. Try reading again. 343 screwed up. The only debate that was going on was whether 343 could've fixed the problem if they delayed the release or if it was an issue that wasn't reasonably ascertainable until the game was released. I wasn't even taking a position one way or another. I was just saying that both were possibilities and anyone who assumes one or the other without proof is obtuse.

Bugs happen. Windows 8 still has bugs and security holes. That does NOT mean they should've delayed the release of Windows 8 (for what, 2 years now?) in the hopes of releasing a product that is completely bug free.

 

[cmdrdredd]

Broken matchmaking isn't a bug IMO. It's integral to the online experience which is pretty integral to Halo itself. It's not like getting glitchy sound or stuck on an invisible wall.

 

[Tweak155]

Not to mention there are quite a few bad bugs on top of matchmaking. I'm not the only one who has their game freeze every so often according to google. It locks up then just restarts the game.

 

[Wingznut]

Broken matchmaking isn't a bug IMO. It's integral to the online experience which is pretty integral to Halo itself. It's not like getting glitchy sound or stuck on an invisible wall.

Absolutely. Everyone, including the developer and publisher, knows that a huge part of this game's fan base is all about the multiplayer.

 

[Justinbaileyman]

Not to mention there are quite a few bad bugs on top of matchmaking. I'm not the only one who has their game freeze every so often according to google. It locks up then just restarts the game.

Yep had this happen to me today damn game froze right up on me for no reason and did not reset. it was just a frozen game screen like I used to get way back in the day when I used to play NES games on the toaster NES.Also had the weirdest thing happen to me to day. I got into a match making game on a halo 3 map the one where there is a sword in a room and the over shield is under the room and there are rockets on the other side of the map with invisibility in the middle of the map in a halway. I think its called the pit??
Any ways when we started everyone headed right for the rockets and I went off on my own heading for the sword.On my way there I was hopping along like I always do to dodge any in coming fire from the opposing team when out of no where I fell through the map.Every time I respawned the game respawn looped me falling through the map over and over??Never ever had this happen in this game to me before.Again I cant connect to any more games again

 

[Lil Frier]

So, to reiterate: People are mad, not having a beta was the dumbest thing possible for a game with a large chunk of its value built into online multiplayer, the patch isn't a cure-all, half of the playlists are still missing, and 343 made a horrible offering of playlists in the first place.

I want Regicide back, damn it.

 

[Phobic9]

Thought I'd finally be able to play online after the last patch but... nope. Just loads... and loads... whoops! Connection lost.

I pretty much bought an Xbox One due to the price cut and MCC. Gonna be putting this one one the backburner until it's finally fixed. Luckily, there's the problem of too much to play for me right now on the other two consoles.

 

[dguy6789]

My findings are that the patch has helped but it's definitely not even close to being a satisfactory matchmaking service yet. Sometimes it will connect within a minute and sometimes it still takes over 10.

When a match finishes it often doesn't keep the lobby and players together so you have to find a new match and wait another however many minutes between every game you play.

I could probably play 5 Call of Duty Advanced Warfare matches in the time it would take to play 1 or 2 in MCC.

 

[Tweak155]

Thought I'd finally be able to play online after the last patch but... nope. Just loads... and loads... whoops! Connection lost.

I pretty much bought an Xbox One due to the price cut and MCC. Gonna be putting this one one the backburner until it's finally fixed. Luckily, there's the problem of too much to play for me right now on the other two consoles.

Ya same here although I'm glad I tried shadow of mordor. It was a really decent game although I didn't care to finish it.

 

[Tweak155]

My findings are that the patch has helped but it's definitely not even close to being a satisfactory matchmaking service yet. Sometimes it will connect within a minute and sometimes it still takes over 10.

When a match finishes it often doesn't keep the lobby and players together so you have to find a new match and wait another however many minutes between every game you play.

I could probably play 5 Call of Duty Advanced Warfare matches in the time it would take to play 1 or 2 in MCC.

Ya patch has helped a little. Overall still very disappointing. I still suck at the game so I don't even have A.I to sharpen my skills against.

 

[Justinbaileyman]

What was this patch even for cause it didnt even fix anything??