The Graphical Issues of Halo Reach (MCC)

[@CFunk99]

For me, I miss the shadows, the colors, and the bloom on the original, but I prefer the framerate, no film grain, and no motion blur on MCC.

[@JZStudiosonline]

That's a super weird motion blur I've never seen before, it's kind of trippy. It would probably actually work pretty well with higher res/framerate.

[@gonnsolo8506]

A good port of the game would have the film grain and motion blur as toggleable options, as well as having the ability to turn bloom on or off

[@d7656]

@@gonnsolo8506 Exactly what I was saying.

[@VictimHazard]

ohmy god, i was wondering why the fuck it felt like my DMR was shooting blanks on MCC. i was like "i don't remember my aim being this dogshit on the 360". fuck bloom in general though

[@gonnsolo8506]

@@VictimHazard we're talking about the visual effect called bloom, where light reflected blurs part of the screen, not the game mechanic bloom. Reticle bloom was actually more intense in the 360 days and it got toned down for MCC multiplayer (the campaign keeps the original reticle bloom values though)

[@RazorToshiba]

As a programmer I can tell you why the framerate and resolution cause these issues, the game was built with a specific resolution and frame rate in mind so a lot of the effects are hard coded as numbers to make the calculations to run them faster and easier for the aging 360 hardware. So if a raindrop is scheduled to be generated every X frames, and fall at a rate of y inches per frame, and you change the framerate there are going to be a lot more raindrops generated that fall faster than they should. Same logic for anti aliasing and light bloom calculations. It's calculating based on a certain number of pixels away from a certain point, and changing resolution makes the effect take a smaller percent of the screenspace. As for shadows and other bugs I have no clue.

[@BudgiePanic]

There's always a trade off between optimization and portability. Obviously bungiee would've gone for insane levels of optimization. They never envisioned these games would one day be on PC

[@RazorToshiba]

@@BudgiePanic Exactly, and that means to fix these algorithms, they'll have to change out hard coded numbers with a formula to calculate the correct numbers based on the resolution, or set multiple preset hard coded possibilities in an array that can be swapped out for the resolutions the game supports, which would be more work but would keep the same speed optimization. Mainly it'd just be a lot of code replacement.

[@BudgiePanic]

@@RazorToshiba such engine revisions may not even be possible. We don't know how well Bungie documented their games, if Microsoft maintains the code base.

[@RazorToshiba]

@@BudgiePanic True, finding the right code to modify, and the likelyhood it doesn't break something else is most likely why these issues still persist

[@natayaway]

coincidentally, this is actually more physically accurate to real-world cameras. increasing the framerate while maintaining the same shutter speed of a camera would cause motion blur trails to appear smaller.

[@adnancharif9296]

Another thing to note: 1:20 The REACH title fades in with the color orange in Legacy, on MCC they just fade in as black.

[@jmccann6735]

I KNEW it was different 🤣🤣

[@alexanderrobins7497]

Blink and you miss it. Good eye! It is much more noticeable if you slow the video down.

[@Orlafilo]

And it was bloody GLORIOUS

[@doltBmB]

I think it's the missing bloom actually, since it is not uniformly yellowed

[@d3rpybac0n83]

My biggest gripe with the MCC changes is definitely the lack of ambient occlusion. The lack of the shadows retracts so much depth from the game and makes the lighting seem really flat

[@haydentravis3348]

Go into your graphics card settings and force AO there. Works really well, most of the time. Might flicker a bit.

[@d3rpybac0n83]

@@haydentravis3348 Hmm. I will have to look into that. Thanks for letting me know man

[@UltimateHalo117]

Really informative video, were it not for this, I probably wouldn't have ever picked up on these changes! Hopefully, it's something that can be resolved in the future :)

[@Commander_Raveth]

Sometimes even the render distance is bugging. Hello btw👋

[@BotBruh448]

honestly you and other Halo youtubers should probably bring light to this issue too, it might just get fixed if enough big voices start spreading the word

[@PackHunter117]

@@BotBruh448 Then it’ll give the MCC something to work on after releasing Flood and Elites to Firefight next week lol

[@BotBruh448]

@@PackHunter117 exactly bro, it should just be fixed

[@hervisdaubeny2784]

Ima be honest, If you didn't know an issue existed before watching a KZbin video I highly doubt its a problem

[@stevemartin2563]

