It is 100% worth submitting tickets, when i submitted ones for the h1a cutscenes i got a reply actually asking for more evidence and footage, so they do care.
@@Spendingryan They sadly haven't been fixed. If anything, cutscenes are now further broken with an incorrect FOV on top of the black bars still being there in 16:9 (cutscenes should be in true 16:9 with no black bars and the original framing intact). It does indicate that someone was aware of the issue and tried to adress it, though, so it's encouraging.
@strelokyas the stuff they fixed was the new bugs, which was the missing enemies from "Long Night of Solace" in halo reach, they are back now, and all of the crazy cutscene problems with halo anniversary, you know the props being swapped around.
Yeah I'm very aware of lots of these bugs, including brand new ones just added in the last update but even I didn't know some of these like the smoke, allthough I just played spartan ops myself in Xbox Series X and swear the antigravity arcing lightning actually was there, but there are bugs that are on pc and not xbox and vice versa.
Thank you for putting in the work to make this, I have noticed a bunch of small stuff like this all over MCC and as a player that plays halo 4 consistently it is noticable. Halo 4 was a very pretty game imo hope to see it again!
Halo 4 was so pretty. I really wish they had delayed it a year and launched on xbone. It would have been even prettier. Amazing they got it running on the 360
Yeah, the part I noticed on my own was the covenant cruiser centre spinning effect, and the asteroid base turrets, it is weird though as the portable railgun has very similar effects but works correctly.
@@HydratedBeansyes, but some of the textures are so pixelated that it hurts to look at and I'd feel an years worth of polishing since 343 was still new to the developing their own new game. And yes I know that some Bungie devs migrated over, but a lot stayed at Bungie itself so a lot were new to serious game development
@@readmyusernamecauseitssoreally they were pixelated because they needed to fit in like a gig of RAM with the higher res textures. The 360 was very out of date at this point
Wow, that may explain why it looks so damn strange in mcc. I remember playing it since release date on my 360 and loved all design aspects, the multiplayer blur, and bloom made it look so good, the game had it's flaws but was a blast in terms of art design. Someting felt we lost in MCC, and I always though it was just the resolution scaling and maybe my brain playing with good memories but no, design details are straight up gone.
@harbingerdawn no, the cutscene bug is brand new, they just literally somehow added these (h1a cutscene, halo reach, memory leak with AMD GPUs) bugs in the latest update.
Thank you for all the work you've done and continue to do in documenting issues like this in MCC! Your videos are a great resource. Just to help with bug documentation: 1:48: FOV isn't affecting bloom, but rather the visibility of fake lens flare/glow effects, which change visibility based on how large the source area appears on screen. The bloom effect itself, which as you point out is affected by render resolution, is the same fundamental issue that has affected other games in MCC, where the bloom radius is a fixed pixel size, rather than a fraction of client render resolution. 3:15: Specifically, the environment map reflection is absent on PC 6:25: Same root cause as the bloom issue, should require only a single fix by the devs 8:15: I suspect it's the same issue as the Banshee (lacking envmap reflections), but I'm not sure as for the rest, just... ffs 343 :|
@@gamerxt333 ...the work of documenting and cataloging all of these bugs? That's very time consuming. And how is whether any of the issues are resolved related to the work that Why has done in documenting them? Regarding what 343 does or doesn't know, you'd be surprised how often many issues are well-known in a community but not as well known among a dev team. There's also less of a priority placed on fixing bugs that aren't talked about vs ones that are. When you catalog and publish stuff like this, it 1) makes any claims of ignorance of the issues by 343 implausible, 2) helps centralize and document all bugs in each game in one place without that work needing to be done by the devs (who almost certainly are not allowed the time required for that, 343 has a notoriously small and overtaxed core programming team and is focused primarily on Halo Infinite, not MCC), and 3) spreads awareness and recognition of the issues within the community, increasing the volume of discussion about the bugs and putting pressure on the devs to fix them.
Thank you so much for highlighting these issues man, the last newest update (7th December 2022) did a number on poor mcc, especially the anniversary cutscenes and missing enemies in halo reach, and of course the AMD GPU memory leak.
@@nononoohfuck It's crazy how we see people complaining about 343 everywhere man. It's almost like they're a terrible company and people are sick of their shit
Great job, I admire your dedication, keep it up, open tickets and be the voice for all of us, truly all of us who can enjoy a better game will thank you
Thanks for sharing! I played a lot of H4 on my 360, and I just bought MCC, it was unfortunate to know that my pc doesen't run halo 4 very well, but it is even sadder to see what they've done to the graphics and what not :(
Hopefully 343 fixes it like they did for Halo 2 Anniversary and you can get some second-hand parts to upgrade your system! (assuming its a desktop and not a laptop)
@@PatrickHoffer Thank you! I do hope that this next update set most things right (simply listening to the community and ticket submissions), and not just add a bunch of new things
@whodatninja439 there's an update coming out today. They released a screenshot showing the Arbiter's Halo 2 armor textures finally corrected to look like the OG xbox version so they are still doing fixes.
I just found myself wondering about the graphic differences for 4 in MCC, having not thought about it for about 2 years. I did a search expecting to find a 5-year-old video and you uploaded this ONE day ago. Wow
I recently played the Xbox 360 copy of Halo 4 on my Series X. There is this bug during the Librarian cutscene in the chapter "Reclaimer." After you see the flashbacks of the Human-Forerunner war, it's supposed to transition (fade to white) back to Master Chief speaking to the Librarian and the rest of the cutscene. Instead, it fades to white, and it stays on the white screen for the rest of the cutscene. I tried reloading the save, and it still happened.
The decal bug gave me a lot of grief while making my recoil video. I wish I'd tested another map, because I just assumed Halo 4 had bad render distance and gave up before I got to the power weapons
Happy to report that the halo 1 anniversary cutscenes and missing halo reach enemies are fixed as part of that update that released today, i did check some if the halo 4 stuff but that hasn't been fixed though.
@XDLugia if you mean what levels and such were fixed, it was "Pillar Of Autumn", "343 Guilty Spark" for halo anniversary, there were incorrect object placements or missing objects in the cutscenes, and "Long Night Of Solace" was missing seraphs, anti air gunfire and repeated squad drops from pelicans and dropships, at the beginning of the level which is fixed now.
Probably most of the bugs in this video are caused by resolution, where the intensity/frequency is a fixed value and remains unchanged regardless of resolution.
Good lord there's so much missing. While this might not be everyone's favorite Halo, I'm really glad someone has been passionate enough to look for all these inconsistencies. The less available the originals become, the more glaring these issues become for preserving video game history.
Hopefully, all of these issues are resolved before MCC’s “final” update. However, that’s doubtful considering how Halo has been handled after all these years. After MCC’s “final” update, you should make a long video of every unresolved issue. Or a dedicated multi-part series of videos with a playlist.
I don't get this. "After how they treated halo" huh? They are treating MCC incredibly well. With tons of updates to bring the bad gearbox port and all the other games way closer to how they originally were and soon even with all the beta assets releasing. MCC never was in a better place and like I said has been treated better then 99% of all game releases from other studio's.
@@private1177 First of all, why use quotations when I never said “After how they treated Halo.” I said “how Halo has been handled after all these years.” Second of all, I said “how Halo has been HANDLED” not MCC (though MCC has been not been at a great state until recently). The franchise known as Halo has been HANDLED horribly under 343 Industries’ guidance, for instance; Halo 4 and 5’s art-style, sprint becoming a permanent fixture in mainline games, MCC’s launch, Halo 5 releasing unfinished, Halo 5’s story with Master Chief being in 3 missions (maybe they should have made Halo 5 and then release a spin-off called Halo 5: Guardians), Halo 5 removing spilt-screen, MCC’s continued lack of support until their decision to port to PC with some of the games launching with issues despite justifying staggered launch as a way to ensure quality, Halo Infinite releasing unfinished despite already botching Halo 5, Infinite’s story being terrible, Infinite being a soft-reboot thus brushing past everything 5 built up (though, 5 was kind of a soft-reboot of 4 and Spartan Ops), promise the return of spilt-screen only to cancel it 80% of the way completed, killing Rookie and Didact in a book (only to bring the Didact back again in another book), relegating 343 Guilty Spark’s return in a book, Halo TV show existing the way it is (make a Band of Brothers type show/Halo Wars intro cinematic. Humanity losses many battles wins a few then losses many more), MCC releasing on Windows Store but is not PlayAnywhere, etc. Rumor has it this may be MCC’s final update but there is still so much left to do in addition to quality parity, such as the introduction of console mod support that is just as robust if not better than Skyrim and Fallout 4. The Digsite content does not seem to be coming to console at all, even cut maps some of which are remakes. At the very least, add them as optional free DLC. Plus, Reach Elites should have customization on par with 3 and 2A, ability to make campaign playlists (modded ones too), port all the weapon/vehicle skins across the games, add weapon/vehicle skins to 2 and Reach, port the remainder of Halo Online content, add Mirage and Orion armor to games without them, etc.
This is one incredibly detailed video, showing the differences between the original and the remake. Your attention to detail is impeccable, and I admire the time and dedication to finding these anomalies. With specific reference to when you showed the FOV change making a lighting corona disappear, could be due to the corona only showing for a specific visual distance and changing the FOV put your character at a longer distance than the corona visibility was set to. I do however think that it isn't broken, it is just different, in some ways the reduced glare makes it better for my personal taste. What does the ticket submission say? I am running this game on completely different hardware, with completely different settings for every aspect of the game and it looks different, so please fix it.
The lighting bloom (including for the lava), shield doors, and the on-pc missing somke effects are a pretty big deal, if nothing else I hope those are fixed. BTW, there's some bugs I found I'm trying to figure out were in legacy or not for Halo 2. Is there a place I can contact you at about them? (can't use twqmtter to do so right now sadly)
Yeah i have a bunch of tickets that unfortunately have been sitting open for a year or two now. Some big stuff in my opinion too like how the Pelican sounds are just completely gone during H1 cutscenes for xbox players. Or how after a few updates ago now friendly Elites in Halo 2 will take collision damage and die when they go into a specific cover animation. Halo 2's rocket launcher also has a clipping barrel spin animation now. It's like it plays 2 spin animations everytime after firing 1 rocket now, happened a few updates ago, H1's rocket launcher had the issue at one point too but that got fixed eventually.
some of the FX like the water rippling in MCC is to me a great feature to make the maps feel less static and more definitive, however, most of the "issues" listed here I do have a problem with, like the bloom issues. Some things arent exactly a visual downgrade if the textures are more defined and more detailed, and that's basically was 343 did here, but they forgot the bloom. the hud issues arent that bad, but the actual graphical and FX issues arent that bad although a few are I will say though the MCC version is VERY highly defined and less blurry, the 360 version of a lot of the less old halo games like halo 4 and reach seem a bit blurry because of the bloom and resolution its running at... And Mcc just basically made it perfectly sharp but they basically forgot to re add the bloom effects that made a balance, and that's what I miss. the new ground effects are cool but the actual issues need to be fixed.
I always had this feeling that Halo 4 looked better than people gave it credit for and with so many graphical issues in MCC maybe that wasn't easy to convey to people
In a some of these videos the differences are technically improvements. All the resolution scaling issues and missing stuff sucks though and should be fixed.
At this stage I've gone back to playing the original PC release of Halo Combat evolved with various community tools installed to restore all the graphical effects that were lost on all releases after the original xbox, as well as reintroducing the original spacial audio, all while still being able to have high FoV and high framerates. I respect the insane dedication of community efforts like those, and this video.
All of the halo anniversary cutscene bugs are literally brand new from the last update along with the AMD GPU memory leak, and the missing Seraph fighters, squads, dropships and anti air gunfire in reach long night of solace mission.
Clearly you havent made a game before. So many things can go wrong in the process even with the most professional and effiecient developers. Especially in a PC port. Also don't diss the MCC team. Throwing them in with the rest of the company is criminal.
@MCCP630Penaflor no I understand and appreciate the work, its just bad that the game has been doing well since 2019 bit by bit, and now in 2023, we somehow have brand new bugs, with the worst being the new memory leak in halo anniversary, clearly something went very wrong with this latest update. From December 7th 2022.
@@Spendingryan The amd leak is in my knowledge the fault of amd and not 343. 343s lack of response with the issue is annoying though especially as an amd user.
Not only for Halo 4 but for all games, the scene in Halo 2 where Arbiter gets teleported near Delta Halo’s control center in Uprising the yellow teleportation field is missing in MCC
To the people who are claiming that 343 is incompetent because of all these visual bugs, you have to keep in mind that all of the Games in the MCC were built off of the same engine. The only difference is come from the devs iterating on it with each game release. All these games have a bunch of spaghetti code so it's honestly amazing they even made it to PC in a fairly playable state to the point where a lot of the bugs are just visual.
they are not going to fix the game completely ever. I just drop the hope. Im glad i just have my x360 and all the games, except Reach, that one i will buy it originally soon.
Does halo 4 even have all the pre-MCC content yet? It took so many years to even get all the actual gameplay content like some armor mods from the DLC while other games got brand new content
i cant believe i never noticed 1SINGEL THING, i played halo 4 sooo much back in the day and that i dont see that is just mind blowing for me, ty for putting in the work
for that cube thing appearing.. i honestly do not know how they would fix that. for all i know, moving the cube could cause even more issues. or if they try to hide the cube with something, then it won't be like the 360 version. so that cube might have to stay there but idk
The cutscene interpolation issue has been there since Halo 4 launched on PC. I reported it for a long time before giving up because the Halo Support team love canceling more support tickets than they actually resolve. They're so dense. Literal quote: "We like to address issues that everyone's submitting tickets about." Me: "Are you kidding me?!" Your videos do a great job of spoon feeding the issues though, so hopefully it will get fixed finally if it hasn't already in the last update. Tore my hair out so much never seeing it get fixed in any update since 2020. I had to let it go among other things.
Perhaps my most hated of those things being related to Cross-Game Playlists. So many issues plague it down to the levels present in playlists. The "Welcome to the Jungle" cross-game playlist has incorrectly had the H2 Gravemind level in it since 2014. And it doesn't make any sense when the only thing remotely close to a jungle level in H2 is Delta Halo. Gravemind is a spaceship level. Shit will never be fixed. Even worse, Halo 3: ODST is featured in the cross-game slideshow despite no cross-game playlist having ever been updated to feature a Halo 3: ODST level as of 2023. In other words, it's a big misadvertisement. I will pay you $100 to make a video about all of the issues with cross-game playlists. I can still promise you though that none of it will ever be fixed. Lmao.
100% believe these will be patched, they did it with Halo CE and 2, they did some stuff for 3, I’m sure Reach and 4 will be touched up once they’re made aware
I thought I was misremembering. Halo 4 had breathtaking visuals at some times on the 360, and I thought it pales in comparison on MCC. Glad (but also sad) that I wasn't wrong.
Dang, this is so recent too I couldn't notice on account of my pc barely being able run Reach, nonetheless Halo 4, so you could assume the graphics are not very good.
4:44 I suspect this is a bitmap issue. At least in Halo CE, these meters are internally a simple gradient on a bitmap, where the meter will fill to the gradient. The defined brightness in MCC for 0% must be lower than the darkest colour in the MCC bitmaps.
I hope if they do fix bloom, they make it toggleable because on Halo Reach when they fixed the bloom, it makes everything to blurry which I rlly dislike.
i've been playing through the series with my friend the past couple months, we are about to finish ODST so Halo 4 would be next but I might want to wait until they fix some of this stuff... kinda crazy how bad it is
I know there was a big complaint about Halo 4 being oversaturated, but this is worse for sure, having lighting bloom disappear because of your FOV is stupid
Can you cover the Elite Mandibles in H2A Campaign being broken please? That and legs not scaling with FOV in Halo 3, ODST and Halo Reach. (Unlike 2 and 4.) I have not seen that covered anywhere else. Also do not know if it would interest you personally, but could you make similar stuff on Mass Effect Legendary Edition? Their legacy Xbox 360 versions have features that are missing in the Legendary Edition. That used to be an Xbox exclusive franchise, and similarly has not been preserved, but unlike MCC now gets no official support. Look up "SciFiIsMyJam" for more information. Like the final fight in Mass Effect 2 missing assets. Broken lighting, broken features such as melee combos in ME3 and Renegade Eyes for custom Femsheps in ME3.
i do hope that if the bloom gets fixed/increased for parity, they give a toggle for it (same with reach) i way prefer how the games look without it, especially reach
Halo 4 looks amazing on a 360 console, but on Xbox One it looked much worse than 3 and Reach. I figured it's mostly due to hwo the textures doesn't scale as well to higher resolutions, but this stuff definitely has an impact. Even when I went back to play Halo 4 before the server sunset, it still looked great on 360.
a big bug of Halo CE on pc, when u are watching the terminals, they cut before finishing the cinematic and u are back in the game, but the audio keeps playing in the background, can u recheck Halo ce after the next big update?
Are you planning on doing a similar video for any gameplay issues still in the games? A big one I have found is in Chapter 3 of the sixth Spartan Ops chapter where it doesn't allow you to complete the first section in stealth. I only know that is a bug thanks to how there was a video 343i did previewing that section in stealth years ago when the second half of Spartan Ops was releasing
I played through H4 on pc recently and was somewhat taken aback by how bland everything looked and feeling gaslit bc I remember this game being genuinely beautiful to look at.
This comment needs to be higher to be honest. You can't help but mess up while working with spaghetti code. The fact they even ported the game with such minimal problems is an achievement in it itself.
@@REALMARCHINADER Man you wouldn't know from Active camo using a fade in effect in Halo CE, to missing foliage in Halo 2, to missing water effects in Halo 3, Reach, 4, 5 and I think Infinite this engine has not liked Nvidia.
