What is the right way to patch a project?
Hi, I have read the releasing and patching documents. And I have created a release version(1.0) and a patching base on it. I would like to know how to create a second patching. Should I make a new release(2.0) and a new patching base on it? Move the patching 1 and patching 2 to the version 1.0 folder?
Did you follow all of the instructions within the documentation? It gives you a step by step guide on how to create your patch and also how to install the patch.
answered Jul 20 '16 at 05:54 PM
When you're creating your second patch, it would be built based off of your first patch so to speak. So you'd update the "Release version this is based on" accordingly, because the new patch would be based on the old patch but with additional updated included. For example: 1.0 to 1.1, and then to 1.2.
Once it's built, you should follow the installing a patch section of the documentation provided.
The patching process creates a pak file in [ProjectName]\Saved\StagedBuilds[PlatformName][ProjectName]\Content\Paks. This pak file is the patch that should be distributed to users. For example, on Windows, you would create an installer to copy that pak file into the user's [ProjectName]\Releases[VersionNumber][PlatformName] folder, next to the original content pak file.
The patch pak file will automatically be mounted when it is located on the device in any of the pak search directories set in FPakPlatformFile::GetPakFolders. To prioritize patches, the mounting system uses a _p at the end of the filename to determine that it gets priority over other pak files. It can be renamed, but you need to include the _p.pak at the end of the file name.
If you build two patches from the same release version, they are both complete patches, so while installing the second patch, you should also remove the first.
answered Jul 21 '16 at 06:26 PM
,Guys Sorry to resurrect this thread,
answered Oct 05 '17 at 10:50 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here