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!
> 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.
Holy crap we’re still dealing with this. I’m right there with you here. Most of the xbox consoles I have bought, I’ve bought to play halo on. I upgraded from One S to One X to get these campaigns in higher quality, and the only reason I bought any of the MCC was obviously to play the campaigns in high quality, they’re clearly where visual fidelity is most important (when compared to MP.) I’m incredibly annoyed with this, if I bought a blu-ray and it got “updated” and suddenly looked worse, I’d get my money back.
So I have a question to some folks on here that experienced the MCC before 2018 only on Xbox One back then, way before Reach got added to the collection. Did MCC on Xbox One at the time have Dynamic Resolution Scaling to keep the FPS locked at 60 FPS even on Anniversary Graphics for CEA and 2A by chance, similar to how Halo 5 functions with its Dynamic Resolution Scaling? If so, I wonder when 343 added Reach to MCC, I wonder if they removed this Dynamic Resolution Scaling to keep the FPS locked to 60 FPS at the time, even when changing between the graphic settings and it fluctuates the resolution depending on the place your in?
