Halo Master Chief Collection: H1-4. H2 full remaster. 1080p60. $59.99 Nov 11 Xbox One

I still can't get over the fact that this game has over 100 maps in multiplayer....

mindblown_6413a2aef3142eab8dd789403f71008e.gif

and ALL campaigns and ALL mp will be on an ALL IN ONE disc
 
They did eventually counter most of it with 1.5, but it kind of hurts when the entire console has been compromised in terms of security.



They never said this to my recollection, and explicitly set up an email h2cheats@microsoft.com (still seared into my brain) for people to report instances.



ELO is provably broken. The sport it was originally invented for no longer uses it. ELO was made to be quickly calculable on pen and paper by humans, but has many issues related to making it easily calculable like that. There's no reason to use a simple broken system when you have servers available that can crunch super complex math in seconds, considering many more parameters.

For example, in ELO, you can actually be punished for winning a game, rank-wise. You can literally enter a game and every option you have (leave, lose, win) will derank you. How is a ranking system like that fair?



So you played against a small tiny fraction of players at Bungie, which proves nobody at Bungie was good at Halo?


Holy shit man, I remember playing Halo 2 with you after OG Xbox Live went down and as long as you stayed connected you could keep playing. Gonna be awesome to get back into Halo 2.
 
My guess for the 6 maps:

-Ascension
-Lockout
-Zanzibar
-Headlong
-Ivory Tower
-Midship

Ascension, Lockout, Midship, and Ivory Tower are virtually guaranteed, as is Zanzibar for assault type games. The only one I'm iffy on is Headlong. I could see that one not making the cut for the super-six if only because it just seems like a middle ground... it's rarely the map people mention when I ask them what their favorite maps of the old days were. Although forging on Headlong would be the shit.


Also has anyone even mentioned how crazy the Machinima coming out of this shit is going to be??

RvB resurrected... SOMEONE CALL CABOOSE!
 
So when you play on a Halo 2 map that hasn't been remastered do all the graphics just look like the the original Xbox game or do the Spartan, Elite and weapon models look like the remaster?
 
So when you play on a Halo 2 map that hasn't been remastered do all the graphics just look like the the original Xbox game or do the Spartan, Elite and weapon models look like the remaster?

Only major difference between the Halo 2 version on the original Xbox and this is that it is running at 1080p60.

Remastered maps run on a variant of the Halo 4 engine with features and mechanics from Halo 2 reintroduced, plus 1080p60.
 
So when you play on a Halo 2 map that hasn't been remastered do all the graphics just look like the the original Xbox game or do the Spartan, Elite and weapon models look like the remaster?

If you're playing on the non-remastered maps, then you will be playing on the original Halo 2
Vista
engine. The gameplay engine that the Anniversary maps are played on is a modified Halo 4 engine that has added features like dual weilding. The Six remastered maps are the only maps (baring later DLC releases) that will be in the updated visual style.
 
Sorry if answered already but is November 11th worldwide release date or just US?
I'm in UK and want to book the week off work.
 
My guess for the 6 maps:

-Ascension
-Lockout
-Zanzibar
-Headlong
-Ivory Tower
-Midship

Ascension is confirmed.
Agreed on Lockout.
I don't think Zanzibar will be in since it was remade pretty well for Halo 3.
Headlong had a Halo reach remake, but maybe.
Ivory Tower, same as Headlong, but there's a chance.
Midship had a nice remake for Halo 3 also..

My list:
-Ascension
-Lockout (classic map, and Halo 3 version was not a true remake)
-Turf
-Terminal
-Coagulation (too much of a classic)
-Sanctuary (symmetrical map to balance)

Now that I've thought about it for a while, I don't really care which maps get the anniversary treatment. If all of them are going to be playable online in original multiplayer, that's enough for me.
 
Still a bit confused on the Halo 2 multiplayer.


So Halo 2 campaign gets the Anniversary treatment, but multiplayer will not, it will run on the old engine only, albeit in 1080p@60fps.


Then there are six maps that will look like Ascension running on an XBO native engine.

So in general, while playing Halo 2 multiplayer, unless you are on those 6 remastered maps, it will look like you are playing Halo 2 Vista Multi at 60fps 1080p..


Am I getting that correct?
 
Still a bit confused on the Halo 2 multiplayer.


So Halo 2 campaign gets the Anniversary treatment, but multiplayer will not, it will run on the old engine only, albeit in 1080p@60fps.


Then there are six maps that will look like Ascension running on an XBO native engine.


So in general, while playing Halo 2 multiplayer, unless you are on those 6 remastered maps, it will look like you are playing Halo 2 Vista Multi at 60fps 1080p..