Minor note: at 3:53, the effect missing primarily is "contact shadows". This is a small-distance shadow solution that's usually used on top of main shadows rendered by the game, often to fill gaps that may be caused. You can see this gap noticeably at 4:04 around the characters feet.

[@zenroles]

It's weird that they turned it off for MCC. I've played around with contact shadows on Blender myself and it doesn't seem to have any significant impact on performance from my experience. Could be engine limitation perhaps?

[@stevemartin2563]

@@zenroles without knowing the engine it's hard to say yeah. It's entirely possible that the contact shadows program would need to be rewritten for higher resolution or frame rate, or it just wasn't a priority under a given deadline.

[@PKspectre]

If CE and H2 MCC are anything to go by, I'm sure this'll be fixed someday. I'm glad 343 isn't leaving broken games as broken forever

[@haydentravis3348]

Micro$oft and 343i are doing such a great job on MCC, why they're ruining Infinite so bad is bonkers. Completely different approaches and one seems infinitely superior from an end-user perspective.

[@Stefantius]

So glad I get these games from Game Pass and don't actually give 343 any money, that's probably what kept me playing Infinite for a few weeks before dropping it

[@LyrisTheCat]

you say this, meanwhile a bug i had gotten on halo 4 campaing that i thought was so stupid and progression breaking was something "new" apparently the bug is on there since launch of halo 4 on mcc :) so yeah they don't care that much.

[@PKspectre]

@@LyrisTheCat I never really play 4 so I didn't realize lol. Still, though. They fixed up CE and 2, so there's still hope

[@Neomeniaaa]

@@LyrisTheCat They do care. You just have to remember the team working on MCC is small, and MCC is one hell of a project with like 11 different game engines, and code never meant to see the light of day again. Not to mention that for a while before infinite they were also ordered to create a lot more content by higher ups and the fanbase alike so their resources were spread even thinner. If the MCC team is allowed to keep working on MCC it will get fixed, of that i'm certain, but who knows how long it'll take.

[@elyastoohey6621]

Yeah I remember finding OG reach more cinematic. Personally I’m not too fussed. The big change that makes me annoyed is that on the space mission (long night of solace) when youre In the saber, on legendary the A.I has been changed to focus only on you when you don’t have cover. Meaning when you can’t just dogfight and have fun like the original. Especially with the Seraphs, you have to hide behind the oribotal defence platform, then pop out score a quick kill, then hide again. Turns the entire section into a hated grind for most players.

[@deem0n__]

That was the hardest part of the game on my legendary playthrough...

[@elyastoohey6621]

@@deem0n__ If you played it on MCC, then yeah it would be.

[@Randy.Bobandy]

I remember it being the same on legacy. They just fucking own you on Legendary.

[@elyastoohey6621]

@@Randy.BobandyIt's still tough on the old 360 version. But the A.I on mcc on legnedary will only target the player when the player is exposed.

[@goodguytyphlosion3347]

never noticed how much i actually like the og reach in terms of looks

[@mjolnirproductions1]

In a blog post way back they mentioned how they deliberately removed/toned down the film grain considering how heavy it was in the original title. I believe the motion blur was removed for similar reasons, although I do agree that should have been left as a toggle.

[@corvax8644]

I do like the film grain with night vision cause it feels like it makes more sense to show up there

[@dexedge4645]

why tone it down when you can have an option to either enable it or disable it?

[@MajoraZ]

Wow, I knew about the improper resolution scaling for postprocessing like lighting bloom, rain, blurring, etc made them less intense, but I never realized it led to so many missing shadows too.

[@Finger112]

ODST also has the same exactly Film Grain issue with the Film Grain being much more subtle, and the outlines on Night Vision are much more thinner on screen.

[@john-ek9gv]

good

[@corvax8644]

I honestly kinda wish the night vision outlines weren’t so bright. Reach’s night vision is so much better and doesn’t feel so gamified

[@CmdrKeene]

For all the flaws, greatly appreciate the fixed aliasing. That ghosting always drove me crazy in the original.

[@silas1414]

This is beautifully done and very much appreciated by those of us who understand the value of certain examples you have used, and the the level of detail, disregard the one person flailing and hyperventilating in the comments because you showed a white screen, for people after visual information that was actually the gold standard example and used in colour grading as it's so useful. This has been extremely helpful in guiding my decision of whether to purchase that version or not, considering I already have the original. My only question is whether there have been improvements to the issues since your upload?

