Originally Posted by sandungas
Yeah, this is the idea, the two important things that needs to be considered are APP_VER and PS3_SYSTEM_VER e.g with gran turismo would be something like this:
Code:
disc -----------> APP_VER = 01.00, PS3_SYSTEM_VER = 3.50
patch 01.01 ---> APP_VER = 01.01, PS3_SYSTEM_VER = 3.55 (200mb)
patch 01.02 ---> APP_VER = 01.01, PS3_SYSTEM_VER = 3.60 (400mb)
fix ------------> APP_VER = 01.02, PS3_SYSTEM_VER = 3.40 (5mb)
This is a correct way to do it, the problem is the APP_VER in the fix has increased and the real 01.02 patch cant be installed.... but later a 01.03 patch can be installed and ruin all (it depends if are cummulative)
In this example the better way to keep the "standard" is by making a patch with APP_VER 01.01 (so after installed... the patch version is the same)
Maybe this can be done b using TARGET_APP_VER but never tested myself
|
Indeed, that is how I am actually packing my fixes, I never change the APP_VER, I leave it as it was in the original update, I just change the Minimum FW Version (in PARAM.SFO).
I have Gran Turismo so I will make some tests and let you know
.
Thanks for the feedback and information.
SeeYa!
************* [ - Post Merged - ] *************
I believe the right approach if there was going to be a "Standard" made for update patches, is like you said
@
sandungas
, just put APP_VER - 09.99
So the user will never update unless a new patch is released, then he can manually update with the new patch fix safely.
I will re-patch all my released PKGs and re-upload them soon, maybe I will make a thread with them soon, so at least on my end I'm following the right approach
. We will just have to exhort other patch makers to do it the same way.
SeeYa!