Not showing payloads from "ps5_autoloader" directories #20

New issue

Closed

opened 2026-05-28 15:06:06 -05:00 by rocknard · 1 comment

rocknard commented

2026-05-28 15:06:06 -05:00

(Migrated from github.com)

Hello.

I was confused about why i placed the payloads on "ps5_autoloader or ps5_autoloader_PPSAXXXXX" and pldmgr was "searching" on the folder "pldmgr" instead to load/search them on autoloader folder (and forcing me to reinstall them on pldmgr). I was expecting the same behaviour as ps5 "ps5_lua_menu".

Since doing a backup of your system only the youtube app will survive (not pldmgr folder/app), i was expecting a ready to use youtube autoloader when using "download0/cache/splash_screen/" folder to load pldmgr and showing them, because if it load/generate the pldmgr folder, i won't have none payload to load and will have to install them using pc/android instead a ready to use on PS5 itself.

Was expecting from "pldmgr" to search from here (like ps5_lua_menu):

Root of a USB drive
Internal drive: /data/ps5_autoloader
/data/pldmgr
The YT's splash_screen folder: download0/cache/splash_screen/aHR0cHM6Ly93d3cueW91dHViZS5jb20vdHY=/ps5_autoloader

Thanks.

Hello. I was confused about why i placed the payloads on "ps5_autoloader or ps5_autoloader_PPSAXXXXX" and pldmgr was "searching" on the folder "pldmgr" instead to load/search them on autoloader folder (and forcing me to reinstall them on pldmgr). I was expecting the same behaviour as ps5 "ps5_lua_menu". Since doing a backup of your system only the youtube app will survive (not pldmgr folder/app), i was expecting a ready to use youtube autoloader when using "download0/cache/splash_screen/" folder to load pldmgr and showing them, because if it load/generate the pldmgr folder, i won't have none payload to load and will have to install them using pc/android instead a ready to use on PS5 itself. Was expecting from "pldmgr" to search from here (like ps5_lua_menu): 1. Root of a USB drive 2. Internal drive: /data/ps5_autoloader 4. /data/pldmgr 5. The YT's splash_screen folder: download0/cache/splash_screen/aHR0cHM6Ly93d3cueW91dHViZS5jb20vdHY=/ps5_autoloader Thanks.

najdek commented

2026-06-01 07:37:04 -05:00

(Migrated from github.com)

Hello!

This project is designed to work separately from autoloaders. Since this project's ELF is very often used in autoloaders, using the same folders could cause conflicts.

Additionally:

Directory & Metadata Structure: pldmgr does not use a flat folder layout like autoloaders. It dynamically groups payloads by creating subdirectories (by stripping versions/suffixes) and generates metadata .json files alongside each payload (containing installation source, version, and checksum info).
Payload Updates & Configs: pldmgr handles updating payloads to newer versions. Since there are different autoloader forks in the wild (not all of which are maintained by me), having pldmgr modify the autoloader's configuration file to update filenames/paths could easily break those setups.

That is why the directories and configs are kept completely separate.

Hello! This project is designed to work separately from autoloaders. Since this project's ELF is very often used in autoloaders, using the same folders could cause conflicts. Additionally: - Directory & Metadata Structure: pldmgr does not use a flat folder layout like autoloaders. It dynamically groups payloads by creating subdirectories (by stripping versions/suffixes) and generates metadata .json files alongside each payload (containing installation source, version, and checksum info). - Payload Updates & Configs: pldmgr handles updating payloads to newer versions. Since there are different autoloader forks in the wild (not all of which are maintained by me), having pldmgr modify the autoloader's configuration file to update filenames/paths could easily break those setups. That is why the directories and configs are kept completely separate.