[@octane_xj6284]

MCC Reach be like: Zack Snyder's Halo Reach

[@bitwolfy]

Supposedly the post processing was fixed with todays update, but I dont see any visual changes myself. Water is still broke as fuck.

[@DanielGonzalez-qq7gh]

I honestly prefer the toned down bloom in MCC. I always thought it was a bit too intense and glaring in the original 360 release. Additionally I think that it also matches the bleaker vibes Reach goes for. However, having it optional would be a neat addition to closely resemble its legacy counterpart

[@JZStudiosonline]

Bloom slider would be best. I almost always turn off bloom immediately since it's usually pretty overdone. If I could cut bloom by like, half, it'd be fine.

[@Spillow-C]

@@JZStudiosonline devs now hate bloom for some reason, they always erased it with all kind of remaster

[@blaniac6591]

Yeah the bloom makes me feel like I’ve just woken up lol

[@corvax8644]

Pretty much same. I can’t stand lighting bloom in any game just cause it makes stuff harder to see and especially in older games like reach, bioshock, and far cry 2, bloom makes stuff look kinda ugly

[@fourfingthing]

No wonder everythimg felt off when I played reach on MCC. I couldn’t quite describe why it seemed different, except the shield doors I noticed that they weren’t blue.

[@GrOuNdZeRo7777]

First time I played Reach was on PC so I never knew what was taken from us.

[@vandal3136]

I gotta say, I dig the MCC's reduced bloom and film grain (well, "dug," as of the August update), I thought the limited/lack of bloom vastly improved visual clarity. It did admittedly reduce the luminance of glowing objects, but I would prefer that over the vaseline-smeared mess that Reach on MCC is now. I get that it was supposed to better restore the MCC's presentation of the games as they originally appeared, but I'd really appreciate it if they added a toggle to for the bloom effects, because I find it damn hard to look at in its current state.

[@digitalfruitcake24]

You mentioned an August update... Did some of the stuff in this video get patched already?

[@vatti9999]

Reach elevators also doesn't let you use armor lock and I'm 75% sure on new alexander the banshees are bugged because they spawn way more frequently

[@Koborover]

I'm glad they removed light bloom, it's a graphical filter that was all the rage back in 2010. At first glance things look more flashy, but it mostly just boosts the contrast to the point where graphical details and sharpness are lost. I know it's how the game shipped, but some things are best left in the past IMHO.

[@alexanderrobins7497]

While I agree, it would be nice to have as an option setting. I always thought it went overboard in H2, but that doesn’t mean I want it completely eliminated either.

[@Fridgemasters]

bloom looked so ugly i’m so glad we moved past it

[@yuzzo92]

Same with motion blur. While not necessarily being a bad choice back then, it wouldn't really make sense to have it in an age where much higher framerates exist

[@gentlemanscarecrow5987]

I replayed Reach on PC and didn't even notice this stuff, mostly I was just impressed at how beautiful a game Reach always was, but when you point out the differences like this, it makes me realize how much prettier the MCC version could've been. The shadows and colors are the biggest letdowns if you ask me.

[@ExponentialCircle]

I knew it didn't look quite right! Thank you for pointing these out!

[@_MaZTeR_]

I hope they fix these issues, they did fix Halo CE and Halo 2 as well as Halo 4's cutscenes

[@Finger112]

Along with Reach getting its motion blur back as an optional feature like the Classic HUD in Combat Evolved in MCC, we should also get a 30 FPS option to play the games how all they originally were played on the original consoles (as all the games did originally play at this FPS until the MCC came out). On PC, you can actually enable this outside of the collection (and EAC allows this) but would be cool if we could play them how they originally were.

[@CrypticMantisTX55]

While you're at it, might as well add 4:3 aspect ratio. (Not sarcasm, in case I needed to clarify that.)

[@connoraber7781]

@@CrypticMantisTX55 That'd be dope AF, you can use 4:3 on PC, but only in windowed mode, so no black bars on the sides. They should add classic resolution options too, I wanna play CE MP at 640/480 or whatever it was, with 4:3 @ 30fps

[@corvax8644]

I mean there’s no point in doing that if they are able to fix issues with the current framerate. 30 fps is terrible for shooter games especially now that technology has improved a ton since 2010

[@Finger112]

@@corvax8644 Its just for Nostalgia sake with all the crazy things 343 has done so far for MCC, nothing personal.

[@rickylonghaul682]

