HCEA +H2A campaigns performance downgrade.(XB1X)

Ever since Reach was added to the MCC, the performance of Halo and Halo 2 campaigns when using remastered visuals have taken a turn for the worse.

With the exception of the beginning of the Guilty spark level in the first Halo, the anniversary remasters were near locked 60, but now both games are dropping noticeably below that target, causing distracting stuttering and ugly screen tearing that wasn't present previously. It's not a very satisfying way to experience these games. This is on an XB1X, so i assume it may be even worse on the base model.

I was hoping todays patch would address this issue, but i just tested and framedrops and tearing are still present.

It's not a complete disaster, as performance is perfect when using original graphics, and Halo 3 and 4 are unaffected, but it's still very disappointing that framerates have seen such a downgrade.

Any hope that this will be addressed in the near future?
Many thanks.

I was actually wondering if the new update did anything with that issue.

Any official commentaries yet?

This is really disappointing,it seems that they stopped caring for Campaigns long time ago.All i see in new updates is Multiplayer improvements.So many people are reporting Campaign issues for months,even years but nothing is done about it.

Yep this is the only reason I haven’t been playing mcc half baked is never going be acceptable

Someone from 343 on Reddit finally replied to this issue. They appeared completely oblivious to it. Said to send in a support request to their support site. So I did that.

E Mc Sq wrote:

SoldierGryphon wrote:

Someone from 343 on Reddit finally replied to this issue. They appeared completely oblivious to it. Said to send in a support request to their support site. So I did that.

So, i went to the support site to create a ticket, and one of the required fields is the current 'build number'.
Any clue what the current build number is?
Many thanks.

When making a ticket, it usually comes up automatically when you select MCC for Xbox. It did for me anyways. If not, in most games, it can usually be found in the start or main menu somewhere on the screen

SoldierGryphon wrote:

E Mc Sq wrote:

SoldierGryphon wrote:

Someone from 343 on Reddit finally replied to this issue. They appeared completely oblivious to it. Said to send in a support request to their support site. So I did that.

So, i went to the support site to create a ticket, and one of the required fields is the current 'build number'.
Any clue what the current build number is?
Many thanks.

When making a ticket, it usually comes up automatically when you select MCC for Xbox. It did for me anyways. If not, in most games, it can usually be found in the start or main menu somewhere on the screen

Thanks, didn't realise it auto filled the build number.
I did manage to find the version number on my xbox and weirdly enough it is different to the one that auto fills in the form (auto filled 1.2416 or something on the support form, 1.1305 on my xbox)
Anyway, issue has been reported, so hopefully we will get some movement on this issue.

E Mc Sq wrote:

SoldierGryphon wrote:

E Mc Sq wrote:

SoldierGryphon wrote:

Someone from 343 on Reddit finally replied to this issue. They appeared completely oblivious to it. Said to send in a support request to their support site. So I did that.

So, i went to the support site to create a ticket, and one of the required fields is the current 'build number'.
Any clue what the current build number is?
Many thanks.

When making a ticket, it usually comes up automatically when you select MCC for Xbox. It did for me anyways. If not, in most games, it can usually be found in the start or main menu somewhere on the screen

Thanks, didn't realise it auto filled the build number.
I did manage to find the version number on my xbox and weirdly enough it is different to the one that auto fills in the form (auto filled 1.2416 or something on the support form, 1.1305 on my xbox)
Anyway, issue has been reported, so hopefully we will get some movement on this issue.

Did it several times, 343 will close the ticket (sic!) with resolution "we have added this issue to our known list of problems". I thinks this is totally illegal and I don't know how make them send official statement. At the update logs they mostly talking about pc version, no one cares about. I think public should now about 343 incompetency, so no one will ever buy their product, knowing that it could be broken any time, and 343 will do nothing. Strange that this still didn't appear anywhere outside halo forums. Should we send public message to Phil, 343?

IIVUnlimiteDVII wrote:

E Mc Sq wrote:

SoldierGryphon wrote:

E Mc Sq wrote:

SoldierGryphon wrote:

Someone from 343 on Reddit finally replied to this issue. They appeared completely oblivious to it. Said to send in a support request to their support site. So I did that.

So, i went to the support site to create a ticket, and one of the required fields is the current 'build number'.
Any clue what the current build number is?
Many thanks.

When making a ticket, it usually comes up automatically when you select MCC for Xbox. It did for me anyways. If not, in most games, it can usually be found in the start or main menu somewhere on the screen

Thanks, didn't realise it auto filled the build number.
I did manage to find the version number on my xbox and weirdly enough it is different to the one that auto fills in the form (auto filled 1.2416 or something on the support form, 1.1305 on my xbox)
Anyway, issue has been reported, so hopefully we will get some movement on this issue.

Did it several times, 343 will close the ticket (sic!) with resolution "we have added this issue to our known list of problems". I thinks this is totally illegal and I don't know how make them send official statement. At the update logs they mostly talking about pc version, no one cares about. I think public should now about 343 incompetency, so no one will ever buy their product, knowing that it could be broken any time, and 343 will do nothing. Strange that this still didn't appear anywhere outside halo forums. Should we send public message to Phil, 343?

Popular and respected Youtube channel Digital Foundry are currently working on a video covering the PC version of Halo anniversary.
Their previous PC related videos usually include a comparison with the console version, so i'm hoping that Digital Foundry will show how bad the framerates currently are on XBOX.
That should help get a spotlight on this issue.