PS3 PKGi PS3 development

I was trying to fix this last week just for fun but it gave me some other errors that I couldn't fix, I'll try now and see, thanks!

just check out the master branch and try to build it. (btw, don't forget to update/checkout the latest libs ya2d and dbglogger from my repos too)

let me know your results :)
 
just check out the master branch and try to build it. (btw, don't forget to update/checkout the latest libs ya2d and dbglogger from my repos too)

let me know your results :)
That must be the issue, I was using the old libs. I'll try this afternoon and report back. :)
 
Compiles flawlessly!
A little later than 'this afternoon' but better late than never haha

[*] SELF built.
[*] Data compressed.
[*] Data encrypted.
[*] c:/Users/Nacho/Documents/GitHub/pkgi-ps3/build/pkg/USRDIR/EBOOT.BIN written.
 
Since I was playing around with .raps and .rifs on Apollo, I thought I could improve pkgi a bit... :)
So, I've implemented .rif creation directly within PKGi (as long as your PS3 is activated and has a "act.dat" file available in any of the user accounts)

Also, a bonus speed improvement: as I added the truncate() syscalls to psl1ght, now the background download queue creation is almost instant, even with big .pkgs (GBs pkg? takes just a sec to create the dummy pkg placeholder)

I just need to clean up a bit the code, then I can release a new version. ;)
 
Since I was playing around with .raps and .rifs on Apollo, I thought I could improve pkgi a bit... :)
So, I've implemented .rif creation directly within PKGi (as long as your PS3 is activated and has a "act.dat" file available in any of the user accounts)

Also, a bonus speed improvement: as I added the truncate() syscalls to psl1ght, now the background download queue creation is almost instant, even with big .pkgs (GBs pkg? takes just a sec to create the dummy pkg placeholder)

I just need to clean up a bit the code, then I can release a new version. ;)

As you're working with .rif creation, I have a question (suggestion):
Does it create rif files in batch like reActPSN does?

PS3HEN/Cobra/Mamba can create the RIF automatically if the RAP is found in /exdata folder.
But only for game being launched.
 
As you're working with .rif creation, I have a question (suggestion):
Does it create rif files in batch like reActPSN does?

I integrated the .rif generation in the download workflow. When you select an item in your list to download, if the item has RAP information, then pkgi generates a .rap in /dev_hdd0/exdata/ . If the PS3 has been activated and the app detects an "act.dat" file, then it also generates a .rif file in /dev_hdd0/home/0000xxx/exdata/ . Then the regular download flows continues as usual.

(It's not doing a batch job to generate .rifs from a folder with .raps) << I guess that could be a "mass import" feature for Apollo

PS3HEN/Cobra/Mamba can create the RIF automatically if the RAP is found in /exdata folder.
But only for game being launched.

For HEN users, there won't be any difference as they already have the same functionality.
I guess it might be useful for CFW users, as I understand that some older Cobra payloads didn't had the feature so in that case pkgi will simplify it.
 
For HEN users, there won't be any difference as they already have the same functionality.
I guess it might be useful for CFW users, as I understand that some older Cobra payloads didn't had the feature so in that case pkgi will simplify it.

Yes, it might be useful for CFW users using Cobra 8.1 or older. But many have updated to Cobra 8.2.

IMHO the mass import would add much more value to HEN users, since CFW users already can use reActPSN or use Cobra 8.2/Mamba 8.3 that already have that function.
 
Some time ago I was looking at the psdev wiki and I found this:
https://www.psdevwiki.com/ps3/Keys#TMDB_Key

and it was itching in my mind for a while, as I wanted to implement it in one of my homebrews... so I did a quick coding session this morning, and added it to PKGi. :D

Now, for example, when you select "Details" on an item, the app will take the content_ID, generate the sha1 hmac and will try to download the ICON0.PNG directly from the TMDB. It will then show it on the "details" dialog window.

Also, when you download an item, if the icon is available it will be used for the package bubble, instead of the generic "PKGi" icon.

btw, since I was coding a bit, I added the XMB callbacks so now you can close PKGI properly using the PS button and selecting "quit" from the XMB.

I'll try to clean up the code so I can release a new version soon

PS: I was also thinking about official content updates... perhaps PKGi could query the official database, get the update XML file for the Title_ID and also queue the .pkg updates. :)
It will be an improvement even over the original XMB updates, because in this case they could be queued for background download, instead of blocking your PS3 until the download+update completes.
(of course, the updates would be queued in order (e.g. v1.01 , v1.05, v1.12), but the user must be wise and install them in order, or the content will become corrupt.)
 