I've actually done this a few times myself where I'll lock it to 30fps using RTSS and lower the res to 720p and plop on 'original' graphics just for the nostalgia. It's a shame the 4:3 only works in windowed because I'd totally do that too. Of course none of us are saying games should go back to being like this. It's just for the nostalgia and to see how we used to play. And to be honest, it's fine. You know, I firmly believe the smoothness of the frame rate is more important than how high it is. Like I'll take a perfectly smooth 30 over a 60 that constantly dips to 40. And boooooyyy can Halo do a smooth 30.

[@JZStudiosonline]

The bloom and AO is likely not a bug if it's tied to resolution. It was probably originally tied to the resolution on 360, so 343 would have to figure out how to either scale it based on resolution or make it not resolution based. Though with it being different at the same res as 360... that might be a bug.

[@Yofu]

Ambient Occlusion is an issue with the Blam! Engine actually, and it persists to this day in Destiny 2. I noticed it when I was comparing AA vs ingame Downsampling and Nvidia DLDSR on my own. The higher Res you go, the thinner the AO looks.

[@keenanrobinson7239]

Wow. I think the only bit I've really noticed was the weird water physics and the amount of bloom displayed. Never would've seen the others, great notes taken, why!

[@reichtangle7734]

Also there is a glitch on where you’re far away from say a rock, the rock will have like a black circular texture with lines on it which goes away when u get closer. It’s very noticeable and it really bugs me.

[@reichtangle7734]

@@HelghastStalker Ah I see, but you’d think that would have been fixed for mcc by now

[@reichtangle7734]

@@HelghastStalker Wow I’m stupid! I genuinely don’t have a clue when it comes game design and programming. Thanks for the info

[@suryaselvakumar5385]

Nice, your back!

[@Mega-Brick]

I read someone explain that although the temporal AA was some kind of processor-saving option, it inadvertently gave Reach a dream-like quality that fit the "legacy story" it focused on. It'd be neat to see that restored.

[@dexedge4645]

NO! Temporal AA is the worst kind of AA out there. it just apply smudge all over your screen and creates ghosting.

[@Mega-Brick]

@@dexedge4645 I know what Temporal AA does. The things you listed are the effects that _add_ to the 'dream-like' effect. Something terrible can be used to lovely results. It could be brought back just as an option or setting.

[@dexedge4645]

@@Mega-Brick I totally agree with having more options. But I'm legit curious to know why you want a gritty war themed game to be deam-like? 🧐

[@Mega-Brick]

@@dexedge4645 "Dream-like" doesn't always mean actual, pleasant dreams; it just means it feels a little less 'real' and 'present,' instead feeling more like an old vision or memory.

[@mrpiratefox4497]

Its literally a shit TAA implementation, nothing to do with "intended looks" or whatever shit you want to bring up

[@Spillow-C]

7:38 what a big difference here, the MCC looks kinda bad, i hope 343 will fix this like Halo CE and 2

[@klaytonb9609]

So that's... CE, 2, 3, and Reach with graphical issues/noticable differences to the original games. What else should we know about?

[@rkitchen69]

On the first mission just after you get off the helicopter and head down and make your way around the side building and the cliff side, the spinning windmills in the distance have glitchy animations. Was this in the original version?

[@yougotaknife]

No

[@masterranger167]

Wish these problems got more attention so 343 would bring the games closer to their original releases

[@mistaJ.]

Its still the same game what do you mean ??

[@akillzonefanboy3313]

Everyone please submit this issue the video covers along with all the other problems that MCC still has! We can make MCC the best it can be!

[@Wylie288]

8/10 things in this video aren't issues but deliberate improvements.

[@EddieFreak]

The shadows are definitely the most important part. The lighting looks pretty bad as a result

[@JoshL117]

Hey why, look at the wind turbines on the first mission of Reach. At higher framerates, you can see them jitter at the animation loop point.

[@admiralrimmer]

I doubt they'll bother doing much with MCC now that Infinite is out. Motion blur was removed from Reach but is present in Halo 3 with no option to turn it off which is something I wish they would have added.

[@86Fallowcp]

Probably halfway through Infinite's seasons they will try working on MCC. It will be really slow tho since most of the resources are being used on the former

[@Spillow-C]

if you play on pc you can remove it by edit some files

[@KevinKoolx]

Great breakdown of the graphical differences. I would have never noticed these!

[@cyd_hunter99]

