You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found out that if you set MasterVersion and AppVersion ZBsp to 1.02 and then want to create an FPKG with Orbis-Pub-gen.exe,
there is an error when checking the param.sfo.
But if you only set the MasterVersion to ZBsp 1.02 and the AppVersion to 1.00 and start the build process, the build process will be implemented normally, if you edit the param.sfo after starting the build process and set the AppVersion to ZBsp 1.02, The build process continues normally and after completion Orbis-pub-chk.exe shows in the details MasterVersion 1.02 and AppVersion 1.02
the same applies after the installation on the PS4 the version number is displayed accordingly 1.02!!!
Now the question is, can you switch off this verification process in order to make it easier to merge Game pkg and Patch pkg in the future so that it works?
I've googled enough and haven't found a real solution for this and mine is the first one that allows this.
Game pkg and Patch pkg merge to one FPKG with correctly displayed version number after FPKG installation on PS4, so cheats are working correctly!!!!
that does It takes additional effort to merge the game and patch pkg, but it also saves storage space per game, and the advantage is that we have everything in one FPKG. you can watch the process here
I have built well over 40 thousand pkgs and ive never seen any issues with param, make sure you have named the folders correctly in the gp4, param will always have to be checked when building the pkg
when you would SET in the param.sfo the MasterVersion example 02.03 and the ApplicationVersion example 02.03 and you would Build with Orbis-pub-gen it shows an Error with the param.sfo!!! so booth Versions can not be the same , thats why iam set ApplicationVersion example 02.03 and the MasterVersion 01.00 and then i start the Building Process of the PKG so param.sfo check is Succsessfull and after the First Seconds wile it Builds iam change MasterVersion example 02.03 so the param.sfo includes now booth Versions 02.03 and at the Building Process where writing the PKG File after 50% it Takes this param.sfo and the Result is a Merged Game and Patch FPKG that shows with Orbis-pub-chk shown in FPKG Informations MasterVersion 02.03 and ApplicationVersion 02.03, so on PS4 Setup it shows too 02.03!!! And i have Ask if you can modify the Orbis-pub-gen param.sfo check so that it accept booth Versions Set example 02.03 and give no Error output and Cancel the Build Process!!!!
Hi,
I found out that if you set MasterVersion and AppVersion ZBsp to 1.02 and then want to create an FPKG with Orbis-Pub-gen.exe,
there is an error when checking the param.sfo.
But if you only set the MasterVersion to ZBsp 1.02 and the AppVersion to 1.00 and start the build process, the build process will be implemented normally, if you edit the param.sfo after starting the build process and set the AppVersion to ZBsp 1.02, The build process continues normally and after completion Orbis-pub-chk.exe shows in the details MasterVersion 1.02 and AppVersion 1.02
the same applies after the installation on the PS4 the version number is displayed accordingly 1.02!!!
Now the question is, can you switch off this verification process in order to make it easier to merge Game pkg and Patch pkg in the future so that it works?
I've googled enough and haven't found a real solution for this and mine is the first one that allows this.
Game pkg and Patch pkg merge to one FPKG with correctly displayed version number after FPKG installation on PS4, so cheats are working correctly!!!!
that does It takes additional effort to merge the game and patch pkg, but it also saves storage space per game, and the advantage is that we have everything in one FPKG. you can watch the process here
([https://www.youtube.com/watch?v=yn5NOfwzaOo&ab_channel=steven])
MFG
Steven aKa System23
The text was updated successfully, but these errors were encountered: