> 2533274807612264;45:
> Guys I finally received an update from my support ticket issued all the way back in March this year and they said they are working on it right now but its taking a long time to solve I am assuming. I told them that the issues are still there and need addressing.
Well…An official public statement should be here…no one sees that except for the people submitting. It does not let the issue be heard.
And I am getting messages from someone on the MCC Xbox forum that i am being rude and sarcastic…I am only trying to get this finally fixed, and people like that never play the campaign, and probably only touched multiplayer… ridiculous.
Stupid question, but still no fix? Even 343 thinks that nobody plays campaign. Or they decided to kill collection for xbox users to give boost to PC? Because of 343, now people thinking that good halo games is like CoD (campaign is like tutorial, main benefit is in multiplayer). Shame, what a stupid thing. Glad I have all original games…
> 2535410255336874;44:
> Tired of confirming this starting December, 2019. Seems to be nobody playing campaign, which is a shame, because I never met such strategically rich campaign anywhere else. And this issue, I mean come one, it was smooth before Reach update!
I might be wrong on this one, but it looks like it. I have checked numerous service records over the past 2 years and it was rare for me to come across someone with above 1k of missions completed (or even 300-400 for that matter). There are people out there with negligible campaign stats while multiplayer stats are beyond the stars. They do nothing wrong, I am just saying, you know…
> 2535410255336874;47:
> Stupid question, but still no fix? Even 343 thinks that nobody plays campaign. Or they decided to kill collection for xbox users to give boost to PC? Because of 343, now people thinking that good halo games is like CoD (campaign is like tutorial, main benefit is in multiplayer). Shame, what a stupid thing. Glad I have all original games…
Completely agree. Just because campaigns do not hold the same “longevity” and attention as multiplayer would, it does not give any excuses for 343 to be such seemingly poor developers. Leave it be…dont bring new content if you are too lazy to address the problems within an acceptable time frame. Again, how are they so incompetent to actually have caused reduction in performance for their own game…on what was their MOST POWEFUL CONSOLE. unbelievable. Waiting for the next big forum to come up.
Does not matter if I have less than 300 missions played (I have had MCC for less than 2 years)…I spent hours appreciating the environments that each level has…Halo is really something special. I did not pay to get an update that downgrades it, and causes random hitching whenever I look through the open areas. I wish I never blindly downloaded that Reach patch…if this is what people would have to deal with…can only hope they treat Halo Infinite campaigns better than the MCC on Xbox One. Joe Staten needs to wake them up, and give the studio a proper backbone to work on…I am speechless.
> 2535472081072397;49:
> Does not matter if I have less than 300 missions played (I have had MCC for less than 2 years)…I spent hours appreciating the environments that each level has…Halo is really something special
So, we started playing at around the same time, early 2018 for me. But yeah, it doesn’t matter. I was highlighting the fact how little the campaigns seems to be played compared to multiplayer. I haven’t seen that many people complaining about fps either and what’s sad is that I have seen those who did were ridiculed by others on more than 1 occasion. I just don’t think they are grasping what’s the issue here.
> 2535454747525049;50:
> > 2535472081072397;49:
> > Does not matter if I have less than 300 missions played (I have had MCC for less than 2 years)…I spent hours appreciating the environments that each level has…Halo is really something special
>
> So, we started playing at around the same time, early 2018 for me. But yeah, it doesn’t matter. I was highlighting the fact how little the campaigns seems to be played compared to multiplayer. I haven’t seen that many people complaining about fps either and what’s sad is that I have seen those who did were ridiculed by others on more than 1 occasion. I just don’t think they are grasping what’s the issue here.
I don’t want to be rude…but honestly
I think some of them just settle for that low performance as something acceptable since all they care about is multiplayer and getting all their vehicle/weapon skins…which I do not understand at all.
> 2535472081072397;51:
> I don’t want to be rude…but honestly
> I think some of them just settle for that low performance as something acceptable since all they care about is multiplayer and getting all their vehicle/weapon skins…which I do not understand at all.
Yeah me neither, not that I have anything against it, it is just I am not that type.
Again, I think they are not grasping the issue. I am not even sure if it actually affects everyone, regardless, it needs fixing. 9 months is quite a long time.
Kind of depressing that this is still a problem… I played CE and 2 Anniversary on the One X with the 4K upgrades in Oct/Nov last year, prior to the Reach udate, and they were totally smooth 60fps with minor occasional hitches on 2. Since the Reach update both are just painful to play, and remain that way 11 months later…
Maybe if 343 have been working on upgrading MCC for Series X|S any fixes will be applied retrospectively, as surely the One X is better equipped GPU-wise for 4K than the Series S even if it doesn’t have CPU for 120fps. If not seems these games will forever be unplayable on One X :’(
> 2533274806267782;53:
> Kind of depressing that this is still a problem… I played CE and 2 Anniversary on the One X with the 4K upgrades in Oct/Nov last year, prior to the Reach udate, and they were totally smooth 60fps with minor occasional hitches on 2. Since the Reach update both are just painful to play, and remain that way 11 months later…
>
> Maybe if 343 have been working on upgrading MCC for Series X|S any fixes will be applied retrospectively, as surely the One X is better equipped GPU-wise for 4K than the Series S even if it doesn’t have CPU for 120fps. If not seems these games will forever be unplayable on One X :’(
Exactly. You are right on everything . This is ridiculous…
343i please stop closing all my tickets I keep creating about the abysmal framerate on Xbox One X. Like I myself and everyone else repeatedly have been reporting for almost a year the framerate took a nose dive when you added Reach to MCC. Reportedly in several of the games, but especially in H2A. Only thing you’ve done so far is keep asking me with every patch if it’s been resolved. Hoping it would automatically fix itself despite you never actually actively working on the issue. It’s not even under “known issues” which is laughable since an unstable framerate that used to be really good affects the gameplay an awful lot. How can you not take this more seriously? The biggest install base for Halo is hands down on Xbox One. I bought a One X specifically for the 4k 60fps enhancements that used to live up to it’s promise, but you’ve taken that away without any option at all for me to revert it to the good state it used to be in. I don’t care about multiplayer. I just want to play the campaign (you know the best part of Halo), but that’s not an option anymore. I’m done with Halo. It runs on a potato for a PC, but there’s no way I’m double dipping considering your lackluster support in this regard. You still won’t even acknowledge this…
I’ve said if before, but I wouldn’t be surprised at all if it’s because of you adding yet another engine to the mix when you released Reach for MCC. Correct me if I’m wrong, but why did you think it was a good idea to use UE4 for the menus? You had working menus before. I know you had trouble managing memory in conjunction with this addition. So I bet it’s down to a bandwidth limitation. It just doesn’t make any sense at all. You could have guessed that having a third engine running on top of the already two running engines (classic and anniversary) would have serious side effects.
So yeah - build 1.1955.0.0 and it’s still a complete mess performance wise.
Thanks for letting me know.
Well I want to buy a Series X mainly for MCC campaiigns but if it’s not going to be a superb experience then why bother?
The asterisks just aren’t good enough any longer.
> 2535467960393373;56:
> 343i please stop closing all my tickets I keep creating about the abysmal framerate on Xbox One X. Like I myself and everyone else repeatedly have been reporting for almost a year the framerate took a nose dive when you added Reach to MCC. Reportedly in several of the games, but especially in H2A. Only thing you’ve done so far is keep asking me with every patch if it’s been resolved. Hoping it would automatically fix itself despite you never actually actively working on the issue. It’s not even under “known issues” which is laughable since an unstable framerate that used to be really good affects the gameplay an awful lot. How can you not take this more seriously? The biggest install base for Halo is hands down on Xbox One. I bought a One X specifically for the 4k 60fps enhancements that used to live up to it’s promise, but you’ve taken that away without any option at all for me to revert it to the good state it used to be in. I don’t care about multiplayer. I just want to play the campaign (you know the best part of Halo), but that’s not an option anymore. I’m done with Halo. It runs on a potato for a PC, but there’s no way I’m double dipping considering your lackluster support in this regard. You still won’t even acknowledge this…
>
> I’ve said if before, but I wouldn’t be surprised at all if it’s because of you adding yet another engine to the mix when you released Reach for MCC. Correct me if I’m wrong, but why did you think it was a good idea to use UE4 for the menus? You had working menus before. I know you had trouble managing memory in conjunction with this addition. So I bet it’s down to a bandwidth limitation. It just doesn’t make any sense at all. You could have guessed that having a third engine running on top of the already two running engines (classic and anniversary) would have serious side effects.
>
> So yeah - build 1.1955.0.0 and it’s still a complete mess performance wise.
Yep, It is really disappointing because I love Halo 2’s gorgeous visuals and before reach on pc, before Halo 2 on pc, the game never went below ~45 frames on my Xbox One X. Now the frames go below 30 which is just bad to look at. I can’t even play Halo 2 on pc without the game giving me a UE4 error. If there is a fix for the UE4 I would gladly like to hear!
Ps. The fact that it is not in the known issues is depressing.
According to here Halo CE’s Anniversary graphics’ frame rates are known to drop even on Series X. So definitely seems like a programming issue that is flowing through any version of hardware.
Anyone have any data on how all 4 games campaigns run on Series X frame rate wise?
These incompetent fools seems to be thinking, that they have fixed the problem, since after reopening the ticket they asking for video recording to prove the issue. Nice job killing the series, 343!