I actually miss the motion blur. People tend to hate motion blur, but most people couldn't even tell you the difference between temporal AA and actual blur. blurring the corners looks great, and doesn't affect player skill even half as much as people like to pretend it does. temporal AA can fuck right off though, no idea why they brought it back in Infinite

[@samuraispiritsx]

even tho not all the things in the original 360 game look great, I feel they are integral to the look of reach.

[@CommanderSammer]

I never played halo reach before the mcc, I had no idea it was that pretty

[@munfurai8083]

The light bloom bug at around 3:42 is something I've noticed going on in just about all of MCC. It has that issue where it doesn't properly light up.

[@CatulCatana]

i miss the bloom and the grain, the cutscenes cinematography looks weird without that.

[@whitingpie5146]

This always happens with remasters, they break more than they improve and the "remaster" ends up looking worse than the original.

[@Wylie288]

The remaster looks vastly better. Its got some odd shadowmap bias issues, which is just a bug, then the missing AO is a bit odd but its likely just reach used a really odd method no one had time to port. Everything else is a visual improvement. Reach was in an era where really, really bad post processing was used and people have wanted it gone for a long time.

[@MadamLava094]

...I never even realized bloom was missing! That added a lot! Same for self-shadowing.

[@pieton9346]

Damn they really did this beautiful game dirty

[@TylerGarner0]

Mr. Why, I love you for putting the effort you do into what will always be my favorite game series. Halo is an incredibly rich game that deserves to be meticulously preserved in its original form, and I'm glad you're doing what you can to make this happen. I hope 343 eventually achieves the truly perfect 1:1 remaster. Reach in particular.

[@bonesbrigader]

This is also an issue in Halo CE Anniversary on the MCC. The lighting has been toned down from the 360 version making most lighting effects dull in comparison. I do hope one day we will get a fix through a next gen optimization atleast given the better processing power.

[@Brandon.S.Brooker]

Your videos are so informative.

[@xXblazmodzXx]

Great video! Since they're updating MCC Again, I'm hoping they'll be able to fix the visual issues with Reach, and the other games some more, as well ^^ It's odd that almost all these are tied to resolution, but hopefully maybe that means it can be fixed easier? I'm not sure, but I hope so.

[@joshuawewel2116]

No motion blur? No film grain? Good.

[@jpcarsmedia]

My first experience with Reach was on PC and I always thought something was off visually but couldn't pin it down since I didn't have an original copy on Xbox 360. Thanks for sharing. I hope these issues get addressed by the devs. Maybe open a ticket and share the link to the video?

[@Wylie288]

They won't because everything they removed were terrible effects and the game looks a lot better. The only feature that actually made the game look better thats missing is the AO. Which is likely just down to not having time to port a really old/odd method for the shadows.

[@BLAM5980]

@@Wylie288 It really doesn’t matter if you think they’re terrible or not. This video was made to bring awareness to the differences in both versions. This is about the visual preservation of Reach and Bungie’s vision for it. It being as accurate as possible to the original is what’s right. I agree with him about making them able to be toggled though. Some people don’t like or can’t handle it, so I get that. But for the people who want to experience Reach as it was meant to be originally: they should be able to do that.

[@Jellybob69]

I really hope they continue to fix stuff like this in future updates. Halo 2 classic’s audio needs fixed so badly.

[@MetaVaria]

Really great video. Hope these are address in the next few months! Definitely would love to see a toggle for film grain and motion blur (theyre not for me, but they need to be an option to uphold the legacy)

[@TheDaxter11]

Holy shit the water issues on MCC remind me of that Nvidia PhysX setting you could use on older games like Borderlands 2. Edit: Oh yeah, another big issue with Reach is 343 have fucked with the size of some armour pieces. The giant shoulder pad Emil uses for example, that's smaller than it was in Reach on the 360. As someone who used those all the time because I loved big, bulky armour, I can tell the difference. It also colours darker than the colour you use on it as well. Say you make your armour one type of blue in all colour options, those shoulder pads, and some others, will be darker despite using the same blue as the rest of your armour.

[@AdeneTzr]

I always found reach on mcc kinda strange and lacks something from the original version but i didnt know what it was

[@gate7clamp]

This is why I’m glad I still have my Xbox 360

[@johnpaulyoshida5690]

While not perfect especially for the contact shadows Reshade can definitely fix some of the color issues. The rest like water physics are definitely engine issues however.

