Topic on Talk:Halo: The Master Chief Collection

Certain UE4 INI Tweaks do impact the game such as the "GraphicsQualityThrottles[i]" array as well as UE4 variables such as "GameResolutionScale" in the GameUserSettings.ini. From the former it is safe to assume that all settings that use an array index call back to the Blam! Engine, but validity of the latter vars will need to be reviewed case by case.

Re: "UE4 ini tweaks only affect the Menu and Armour Customisation UI / UX. These have no effect on the in-game rendering which uses the Blam! engine"

Looks like there's a few custom settings in the UserGameSettings file that can, eg. the GameResolutionScale variable: normally it can only be set up to 1.00 via the in-game options, but setting it higher than 1 in the INI does seem to take effect in the actual game itself (though for me at least, trying this with 2.25 made the in-game UIs like the scoreboard etc act strange, no longer centering properly...)

It'd probably be safe to guess that the default UE4 variables probably won't have any effect on Blam (like that AudioQuality fix that's been shared around), but custom ones added by 343 might still be worth looking into.

(don't have a list of what a default UE4 UserGameSettings would look like to try seeing what they added though.. not even sure which UE4 version they based it on, 4.18 maybe?)

Upon reviewing a few posts on the topic it does seem that a few variables in the UE4 ini files do interoperate with the settings in Blam. LowSpecGamer has also made a video showcasing this as well.

Looks like Reach in particular uses "[5]" for its array index on the setting values, I'm assuming the index is listed in OG release order with "[0]" being the universal setting for all games.

There is a risk of a lot of placebos slipping through the cracks, so the best thing would be to ensure that config fixes and tweaks are referenced to ensure validity.