Talk:Halo: The Master Chief Collection

System requirements are listed as "20 GB (Windows Store: 24.93 GB) (Steam:23.97GB)" however just to download Halo: Reach on Xbox Game Pass I am required to download 135.4GBs so I do not know where these numbers are from.

Game Pass lists 152.35GBs as "approximate size" and I assume this is for all the games.

Steam is also listed as 43GBs, though 25GB for Reach, so I am not sure what should be put down, and I don't own the Steam version either.

Modifiable

• "?:\\Program Files\\ModifiableWindowsApps\\HaloMCC"
• "?:\\ModifiableWindowsApps\\HaloMCC"

Non-modifiable

• "?:\\Program Files\\WindowsApps\\Microsoft.Chelan_*.*.*.*_x64_8wekyb3d8bbwe\\"
• "?:\\Program Files\\WindowsApps\\Mutable\\Microsoft.Chelan_*.*.*.*_x64_8wekyb3d8bbwe\\"
• "?:\\WindowsApps\\Microsoft.Chelan_*.*.*.*_x64_8wekyb3d8bbwe\\"
• REG_SZ PackageRootFolder of "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\Repository\Packages\Microsoft.Chelan_*.*.*.*_x64_8wekyb3d8bbwe\\"

Note: The reported "Size" of a directory and its contents represents how much space the filesystem thinks they would take up. The "Size on Disk" measurement shows how much storage space they actually use. They can be different than expected due to filesystem Symbolic/Hard/Junction Links and NTFS compression.

I don't actually own the UWP release of MCC, so this is acquired knowledge from support threads. Corrections would be appreciated.

This might be an OS-related issues, but on Linux, adding the /Option1 to the command in the shortcut doesn't launch the game in the intended mode. - 2001:14BA:8438:3301:2207:6013:33CA:3EE 19:08, 14 June 2020 (UTC)

http://forums.bungie.org/halo/archive38.pl?read=1138638 https://media.discordapp.net/attachments/547440061478862850/661801633289863189/Screenshot_20191231-232115_Edge.jpg https://media.discordapp.net/attachments/547440061478862850/661801633289863190/Screenshot_20191231-232201_Edge.jpg https://media.discordapp.net/attachments/547440061478862850/661801634132656138/Screenshot_20191231-232223_Edge.jpg https://media.discordapp.net/attachments/547440061478862850/661801634132656139/Screenshot_20191231-232242_Edge.jpg https://media.discordapp.net/attachments/547440061478862850/661801634707406858/Screenshot_20191231-232301_Edge.jpg

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.

The chatter on the PCGW Discord have suggested that differences between the games might be large enough to necessitate having separate pages and tracking support separately.

Whether this will be the case or not is currently up in the air still, but we'll know more around the time when the next title in the collection gets released.

If enough differences exists to necessitate separation, I was planning to redirect the "Halo: The Master Chief Collection" page to e.g. "Series:Halo: The Master Chief Collection", where we'd then list individual pages for each game.

The name of the individual pages would probably become this (or something like it):

• Halo: Reach
• Halo: Combat Evolved Anniversary
• Halo 2: Anniversary
• Halo 3
• Halo 3: ODST
• Halo 4

They would basically be tracked in "Series:Halo: The Master Chief Collection" which itself would be a subseries of the current "Series:Halo" page we have (see e.g. "Series:Lego Batman" for an example).

Anyway, writing it here so it doesn't get lost on the Discord, and we'll see when we get closer to the release of the second title :)

Yeah, it may be a good idea certainly if essential mods and fixes are not unified per each title. There are also some issues surrounding the localisation of each title and accurately highlighting this per game.

With the uncertainty regarding 120+fps support, and a fixed max FOV for every title in the collection, I can see a worst case where we basically would need to add exceptions to certain features.

Only issue I could see with this is the fact that we would be copying a lot of features and images (settings, and controller layouts) across to each sub-article.

Hopefully it is not needed but it would be the best option to ensure that the collection remains easy to read and relevant to the game that the user is trying to fix.

I have made some test articles to document what this may look like if we go down this route. https://www.pcgamingwiki.com/wiki/Series:User:Weion/Sandbox/Games/HaloMCC/Series

I like this idea, as long as it doesn't get as messy as the Mega Drive games on Steam, which are all individual game pages with varying levels of completion, as well as a combined one for the actual emulator.

I don't think it will be as messy as there are only 6 games in the collection. The issue I see is linking back to the launcher (Halo MCC) page as we would need the Main "Halo" Series and the "Halo MCC" Series box within the articles so users could link back to the Launcher page easily.

Release of Halo Reach in Halo MCC for both PC and XBO confirmed for "December 3, 2019"

I have a feeling MCC is going to be released on the 15th again as it's an anniversary date plus it happens while X019 is going on.

Reach has a spot on Saturday: https://twitter.com/Xbox/status/1193906516429918208

Good find.

The newly "leaked" release date of December 3, 2019 is still up on the Microsoft Store page, so I added that one.

https://www.microsoft.com/en-us/p/halo-the-master-chief-collection/9ntm9hxnlszx?activetab=pivot:overviewtab

Another good find! (though this may still be subject to change)

Just confirmed on the X019 Stream to be 03/12/2019.

That's weird that they're holding out beyond both Black Friday and Cyber Monday, but hey...more games for the Christmas season is always nice.