just upgrade it straight to 9.00 it's a lot stable than 6.72 version IMOI received my ps4 pro in 6.00 I went to 6.72 with the installation of the testKit on it![]()
I prefer to stay in 6.72 I have no KP in 6.72just upgrade it straight to 9.00 it's a lot stable than 6.72 version IMO
you just not yet experienced kp, my pro was 6.72 before i decided to upgrade it straight to 9.00, got a kp in a middle of game sometimes when running exploitI received my ps4 pro in 6.00 I went to 6.72 with the installation of the testKit on it![]()
I know but I stay with my, 6.72 on my ps4 pro sorryyou just not yet experienced kp, my pro was 6.72 before i decided to upgrade it straight to 9.00, got a kp in a middle of game sometimes when running exploit
6.72 without kp is a myth, trust me 9.00 is a lot stable you just need a usb to act as a dongle, even if you're still using harddisk you can run the exploit right from the time you boot the ps4
np your console your rule i just suggestingI know but I stay with my, 6.72 on my ps4 pro sorry
Hey bud... question for ya. You seem to be up on the ps4 scene. We've chatted before over on psx-place a few times...iirc, there's also an icon0.dds file, but it's made by the png version of the file, so if you build a package, you're not supposed to include it as orbis will create it for you. I don't know where that's used, but the avatar folder consists of both png and dds files from what I remember. each with different dimensions, so they're each used in different places on the home menu.
Thanks bud... Yea the dump itself included both the DDS version and the PNG version... I am using a GP4 file as well made from using the orbis toolset.no, you don't want to remove the icon0.png. there's a second file called the icon0.dds that you'd remove, because I think it's created from the png. the gp4 should not record it, but if you're making a pkg without the gp4, you don't want to add any of the .dds files. leaving the .dds files in will error with orbis.
Yea I ended up figuring it out. Essentially user error on my part. The drive I was trying to process these from was only 250 GB. Just a small SSD I used to dump the game. I was thinking since I set my temp folders to larger drives on my pc it wouldn't be problem, but I was wrong. I moved the dumps directly to the internal drive and it processed without a hitch. I appreciate the advice though man.if they're in there, make sure your user name on your pc doesn't have a space in it or there are no spaces in the path. I know this is an issue with the ps2 package creator for the ps4. I think the file that creates the sce_sys folder aside from the keystone is the sc.exe, because it's part of the sc part of the package, which is something that can be removed without a passcode. that's why an official package -- its information can be read even without knowing the passcode. image0 requires the passcode though. it will separate both of them when building the package as not to confuse people, it just lists image0 as the entire package. however, if you try to extract it with pub-chk, it will be separated. sc0 is just sce_sys minus the keystone and possibly the right.sprx, which is the copyright file that appears when you go into I think information or something on the home menu. that is also created by orbis, so it's not needed.
iirc, you don't have to remarry dlc. there's not even a place to put the base package information like a patch in orbis anyway.Yea I ended up figuring it out. Essentially user error on my part. The drive I was trying to process these from was only 250 GB. Just a small SSD I used to dump the game. I was thinking since I set my temp folders to larger drives on my pc it wouldn't be problem, but I was wrong. I moved the dumps directly to the internal drive and it processed without a hitch. I appreciate the advice though man.
On another note, you don't by chance have a good suggestion for re-marrying DLC to a game base that came from a different source than the DLC, do you? I was poking around looking at a few different homebrew apps for this sort of thing, but wasn't quite sure the best route to go... Same title ID's, just different sources