PKGi PS3.png
 
perhaps PKGi could query the official database, get the update XML file for the Title_ID and also queue the .pkg updates.
that would be a great feature specially on large update. though this thing maybe problematic if the update needs to be installed on incremental order. but whatever, just add the feature, its better to have this since this will let us download the updates while I play other casual games, rather than letting PS3 sit doing nothing while it downloads.
 
PS: I was also thinking about official content updates... perhaps PKGi could query the official database, get the update XML file for the Title_ID and also queue the .pkg updates. :)
It will be an improvement even over the original XMB updates, because in this case they could be queued for background download, instead of blocking your PS3 until the download+update completes.
(of course, the updates would be queued in order (e.g. v1.01 , v1.05, v1.12), but the user must be wise and install them in order, or the content will become corrupt.)
Not sure if this would be possible or worth considering, but for archiving game updates I like to combine them into one package, This is easy enough. I just extract each update and then paste into the same folder overwriting existing files, then repack into a new package. This makes installing them much quicker and reduces the file size as it gets rid of duplicated files.

Off topic: I also add the combined update into the games ISO in a "packages" folder so its easily accessible in future.
 
hello, I have a problem with downloading the game from your program, when I was downloading the game, the game console turned on due to the standby mode (I did not look), the sample file apparently was not downloaded to the end, but mmCM cannot find it, it simply is not in any from the folders of the system but at the same time it takes about 8 gigabytes of my memory, where can I find it?
 
hello, I have a problem with downloading the game from your program, when I was downloading the game, the game console turned on due to the standby mode (I did not look), the sample file apparently was not downloaded to the end, but mmCM cannot find it, it simply is not in any from the folders of the system but at the same time it takes about 8 gigabytes of my memory, where can I find it?

Check these folders:

/dev_hdd0/tmp/pkgi/
/dev_hdd0/vsh/task/
/dev_hdd0/vsh/game_pkg/
 
that would be a great feature specially on large update. though this thing maybe problematic if the update needs to be installed on incremental order. but whatever, just add the feature, its better to have this since this will let us download the updates while I play other casual games, rather than letting PS3 sit doing nothing while it downloads.

the .xml download is trivial (https support is already available in PKGi), I just need to add the XML parser to "grab" the .pkg update links and then queue them for background download. My only real question is where should I put such option... I'm thinking that it could be on the "Details" window... if you request details for an item, PKGI will also check for the update XML and ask if you want to queue those .pkg files.

Not sure if this would be possible or worth considering, but for archiving game updates I like to combine them into one package, This is easy enough. I just extract each update and then paste into the same folder overwriting existing files, then repack into a new package. This makes installing them much quicker and reduces the file size as it gets rid of duplicated files.

Off topic: I also add the combined update into the games ISO in a "packages" folder so its easily accessible in future.

this is practical, but I think it makes more sense to be done in a computer. The network speed, disk space and processing power on a regular PC will give a much better performance for this task than the ps3.
And I think that in a PC this could be done with a batch file, because unpacking/ packing tools are already available.
 
Last edited:
@aldostools , here's an EBOOT.BIN with the "save to /packages" hack... basically if you're using direct download, the file will be saved to dev_hdd0/packages instead of creating the bubble

Since I'm probably not going to release a new version of pkgi for a while, I thought you could just try this build and use it in case you need
cheers
 

Attachments

Back
Top