EVERYTHING BROKEN in Halo MCC Reach : Tip Of The Spear
HTML-код
- Опубликовано: 8 апр 2024
- This documents all the shader, lighting, shadow and visual issues within Cutscenes of "Tip Of The Spear" in Halo Reach on the Master Chief Collection. Totaling 13 visual bugs within 3 cutscenes
If you care about the MCC being on par with legacy graphics and preserving these games properly, please file tickets on the Halo support site: support.halowaypoint.com/hc/e...
The community bug list by @whyyoutube : docs.google.com/spreadsheets/...
This video is inspired by @whyyoutube and his "Graphical Issues" series 
Игры
![Jelly Roll - Dead End Road (From Twisters: The Album) [Official Music Video]](http://i.ytimg.com/vi/_Mb8CqKW4R8/mqdefault.jpg)
Jesus f•cking christ it's worse than I thought.
I swear, I broke out the 360 to experience this game again and while it took a while for my brain to adjust to the system _chugging_ during intensive moments, once it did, those little subtleties made the experience that much better.
The armor _did_ have that matte finish. Visors _did_ look extremely reflective. Lighting _was_ more atmospheric. _Rain_ was more noticeable.
The fact that so many in the gaming public have been effectively *gaslit* by MCC is such _a colossal_ f•cking shame.
I don't think these issues are severely impacting new players' experiences on MCC. My first playthrough of the games was on MCC and I had a great time.
That said, a lot of these little touches that are missing make the games feel way more dated than they are.
This is the least buggy mission sadly. Long Night of Solace is extremely bugged.
The highest number of counted issues so far
ruclips.net/video/0FJkTWHNQ3w/видео.html
@@Skitt64Gaming the problem is - it causes the whole false rose-tinted glasses since "the game never had it and this is the easiest to boot up"
also I think due to 60 FPS, I swear the Covenant shoot faster and causing me to die on the Falcon Rail Section of Exodus, especially the part over the Beach and dying to Banshees I cant even hit on the other side that never happened on the 360.
@@watch.v-dQw4w9WgXcQ i think the higher fps does make them more aggressive, i remember looking up why the saber section in long night at solace on legendary was so hard or if i was doing something'l wrong and one of the things people said was the higher fps making enemies more aggressive
@@Whoatedmycookiez dude get a life no one cares so, stop nit pick over stupid crap.
I mean I just launched tip of the spear now, and the trooper there has a backpack, I'd say its just randomised like most things in halo when it comes to enemies and npc's
The Frigate autocannon projectiles are really weird, i have no idea why that light volume tag acts like that, it does have a color function which makes the round look like its cooling off mid flight. Somehow it just turns green, blue purple and flickers in and out.
Taking the light volume system tag from any other turret like the M71 Scythe fixes the issue.
Maybe 343 thought that they needed to fire tracers rounds? No idea why though...
@@LockeLynx there are a number of tag related issues in the HREK tagset. Like the frigate_battles firing effect from Condemned doesn't even exist in the tagset.
To me it looks like the light volume tag straight up is just corrupted in some weird way.
i was playing reach on the 360 disc and the army troopers had no backpacks
By chance it's not a pirated copy?
@@gustavojimenez9980 could be that it’s RNG that determines the marine character model.
About the marines backpack, they equipment is randomized. The backpack could be one of these always random equipments(Btw i'm using my memory, so the backpack could not be one of these always random equipments, plz correct me if i'm wrong)
I don't think they're randomized in cutscenes actually. The trooper grabbed by the Zealot at the end of Winter Contingency always has the same uniform, armor variant and a balaclava. Marines at Long Night of Solace also always have the exact same gear in the cutscene.
@@viperactual6036 The trooper grabbed by the zealot has it's own specific variant (Dead_kiva if i remember properly)
About "long night of solace", i have to check
@@purporium6902 Do you know if other cutscene troopers have set models for them? Like the marines at the end of The Package or the ODSTs at the start of the 2nd last mission?
0:06 They're Army Troopers, no Marines.
And?
I think every halo fan is so used to saying Marines because that's who the Spartans usually chill with
@@UrBoiEthanMikl It's not a big deal but in real-life it is considered disrespectful among certain armed forces to identify their service branch incorrectly.
@@viperactual6036
Well, woopdy freaking doo, last time I checked Halo was a fictional video game with fictional space branches.
If you feel 'disrespected' because some asshat on the internet got 2 fictional space branches mixed up, then that says more about you than it does the actual video...
@@UrBoiEthanMikl I know? No need to be rude, I simply offered an answer to your question. Mislabeling troopers as marines is an easy mistake to make, just like some confuse soldiers and marines IRL.
I think the troopers backpack is randomized, it’s not a consistent thing even in the og. Regarding “glow,” I’m pretty sure it’s a bloom toggle thing, but I can’t say for certain
Not to mention at the very start of the cinematic in the MCC-version of the mission where there's static .jpg-renders of Banshees on the horizon before the pylon tower is blown up.
Tbf that’s in the original game, it’s just much less noticeable due to the 720p original resolution of Reach.
@@MyToastyToast Hmm, are you sure? I don't remember seeing it back on the 360...
@@viperactual6036 sorry I misunderstood what you meant - yeah the banshees showing up on Auntie-Dot’s briefing screen are a MCC glitch
The fact that the xbox one couldnt handle halo reach graphics is hilarious
What platform are you recording the MCC on? With this effectively being available on 3 or 5 platforms (depending on how you look at it), I'm curious if the MCC irregularities are consistent across all of them or are only reproduceable on one or some.
Going on a bit of a tangent here, it always makes me wonder what technical thing behind the scenes causes these sorts of bugs/changes between versions. I'm sure none of these are intentional, and it's fascinating it think about at what point along the porting process causes these sorts of issues. Taking a game from a singular platform, the Xbox 360, to several others (with PC being a platform of technically unlimited configurations) is nearly impossible to do with caveats like this which makes it all the more interesting to see what causes them. In the updates the MCC team has given in making improvements to the graphics of the games within in, they've been pretty thorough in explaining what their findings were and how they fixed them which has made for interesting reads. I'd be curious if any of it is related to the increase in resolution, since it was originally designed entirely around being played natively at 720p.
Assuming that there's still a team working on improving the MCC, I'm sure these sorts of videos help point them in the right directions to look for fixes! It'd certainly be great to see Reach get as close as possible to the original stylistic fidelity it was released in, but at the same time these certainly aren't stopping me from playing Reach on the PC. All of the advantages granted by the MCC greatly outweigh some of the visual bugs that are, admittedly, difficult to spot in motion.
Though I still miss all of the original menus from each games.
I recorded MCC on PC. There are a few differences. The biggest issue is Xbox Series X has an awful blurring filter that PC doesn’t have and Legacy didn’t have.
Every issue I’ve documented so far is on every platform.
All good, I like tangents.
That’s exactly correct. Bungie hardcoded post processing effects like bloom, ambient occlusion, and Depth of Field to the game resolution so the console didn’t have to work as hard. When 343 ported the game to PC they never fixed this. So changing your resolution will alter these effects.
The higher your resolution the less bloom you’ll see, same with everything else
AO being broken is what I believe is breaking the little shadows on characters.
Depth of field was kinda fixed but still is bound to resolution. It’s breaking colours and causing weird issues now with saturation unfortunately.
All these problems extend to EVERY 360 game in the collection. Every game has its colours broken and Post Processing issues.
Reach seems to be the worst for graphics problems though.
Raindrops were also bound to frame rate and are longer and thinner than legacy.
Yeah, even if they’re small. It’s still a downgrade from legacy and I really hope a team fixes it someday because preserving these games is important. I don’t want another Gearbox CE situation.
I wish they kept the menus. I love sitting on them and just vibing with the feels. The new menus feel so sterile and unfriendly to navigate
There’s definite issues on Xbox version as well, I can confirm. The thing that keeps standing out to me is the lighting being all glare in H:R
@@Whoatedmycookiez Mcc was abandoned in june 2023, look it up.
#Fire343
Fun fact armour colour in MCC not same original look
It might look the same generally but usually the game is ported to a newer engine that will just break everything. Prime example look at Halo CE and the poor port gear box did that broke all the shaders and bump maps. It’s not always as straight forward as it sounds. I know the argument would be “they’re a professional dev how’d they miss so much?” Well they didn’t make the original Reach so finer details can easily be overlooked by people not familiar with the original game. These are also things that are considered an acceptable margin of error. A true port could only be done be a hardcore fan with years of spare time.
I wonder if some of these are intentional choices, like the extra geometry in the Warthog, or removing the glow on the spire to make it more visible
pretty sure the glow is minimised and the extra warthog geometry is just a small touch
Considering the MCC Devs did tweak some things with Reaches Editing Kit and they have access to some old bungie stuff like hipoly models somebody could've added that geo.
Nothing here is “broken” but these are details that really ought to be there. I wonder if anything here can be modded back in
@@LateNightHalo This is sadly one of the good levels. Long Night of Solace is extremely bad
Nearly everything is bugged to some degree.
Lighting, materials, effects and audio. Final count was over 20 issues IIRC
ruclips.net/video/0FJkTWHNQ3w/видео.htmlsi=roVACcSQsb3SSdTw
P.S love your content, thanks for commenting. Made me smile ❤️
Fucking idiot of course is broken
@@Whoatedmycookiez Haven't played the original 360 version but I heard Long Night of Solace space battles are unusually more difficult in MCC, is this true?
@thetower8553 yes that is true. The new 60 FPS tickrate effects the AI.
They can now fire faster than previously possible, meaning you die faster than originally intended.
Thanks I'll never unsee this x'D
I wasn’t fully aware of the extent of the darkening issue. Was that introduced when they added bloom into the game? I feel like I remember the game being brighter and easier to see before that update, but that may just be my dislike of heavy bloom coloring my memories.
It's been an issue since launch and has to do with the gamma being broken during porting.
MCC's bloom is way stronger than it's supposed to be as well which isn't helping
The cutscenes in New Alexandria are also now overly BRIGHT instead of being dark and look awful.
ruclips.net/video/XMulyO2bnC0/видео.html
@@Whoatedmycookiez thank you for meticulously tracking these things. I hate that my mind might attribute an inferior version of an effect or texture to the original execution of a scene just because I have now spent the vast majority of my halo time in MCC. It’s nice to have a reality check for me!
That's the unfortunate nature of many of these issues. As well as Reach being 14 years old
If you hated bloom back then, you'd assume it was always this bad.
It sucks that Reach, 3, ODST and 4 are left with many issues that most people don't care about and thus will never be fixed
I'm glad some people do care about it though. Thank you for being nice to me and my stupid attention to detail
The guys on the warthog are army troopers not marines. And the equipment is randomized. They can have balaclavas or face paints or anything really.
Im pretty sure i got a bug where In Halo 3 ODST The engineer randomly dies on the last part of the mission after riding the tank which is insanely confusing if I'm the only one getting this bug i really don't know literally restarted the mission too but it still happens
Super late - but this happens if you have the either the skull that accelerates explosions or the skull that accelerates impact physics on. The game gives you a warning if you load that level with the skull on that it’ll glitch out as the original game did not launch with this skull (it was added in when 343 made all the Halo 2 skulls work in each game). The fix is parking the scorpion tank in front of the off-ramp without going down it. It will cause the engineer and Dare to teleport out of the Oliphant rather than “climb” out, which is what causes the glitch
@@MyToastyToast okay got u i did have these skulls on when i was doing some mods
@@solidxsnackssnfearless5371 yeah it’s one of those things where if they “fixed” it then probably something bigger would break. It’s not a defense of 343 at all but in that particular instance I’d give them a pass because they could have easily decided to just keep ODST to the skulls the game had at launch
With all these graphics comparisons 343 felt inclined to bring back the Legacy Bloom Effect but it flickers so much during cutscenes that it becomes really distracting. I went back to get some footage of the last mission and let’s just seeing it broken kind of sucks.
I don’t want people to resort to emulation just to upscale the legacy graphics. There could be a fan patch one day, but who knows if that would be enough…
The bloom only fickers at 4K. It's a known issue on all platforms.
Bloom was a part of the original game but it was way less prominent in legacy than MCC.
343 seem to have thrown the sliders way too far up, and it still scales with resolution. Which is probably causing the flickering problem.
@@Whoatedmycookiez I am playing in 1440p and the issues really bother me.
@CyberVirtual interesting. What platform?
I was playing on PC
The Steam Version to be specific.
Any upscaling or downscaling at play?
Does it sort itself if you set res to 1080p?
Well, graphic mistakes may be sad, but hey, I finished it on the anniversary graphics and didn't notice a single one because I was too consumed by either the story or the action, I understand they didn't really bother with it but it's still sad to see how little effort was actually given into these details, unlike truly dedicated Devs would
343 Managers try to do anything right challenge: Impossible
Silly, they did.
And then pooped their game back up. (Shop prices)
"Reclaimer" mission in H4, gameplay in Guardians, Chief being very humanized in Infinite, but without being exaggerated. Well, 3 things. Not bad for 343 getting 3 things right over 12 years
@@Bocchi-chi The fact that 343 barely puts a new actual feature in infinite for over the course of 3 years, then making the next game come out in at least another 3-4, not adding new vehicles bc it doesn't give them money, or anything else for that matter, is just depressing.
Halo as a franchise will die, that is if 343 doesn't make a solid next game, people will not be able to trust them after the years upon years of broken promises.
I'd probably just resort to making cringy fanfictions honestly.
@@RuthlessSpartanB320 Yeah, I know. The problem is that many are not understanding that this time it was less of the 343's fault. Microsoft kept changing employees during the development of Infinite and for the stupid reason that they didn't stay there long enough to receive more benefits. This means that no matter how much was invested in the game, changing teams caused a lot of delay and in 6 years of waiting, we had content equivalent to a 2-3 year wait. All because of Microsoft's negligence. H4 and Guardians were mostly 343's fault
@@Bocchi-chi well, it's on both Microsoft and 343 mishandling the entirety of the franchise.
holy fuck, do they even do comparisons themselves to actually make sure? Why do they have to leave it to the community to point this out again like in CE? It might be small details but shit adds up in the long run imo
I don’t even have MCC installed at this point lmao, they basically fucked up the classic titles
343 moment.
Subscribed!
man, Ruffian Games really dropped the ball on this one.. didn't even have "enhanced lighting" to hide theae issues behind
I'm curious, you mentioned Marines, however there aren't any in this video.
No fucking way they used covenant tracers instead of human on this mission, im fucking dead there’s no excuse for that. What the fuck.
Not broken all looks same to me 😂
Words cannot express how much I loathe 343 and their epic mishandling of the franchise at every possible turn.
It's not that serious you absolute twat
Bro shut the f**k up. People out there dying in the world you don’t know what “loathing” means.
And you got all that from a few missing shadows and some strange lightings? Some people only seek to be unhappy I suppose.
@@Mehfargahdur read it again strawman.
@@robbsix836 I did. I guess I might need to spell it out for you, since you’re so hasty to be rude. I meant that by “it seems like a disproportionate response to a video where it highlights some downgrades from the original that are mostly easily passed by with little impact”.
There. I did all the interpretation for you.
I really don’t agree with this. It just seems very _petty_ to make a statement like the title does and then show me like only 3 actual problems that are “important”. The UNSC Frigates shooting Covenant plasma and/or having weird cool off effects, Jorge’s shadow and stuff like that is the issue. Those Army Troopers having no backpacks doesn’t affect anything (I saw people claiming it could be randomized equipment but I can’t confirm). Brighter explosions/spire effects looked worse (for me personally). And a lost shadow pr two isn’t that big of a deal*. At the end of the day Reach wasn’t good because the graphics were good. It was always the story. (This is also coming from a newcomer to the franchise. I also would like to clarify that I’m not pandering 343. I believe they did Halo an injustice in the end despite their best efforts or lack thereof.)
*Unless it completely breaks physics and stuff like that.
Why does it feel like we just got the mobile version? Hahahaha.
MCC makes you forget Halo used to actually be really polished and gorgeous for the hardware they had to made it on, it's the small things that really add up, I miss when Halo was good
They would've had to have replaced that marine model with another one for this to even be a thing. Seriously, how the fuck does that even happen? This is like replacing the Zealots in the cutscenes with Ultras or some shit.
Not necessarily. I can't see any other differences with it. I can only assume Bungie built toggles into the characters for backpacks and other such gear to make creating all the variants easier
This toggle was left off or reset when the game was ported
@@Whoatedmycookiez Okay that would make a lot more sense. I figured each marine model was unique like the Covenant, I didn't realize all the equipment they wear was a different thing.
they sabotage the old games to sell newer shiny ones
All of you need to touch grass.
Wow 343 is trash
Bro people in these comments are like "343 ruined the game!!1" over like 3 minor graphical details.
The thing is this:
Yes there are issues, but if you hate 343 over them, then you are the issue. Instead of hating 343, we should point out bugs like this to help them.
It's no easy task porting games over, and it's the least we could do.
@@m16-a2 Finally, some common sense.
details make difference
@@nosejajalol5282 So does respect.
@@nosejajalol5282 and that's why we must warn *them* and not just hate *them*
Generally I don't mind minor issues like this. As long as there's nothing gamebreaking, I'm just glad to be able to play an old game again.
Bro decided to call them “Marines” instead of army troopers, bro broke himself-
Bro decided to focus on him calling "Army troopers" Marines, bro missed the whole point-
@@UrBoiEthanMikl Oh, no I got the point, either way THEY AREN’T MARINES, THE MARINES ARE ON THE LEVEL “THE PILLAR OF AUTUMN”
PLEASE RECOGNISE 343i THIS ISN’T GOOD ENOUGH WHEN THE 360 VERSION LOOKS BETTER THAN THE RE-RELEASE 😢
All they had to do was port it.
Yeah it’s so easy, they just had to click and drag the files into the mcc folder
None of these items are "broken". This is just nitpicking...literally nothing.
The only two inconsistencies actually worth noting are as follows (and even these are overstated):
1. The warthog didnt explode.
2. The blue lasers coming from the human ship.
Everything else is just an improvement on graphics/shaders for the game as a whole.
Anybody who thinks 343 mishandled MCC is just blinded by unjustified hate. It is literally the best possible thing any Halo fan could've asked for. Every Halo game bundled together, with huge graphical improvements (with the option to toggle legacy graphics for some titles). And people still try to find a way to complain?
You're getting a lot from just a single word. The group of people spending their free time to identify and document these differences (look at the linked spreadsheet) must have nothing but a ton of love for Halo. These people are digging into the files and mod support to document the littlest of differences. This collection of issues could prove invaluable to 343 if they're ever allowed to take a big crack at the MCC again. Mind you, work like this already paid off once before. Members of the community documented numerous issues with the PC port of Halo CE which followed into Halo CE Anniversary and then into MCC. Many were finally fixed in May of 2021, 18 years after they were first introduced and documented. I really hope these people continue their efforts.
Most the shadows were broken, he wasn't nitpicking anything.
If you think "Everything else is just an improvement" then you must watch RUclips on 480p resolution.
Anybody who thinks 343 mishandled MCC is just blinded by unjustified hate. Orrrr the fact that MCC was basically unplayable for YEARS until it came to PC. It still has issues, but better than it was.
I could have ported the halo games better
@@googleuser4720 do it
@@googleuser4720bullshit
gonna be honest, 90% of the shit you showed is almost meaningless. there are a couple that do actually very much matter like the projectiles, but for fuck's sake how do people look at this and actually think MCC is somehow bad
yall wanna see a bad port? yall are welcome to browse the sonic library of shitty unoptimized ports with graphical issues that change the entire style of the game
MCC is actually insanely good, the most major difference is *some* effects not scaling with resolution.
343 has ruined MCC
Nah
they're literally just minor details dude, you're not gonna die because noble six doesn't have the extra inch on his cock that he did back in 2011.
Grow up you entiled cry baby
Reason why this shit is broken is because MCC is slipspace engine, which is the shitty engine that 4,5 and infinite run on so they can cram in DLC.
Every Halo game on MCC is more or less running in emulation. with slipspace trying to emulate the -Blam- engine (What Bungie used for Halo 1-Reach [and ONI])
I think you have allucinations
the guy is just a drama queen, screaming over some minor graphic effects missing
Yeah, these aren't even any big deals. Like... dudes in the comments need to fucking chill