I didn’t expect that. Looks like we’re going to enjoy matchmaking tomorrow !
hope the party system works the way its supposed to after this update, ready for tomorrow!
Hopefully this update fixes all of the matchmaking problems and then all of this will be in the past. Can’t wait to play some solid Halo.
At the bottom is the best part. More fixes in the future too. So the fix train will be rolling in which is great.
It’s rather appalling how big the list is. You would think any number of those bugs/glitches would have been found during testing given how huge the list is. More on the way as well? Patch notes like this when the game is barely a week old begs the questions, was there ANY testing of the final product done whatsoever before asking for our money? Extremely unsettling…
> 2533274821210403;5:
> It’s rather appalling how big the list is. You would think any number of those bugs/glitches would have been found during testing given how huge the list is. More on the way as well? Patch notes like this when the game is barely a week old begs the questions, was there ANY testing of the final product done whatsoever before asking for our money? Extremely unsettling…
Even a game that didn’t have many launch complaints still gets tons of fixes. Let’s take Call of Duty Advanced Warfare for example:
Pretty large list of fixes in several patches Most large games these days go through several patches to fix a long list of things.
I’m glad for the update! Really keen to get this going.
I have not been that annoyed about the MP issues. Sure it was bad, and I could not find a game for the first few days, but games started to creep in.
TBH, I would have been surprised if this game had no glitch / bugs. Its 4 game engines, with 2 extra graphics engines on top of that. Really, what other game has to deal with this kind of stuff? and for them to be previous gen titles as well.
This could have turned out a lot worse (Myth 2 uninstall bug anyone - for people who do not know, it would start to wipe your HDD on your computer when you went to uninstall it, ( Bungie.net ).
Games today are so big that I’m not surprised bugs are in it, you would have to have a HUGE QA team to test out what millions of consumers can in experience in hours after release.
I’m happy it’s getting fixed, I’m happy they are telling me the patch notes, I’m happy with the product that I have bought. (I live in AUS so I paid $100 for mine)
A++ 10/10 would buy again.
> 2533274808972171;6:
> > 2533274821210403;5:
> > It’s rather appalling how big the list is. You would think any number of those bugs/glitches would have been found during testing given how huge the list is. More on the way as well? Patch notes like this when the game is barely a week old begs the questions, was there ANY testing of the final product done whatsoever before asking for our money? Extremely unsettling…
>
>
>
>
> Even a game that didn’t have many launch complaints still gets tons of fixes. Let’s take Call of Duty Advanced Warfare for example:
>
> Pretty large list of fixes in several patches Most large games these days go through several patches to fix a long list of things.
- That list isn’t as extensive as this one.
- Over half (yes HALF) of that list is fixing spots where players are able to get outside a multiplayer map.
- In no way was I saying 343i was/is the only game developer to release a game with this many errors. Ones that should have, at least SOME, been caught through testing before putting it on the shelves and putting a next gen price tag on it.
- Yes, games get patches throughout their lifespan fixing a great many bugs. However, that being said, most games, at least in the past before game developers relied so heavily on patching versus testing, do not require this many fixes after the game has been out for a weeks time.
I’ll say again, patch notes like these so early after the game release begs the question have they given even a weeks worth of testing on their own? Surely had they done at least that, they would have found a number of these bugs that they’re just now fixing. Game developers alike, not singling out 343i, rely too heavily on post-release patches. They push games out without the proper time put in the testing phase. Why? Hell! Why not?! We can just patch it later if it doesn’t work properly, guys!
It’s a -Yoink!- mentality but as more and more games get released with these problems (as you were so kind to point out), it’s surely the mentality that most of them have adopted.
Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
> 2533274797947966;9:
> Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
I’m not hating on them whatsoever, just voicing my concerns and what appears to be many others concerns as well.
How do you figure it’s pretty obvious they play tested? Obviously they were the luckiest people to play the game to date since during testing they never once froze at the loading screen after a multiplayer game had ended. Oh, and players never got kicked from the lobby while they were switching up games or playlists. Not to mention, throughout all this play testing not a single one of the testers decided to look at the post-game carnage reports to see who they killed the most or who killed them the most.
You may be right, but if you are and “obviously” they play tested the game, then they were “obviously” the luckiest, as well as the stupidest, group of testers the game industry has ever seen.
Give me a break…
> 2533274797947966;9:
> Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
It’s obvious that the testing that they did wasn’t very thorough. I don’t care if it’s 4 in one, different engines, etc. They knew that before they released the game, so they should have prepared themselves better. They knew that it wasn’t going to be ready at release, but they released it anyway.
I’m talking about things like 1th, party breakage, freezing, etc. There are sooooo many bugs, they couldn’t have missed them. And they aren’t the normal type of bug that slips through testing, the kind that you have to do a certain combination of strange things in order to trigger it. They are very obvious things that happen in normal gameplay.
An example would be the super bouncing of Halo 2. You wouldn’t experience that just by playing the game, except on extremely rare circumstances, which is why it was missed. The Rocket/Sword lunge is another. Those are bugs that only occur in extremely specific circumstances.
Most of the bugs in MCC aren’t that way.
> 2533274797947966;9:
> Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
Its pretty obvious they didn’t test MCC, or clearly not properly, otherwise we wouldn’t be here discussing the matter a week later after release and playing instead.
There’s too many big game breaking bugs, there’s no way they tested the game properly, they just were out of time and thought “f-u-c-k it” shipped the game to be printed on discs and then hoped they’d just patch the crap out of it thanks to now being able to easily path games after release through online service.
Halo 2 didn’t have these kind of issues, why? because back then they couldn’t patch the games after release like they can nowadays therefore it had proper testing and the game wasn’t printed until they made sure it worked fine, the only issues H2 had were on the servers, which were fixed within two days tops.
> 2533274792437461;12:
> > 2533274797947966;9:
> > Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
>
>
> Its pretty obvious they didn’t test MCC, or clearly not properly, otherwise we wouldn’t be here discussing the matter a week later after release and playing instead.
>
> There’s too many big game breaking bugs, there’s no way they tested the game properly, they just were out of time and thought “f-u-c-k it” shipped the game to be printed on discs and then hoped they’d just patch the crap out of it thanks to now being able to easily path games after release through online service.
>
> Halo 2 didn’t have these kind of issues, why? because back then they couldn’t patch the games after release like they can nowadays therefore it had proper testing and the game wasn’t printed until they made sure it worked fine, the only issues H2 had were on the servers, which were fixed within two days tops.
You do know they patched H2 multiple times right? Fixing the BR spread etc…
> 2533274821210403;13:
> > 2533274792437461;12:
> > > 2533274797947966;9:
> > > Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
> >
> >
> >
> >
> > Its pretty obvious they didn’t test MCC, or clearly not properly, otherwise we wouldn’t be here discussing the matter a week later after release and playing instead.
> >
> > There’s too many big game breaking bugs, there’s no way they tested the game properly, they just were out of time and thought “f-u-c-k it” shipped the game to be printed on discs and then hoped they’d just patch the crap out of it thanks to now being able to easily path games after release through online service.
> >
> > Halo 2 didn’t have these kind of issues, why? because back then they couldn’t patch the games after release like they can nowadays therefore it had proper testing and the game wasn’t printed until they made sure it worked fine, the only issues H2 had were on the servers, which were fixed within two days tops.
>
>
>
>
> You do know they patched H2 multiple times right? Fixing the BR spread etc…
Yes I know, those patches came in much later, once xbox live was able to handle game updates, Halo 2 didn’t have a single game breaking bug like MCC has, my point stands.
Developers and publishers are getting very lax on how they put out games, too many half -Yoinked!- game releases lately, its not something we should defend developers on just because we are fans, this is not acceptable.
> 2533274792437461;14:
> > 2533274821210403;13:
> > > 2533274792437461;12:
> > > > 2533274797947966;9:
> > > > Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
> > >
> > >
> > >
> > >
> > > Its pretty obvious they didn’t test MCC, or clearly not properly, otherwise we wouldn’t be here discussing the matter a week later after release and playing instead.
> > >
> > > There’s too many big game breaking bugs, there’s no way they tested the game properly, they just were out of time and thought “f-u-c-k it” shipped the game to be printed on discs and then hoped they’d just patch the crap out of it thanks to now being able to easily path games after release through online service.
> > >
> > > Halo 2 didn’t have these kind of issues, why? because back then they couldn’t patch the games after release like they can nowadays therefore it had proper testing and the game wasn’t printed until they made sure it worked fine, the only issues H2 had were on the servers, which were fixed within two days tops.
> >
> >
> >
> >
> > You do know they patched H2 multiple times right? Fixing the BR spread etc…
>
>
> Yes I know, those patches came in much later, once xbox live was able to handle game updates, Halo 2 didn’t have a single game breaking bug like MCC has, my point stands.
>
> Developers and publishers are getting very lax on how they put out games, too many half -Yoinked!- game releases lately, its not something we should defend developers on just because we are fans, this is not acceptable.
You are an idiot if you think Halo 2 didn’t have any game breaking bugs. The game as a whole was broken. You could sword lunge by using a sniper and sword, gernades were weak, BRs were 8 shot kills, the lag was god awful especially on waterworks. Halo 3 also had a serve issues at launch.
> 2533274854379580;15:
> > 2533274792437461;14:
> > > 2533274821210403;13:
> > > > 2533274792437461;12:
> > > > > 2533274797947966;9:
> > > > > Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
> > > >
> > > >
> > > >
> > > >
> > > > Its pretty obvious they didn’t test MCC, or clearly not properly, otherwise we wouldn’t be here discussing the matter a week later after release and playing instead.
> > > >
> > > > There’s too many big game breaking bugs, there’s no way they tested the game properly, they just were out of time and thought “f-u-c-k it” shipped the game to be printed on discs and then hoped they’d just patch the crap out of it thanks to now being able to easily path games after release through online service.
> > > >
> > > > Halo 2 didn’t have these kind of issues, why? because back then they couldn’t patch the games after release like they can nowadays therefore it had proper testing and the game wasn’t printed until they made sure it worked fine, the only issues H2 had were on the servers, which were fixed within two days tops.
> > >
> > >
> > >
> > >
> > > You do know they patched H2 multiple times right? Fixing the BR spread etc…
> >
> >
> >
> > Yes I know, those patches came in much later, once xbox live was able to handle game updates, Halo 2 didn’t have a single game breaking bug like MCC has, my point stands.
> >
> > Developers and publishers are getting very lax on how they put out games, too many half -Yoinked!- game releases lately, its not something we should defend developers on just because we are fans, this is not acceptable.
>
>
> You are an idiot if you think Halo 2 didn’t have any game breaking bugs. The game as a whole was broken. You could sword lunge by using a sniper and sword, gernades were weak, BRs were 8 shot kills, the lag was god awful especially on waterworks. Halo 3 also had a serve issues at launch.
I also believe the melee system was broken.
> 2533274854379580;15:
> > 2533274792437461;14:
> > > 2533274821210403;13:
> > > > 2533274792437461;12:
> > > > > 2533274797947966;9:
> > > > > Its pretty obvious they play tested the game. No developer would put out something they didn’t test. The thing that people don’t realize is that testing in a controlled environment is in no way an accurate representation of real world conditions and whose to say that these issues were ones they had no way of anticipating. While they did in fact release a broken experience, you can’t fault them by saying they didn’t try. Its absurd to assume they just smashed all these games together and didn’t put forth any real effort in making sure they worked. I’m not saying they were right to release the game in this state, I just don’t believe they deserve so much hate is all.
> > > >
> > > >
> > > >
> > > >
> > > > Its pretty obvious they didn’t test MCC, or clearly not properly, otherwise we wouldn’t be here discussing the matter a week later after release and playing instead.
> > > >
> > > > There’s too many big game breaking bugs, there’s no way they tested the game properly, they just were out of time and thought “f-u-c-k it” shipped the game to be printed on discs and then hoped they’d just patch the crap out of it thanks to now being able to easily path games after release through online service.
> > > >
> > > > Halo 2 didn’t have these kind of issues, why? because back then they couldn’t patch the games after release like they can nowadays therefore it had proper testing and the game wasn’t printed until they made sure it worked fine, the only issues H2 had were on the servers, which were fixed within two days tops.
> > >
> > >
> > >
> > >
> > > You do know they patched H2 multiple times right? Fixing the BR spread etc…
> >
> >
> >
> >
> > Yes I know, those patches came in much later, once xbox live was able to handle game updates, Halo 2 didn’t have a single game breaking bug like MCC has, my point stands.
> >
> > Developers and publishers are getting very lax on how they put out games, too many half -Yoinked!- game releases lately, its not something we should defend developers on just because we are fans, this is not acceptable.
>
>
>
>
> You are an idiot if you think Halo 2 didn’t have any game breaking bugs. The game as a whole was broken. You could sword lunge by using a sniper and sword, gernades were weak, BRs were 8 shot kills, the lag was god awful especially on waterworks. Halo 3 also had a serve issues at launch.
I said game breaking bugs, not gameplay bugs.
By game break bugs, I mean like how MCC crashes, how you can’t play matchmaking, how H2A campaing coop doesn’t work, etc, none of that happened for Halo 2 or other games for that matter.
And those halo 2 gameplay issues were fixed months later on, because the xbox live at first could not deliver game updates, hence my point, they shipped Halo 2 properly tested, the only bugs were gameplay mechanics that could be exploited, not crashes not faulty UIs etc
Yeah this update is pretty huge. It added all new bugs. I love it.
Well, it didn’t improve anything…
Yeah, H2A coop still doesn’t work at all, now matchmaking crashes when trying to load maps 1/2 times (at least for H2A), UI still glitchy as hell, especially the lobbies and how it displays the player list while searching or after a game.
Search times have improved a bit, though sometimes it’ll take minutes and not find anything 