Am I getting that correct?


Pretty much.


Same with CE, the maps will look like they did originally but at 1080p and 60fps.
 
I admit, I am now, for the first time, actually tempted to get an Xbone... But the idea of paying for Live keeps bringing me back to my senses.

You gotta pay for PS+ to play multiplayer on PS4. The hard truth is that if you want multiplayer gaming on consoles going into this gen and beyond, you'll likely need a subscription of some sort.

PS3's free multi was always an insane value, but sooner or later they had to start recouping costs somewhere.

I get it if you're a PC player, I get it and for your sake I hope that the PC release of this isn't too far off, although it needs to be far enough off not to cannibalize XB1 sales too. So if MS is considering it, I'm sure they're weighing 'how long is long enough, without being too long' for a PC release.
 
Then there are six maps that will look like Ascension running on an XBO native engine.

So in general, while playing Halo 2 multiplayer, unless you are on those 6 remastered maps, it will look like you are playing Halo 2 Vista Multi at 60fps 1080p..

Am I getting that correct?

From what I understand, Halo 2 multiplayer (containing all Halo 2 maps), and Halo 2 Anniversary multiplayer (containing 6 remade maps) are two separate things. So those 6 maps come in two flavors, Halo 2 and Halo 2 Anniversary.
 
Ok I think this was answered above, but I want to make sure this is right. Two questions:

In lobby for multiplayer, will be be able to switch between games on the fly? ex: halo 1 hang em high --> guardian halo 3.

2. Will gameplay be specific to that engine when we play? For instance, will I actually be playing halo 1 engine, pistol and all, or a modified halo 4 engine?
 
From what I understand, Halo 2 multiplayer (containing all Halo 2 maps), and Halo 2 Anniversary multiplayer (containing 6 remade maps) are two separate things. So those 6 maps come in two flavors, Halo 2 and Halo 2 Anniversary.

This is correct, from my understanding.
 
Dedicated servers are such a big deal along with the 60 fps.
Hopefully this becomes an industry standard. Online FPS should all run at locked 60 fps on dedicated servers.

Can't wait for this. The more I think about it the better it gets.

I'm even excited for the Ridley Scott tv show thing. I'm gonna be absolutely consumed by Halo for months and months.
 
Actually, Bungie was correct about bloom - they couldn't change it without breaking LAN compatibility, which they had never done for any Halo title, ever. 343 made the bloom changeable, and in the process Reach 1.0 is not compatible with Reach 1.1 on LAN, because it's a client side change.

No, they weren't "correct." They claimed it couldn't be done and that it couldn't be made an option. That wasn't true. LAN compatibility is a whole different issue and hardly an excuse with how easy it is to pull down a title update. Bungie was stubborn, made excuses, and misled the community in an effort to stand behind the mistake that was bloom. It should have never existed or at the very least been a custom gametype selectable option, but Bungie insisted on shoving it down the throats of unhappy players.

Literally any counter you could have thought of would have a counter-counter because modders had the keys to the kingdom on the original Xbox. All Bungie did was make modders detectable faster, not block them. By the time 1.5 came out, modding on 360 was more profitable, and most of them had moved on. The patch kiddies didn't have the expertise to get around the checks. "The system being compromised" is in fact, a valid excuse, because they were helpless against any local exploits. Every developer was. By the time 1.5 came out it wasn't even hard to run your own code on the Xbox - all you had to do was take the hard drive out of it, put it in your computer, wait 5 minutes and the entire thing was yours.

There isn't really a counter for server-side hash verification, short of a collision attack. Assuming you use an algorithm like SHA-1, that's not a problem either, because the collision attack possibility is only theoretical and no actual collision has been produced. And if countless computer scientists, cryptologists, and government agencies haven't managed to produce a collision over the past twenty years, some script kiddies trying to cheat in online games sure as hell aren't going to figure out.

Hell, you wouldn't even need to go that far, just check the built-in signature system in the .map header and make sure it matches the server side copy. It would be slightly less secure than a full hash compute in that it would theoretically be more vulnerable to a collision attack, but again, collision attacks are not the type of thing script kiddies are going to be capable of doing to cheat in an online game.

Regarding the system security you mentioned, the example you gave was for softmodding via an IDE unlock timing vulnerability. This, like mod chips and other soft mod methods, did in fact allow you to run modified or homebrew executables by loading a modified BIOS into memory which skipped the xbe signature and media flag security checks. However, modified BIOSes were immediately detectable by Xbox Live, and you were unable to actually get on Live with a modified BIOS in memory. What was gained was filesystem access in the interim while the modified BIOS was there, allowing modification of non-.xbe files, i.e. files not signed with MS's private key.