[@doltBmB]

I would say the rain is not a bug, since the streak is a kind of fake motion blur, higher fps should be less streaked.

[@ryanwassink7622]

I was so excited about the higher resolutions and frame rate that I didn't notice this at all. Thank you for the video because now I can see how much has also been lost as well. Hopefully 343 fixes this but I won't get my hopes up.

[@muwuny]

So annoying that people only care about CE being broken because a big youtuber made a video about it and all the normals downloaded their new opinion from it. And now that CE is mostly fixed these same people just declare that MCC is "fixed now", when every other game is still broken.

[@billysuter]

There's a lot of issues with the port on mcc. The firefight AI is much too easy, in OG there was a way of adjusting the enemies aggressiveness and "shootiness" I feel like these were somehow turned down as default on the mcc

[@bigdaddychemster1201]

While I greatly prefer the mcc version, any good port would have the changes as a toggle in the options. Prime example: the Quake remaster has tons of graphical changes that you can simply turn off, and even includes the original version of the game as its own executable

[@dexedge4645]

YES THANK YOU! I'VE BEEN WAITING FOR THIS VIDEO FOR AGES!

[@_Bren__]

I still just play Reach on 360. I’m one of those people who prefers to play games on their original consoles.

[@Spillow-C]

On Xbox one or series x/s you can play the 360 version but with just higher framerate, the rest is identical

[@_Bren__]

@@Spillow-C Ah yes! I watched my brother try it out. It was actually really neat.

[@itoaster]

I’m glad you’ve taken the time to make a video like this - similar videos are the reason why 343 ever even fixed Halo 1 & Halo 2’s graphical issues, and with halo reach being my favorite game in the series for its cinematic details, all these little things add up to really make it a better experience - especially for new people who may not have played it on the 360 prior to MCC. None are inherently game breaking, but their absence does remove some of that “wow” factor we all had playing it back in 2010. It’s details like this that have made my girlfriend, who never played halo reach, want to hold off on the campaign until it’s either fixed or we have an opportunity to play it on a console through backwards compatibility (both PC, neither of us have an xbox console atm). I’ll definitely share this around and I hope others do the same - a video like this getting lots of traction has proven to get 343’s attention in the past, so here’s hoping it happens again!

[@alecjohnson5043]

I hope they fix this like they did with CE and h2a

[@YanAde]

a lot of this doesnt really bother me. but the BLOOM was so much of the "Reach Look" for me. it really isnt the same without it.

[@JAGtheTrekkieGEMINI1701]

*REMEMBER REACH*

[@SynthLizard8]

I honestly prefer MCC, having the Spartan armor have a matte color makes more sense to me as opposed to a bright sheen and you can see more of the texture.

[@corvax8644]

Legacy pretty much just looks more cinematic. Mcc does have some broken stuff but the clarity is way higher. I do wish for specifically the cutscenes they looked more like legacy but in game I mostly prefer mcc save for the color and shadowing bugs

[@falloutraider4168]

Another thing unrelated to this video is that the commando rear fanny pack is gone also the brim of the mark v b helmet is gone when you use the other helmet variants

[@Whoatedmycookiez]

To this day the opening cutscene still has OVER 20 shadow, shader and lighting issues/problems, on its own.

[@milkman1649]

Spectacular video my friend and great observations. Would like to see one on halo 3.

[@hereticstanlyhalo6916]

I think the major issues right now they need to focus on, are contact shadows and ambient occlusion.

[@Wylie288]

Those are the only issues. The rest were improvements. There is a reason those effects weren't ported. Its not going to happen. Its likely the method used was odd to port and the AO provided via AMD or Nvidia is going to be better quality anyway.

[@hereticstanlyhalo6916]

@@Wylie288 True dat, older consoles had their own provided way of rendering that stuff, now computers have a default of rendering it a certain way it'll look different, so it's hard to replicate it on a hardware that's no the same of pc's.

[@DoktorObvious]

In the level exodus when the civilian transport gets shot down the texture of the ship doesnt change. In fact it starts with the destroyed texture.

[@RED33Md]

I’m sure things like these will be added/fixed because the MCC team have been doing quite good with listening to feedback

[@ghostryu6662]

10 months later and no fix, yeah they really "care"

[@RED33Md]

@@ghostryu6662 I thought they fixed it? I haven’t seen any issues when I played a bout a month ago

[@billysuter]

