This question was created in reference to: [Solution for large Steam patch sizes when pak compression is [Content removed]
In the above question, Per Larsson of Epic Games wrote:
I’ve created Jira to update the docs and to expose the compression block size in a better way.
We’d like to set our patchpaddingalign to be optimal for distribution through Steam, but it seems from reading the code of UE5.4 that the above Jira wasn’t completed for this, so it looks like the only ways to set the compression block alignment whilst building with UAT BuildCookRun is to either:
- Make an engine mod as per the suggestion in the thread
- Use the iostorepatchpaddingalign param
I’m not hugely fond of either of these options, as we don’t want to introduce engine mods that aren’t strictly necessary, and there’s a comment attached to the usage of iostorepatchpaddingalign that states:
// Temporary, this command-line allows us to explicitly override the value otherwise shared between pak building and iostore
Do you know when the plan to expose the compression block size might come to fruition, please? And do you know how temporary the iostorepatchpaddingalign parameter is and when it might get removed from under us? Do you have any other guidance for how best we can optimize our patch sizes that avoids the use of an engine mod or a temporary CLI arg?