Halo 2's vulnerability was in that the map files could be modified rather than the main executable, due to the way the Blam! engine handles game settings and resources. Bungie implemented security checks against this (the aforementioned map signatures) and even additional checks in the DLC. However, Bungie being Bungie, they used their own in-house method rather than a more standard and logical hash algorithm. And, surely enough, it was defeated almost immediately.

The right thing to do would have been to admit that their in-house algorithms were useless in a security context, abandon relying on them as an anti-cheat method, and switch over to a proven hashing algorithm and server-side verification as implemented in a patch. Instead, they denied the problem and did absolutely nothing until 1.5 came along and the game was already pretty much dead.

There's no way around it - Bungie was ignorant, negligent, and unwilling to respond appropriately to the cheating and security issues in their game. They are to blame.
 
Ascension is confirmed.
Agreed on Lockout.
I don't think Zanzibar will be in since it was remade pretty well for Halo 3.
Headlong had a Halo reach remake, but maybe.
Ivory Tower, same as Headlong, but there's a chance.
Midship had a nice remake for Halo 3 also..

My list:
-Ascension
-Lockout (classic map, and Halo 3 version was not a true remake)
-Turf
-Terminal
-Coagulation (too much of a classic)
-Sanctuary (symmetrical map to balance)

Now that I've thought about it for a while, I don't really care which maps get the anniversary treatment. If all of them are going to be playable online in original multiplayer, that's enough for me.

Zanzibar is already confirmed to be one of the six though. Burial Mounds is classic Halo 2 though so I imagine that being one of them.
 
Still a bit confused on the Halo 2 multiplayer.


So Halo 2 campaign gets the Anniversary treatment, but multiplayer will not, it will run on the old engine only, albeit in 1080p@60fps.


Then there are six maps that will look like Ascension running on an XBO native engine.


So in general, while playing Halo 2 multiplayer, unless you are on those 6 remastered maps, it will look like you are playing Halo 2 Vista Multi at 60fps 1080p..



Am I getting that correct?

but in 16:9
 
There's no way around it - Bungie was ignorant, negligent, and unwilling to respond appropriately to the cheating and security issues in their game. They are to blame.

The map security issues never should have happened. It was absolute madness not to take full advantage of their best weapon (that the XBE couldn't be modified on Xbox Live), and use that to ensure map integrity.

At least with some of the networking exploits, there was the legitimate excuse that patching in fixes was difficult and dangerous. It's hard to imagine that proper hash checks built into the menu/ui component would have been likely to break the game.
 
Ok I think this was answered above, but I want to make sure this is right. Two questions:

In lobby for multiplayer, will be be able to switch between games on the fly? ex: halo 1 hang em high --> guardian halo 3.

2. Will gameplay be specific to that engine when we play? For instance, will I actually be playing halo 1 engine, pistol and all, or a modified halo 4 engine?

1. Yup, you'll vote on what map you want to play then load into the engine that the map runs on.

2. The gameplay is entirely the original, no modified Halo 4 engines. If you're playing on Blood Gulch you're playing CE, if you're on Coagulation you're playing Halo 2 etc.
 
Like I'm 17 again. Me and my bud planning a campaign marathon similar to our Gears N Beers nights. Can't freaking wait. Also it will be great for peeps that missed out on Halo 2 online to get a chance now.
 
Goddammit I'm going to end up owning all 3 consoles by the end of this year. I don't even game all that often but I've already accepted this reality. Gonna wait until Black Friday for some nice deals on XB1/Wii U but both will be mine. And it will be glorious. This game sealed the deal for me as far as the XB1 is concerned. Nice job, nice turnaround by MS.
 
No it didn't.

The XBone GPU (1,310 GFLOPS) whcih is about as fast as the Radeon 7790 is about 6x faster than the 360 (240 GFLOPS) GPU which is about as fast as the Radeon X1900, not even taking into consideration the other technological advancements (The two chips are 6 generations apart). They could pretty much throw the code at it without optimizations, and the game would probably easily run at 1080p. I wouldn't be surprised if it could run at 4K even. All the coding they probably did was due to moving architectures (PPC to x86-64) and DirectX versions and/or GPU specific code (like eDRAM etc.).

I'm not even talking about the GPU. I was talking about the CPU. Those game codes were written for a high clock triple core in order CPU. Taking that and making it run on a low clock octo core OOOe CPU can't be trivial. It can't be simple as recompiling for X86 from PPC.
 
I'd like to see
- Ascension
- Burial Mounds
- Midship
- Relic
- Colossus
- Turf

I know may not be the mainstream favorites, but they were all great maps!
 
Top Bottom