The bleed through creates a lot of issues with social maps, it's fine for competitive but for social its too much, the maps are too big and you die much too quickly

[@ARC_Tiny]

I just found this channel glad I did! I subscribed

[@zeliph]

Good thing we have reshade to restore most of these visuals, right?

[@silas1414]

Okay well that was great, very thorough, super appreciate your meticulous work here. My question is; how does it stand as of today? Were these things patched? I'm primarily concerned with the visual presentation, so the colour temperature, the bloom, the shadows, the depth of field effects and motion blur. Were there any updates over the last two years since this video?

[@MrMightyZ]

Have they put in a music volume slider? I love the soundtrack but reason I can't play either version anymore is the compulsory music and the extremely loud volume of the music. The guns are always quiet but in parts of the campaign my assault rifle was quietly "t-t-t-t-t-t-t"-ing away while the music went "BOOOOOM TA DA DA DA BOOOOOM!" and it got especially noticeable after a few playthroughs. I loaded Reach on MCC and played long enough to confirm that the guns were still whispering and the music was still booming and haven't touched it since. But I'll reinstall if they've fixed it.

[@Skazzy3YT]

5:04 I'm pretty sure this was done on purpose with one of the season updates. In Legacy and and pre season 7 or 6, can't remember your reticle would move slightly upward when zoomed in. Never understood why. To me it makes sense to remove this.

[@Aceb_k]

For me, I like the visual defects of the original, it gives me nostalgia

[@roguespartan2854]

To be honest, I'm fine with the unnoticeable trade-offs for a crisper presentation and smoother frame rate

[@Tetsaga]

Thank you for caring about the game so much to make this! Hope they correct these issues!

[@dafarmer3721]

Also when holding weapons such as needler and plasma pistol as an elite they use both hands but shadow doesn’t show it

[@daedalus6433]

I don't like motion blur because of the fact that your eyes already blur motion naturally, and as such it just bogs down on your vision for not much gain.

[@yewtewbstew547]

Great video, hopefully they bring this stuff back. Maybe make things like the motion blur, grain and bloom tweakable in options, since I know not everyone likes those effects in games.

[@JonesBrothersProductionsiac]

I actually had no idea there were visual differences. I never saw anyone speak in these previously. Edit: Except for Motion Blur. I do actually wish that was in the MCC.

[@Helsinki40268]

while not specifically related to graphics, knives and other parts of armor don't appear in cutscenes or in gameplay.

[@Simte]

I think we might see the community work on mods to have a more accurate representation of legacy games. 343 won't bother for MCC for a while, they never implemented split-screen for instance, it bugs me a lot but as long as emulation isn't accurate elsewhere this is the only way to play them on PC.

[@corvax8644]

All they need to do is add steam workshop support and the rest of the game modding tools and I guarantee so many bugs and issues will be fixed within months just from community efforts

[@tiger_lord305]

Who plays split screen on PC?

[@corvax8644]

@@tiger_lord305 people who farm achievements that are co-op only

[@FierceElements]

The good news is with ReShade: You can colorise, posterize, mimic HDR bloom and mimic SSAO strengths using ReShade yes?

[@BudgiePanic]

I'm not surprised there are so many differences. The original games made use of the assumption that they would be running at 30FPS at a specific resolution.

[@corvax8644]

Holy shit the mcc water physics are that bad? I can’t believe I never noticed

[@spaceageGecko]

It's 100% because the original water physics were coded with 30FPS in mind, higher framerates make it go weird.

[@corvax8644]

@@spaceageGecko yeah I figured that’s why it was janky. Surprised the older games like h3 and odst don’t have as noticeable of physics issues tho

[@oscarkabowski8413]

I find myself constantly messing around with the HDR settings on the MCC when playing on my Xbox series X through an LG 4K OLED. I don’t know why but by default it has HDR brightness at maximum, contrast halfway and the paper white at like 0.5. Is this normal? All the colours look washed out, everything is kind of grey and too bright while the blacks don’t look dark enough. What do?!

[@Sushiwolves]

I felt like the mcc was off but now I know why.

[@randomcatdude]

the shadows look like a severe case of shadowmap bias being way too high, you can see at 4:04 how the shadow is clearly still there, just cut off at the parts where its close to what's actually casting the shadow this one is particularly strange to me -- resolution and framerate-dependent effects make sense, but this change makes no sense at all, it looks fine in the legacy game...