#SOUL SACRIFICE DELTA DLC LIST INSTALL#
#SOUL SACRIFICE DELTA DLC LIST UPDATE#

#SOUL SACRIFICE DELTA DLC LIST UPDATE#

UPDATE tbl_appinfo SET val='gdb' WHERE key='566916785' and titleid=new.titleid if it's a fluke, maybe, but I think it's the PARAM.SFO flag restriction causing the issue to which u can't fix unless u apply the correct dlc key and content id to the tbl_appinfo.Ĭode: CREATE TRIGGER CHANGE_CATEGORY_GPC AFTER INSERT ON tbl_appinfo I know I found the app version for content, and it has the same key for each content item, so I think fixing this problem is doable.Īs far as ur edit 2, I don't know if that will work. afaik, it should be the same key for each parameter. It can be difficult to understand the tbl_appinfo section since u need to know which key applies to which PARAM.SFO. even cartridge games r recorded in the app.db. iirc, the flag override key is the same for each content type, so it's just a matter of know what the content id is for dlc. I think what's happening is that the PARAM.SFO flag is still intact for the dlc causing the game not to boot.

#SOUL SACRIFICE DELTA DLC LIST INSTALL#

ur forcing an install since it's recorded by the app.db.Ĭlick to expand.I'm not sure how it looks since I don't have any dlc, but the app.db is like the metadata indexer for the ps3 in which it records PARAM.SFO information. it's also how the ps1 bubbles thing works. that's how the backup of the entire memory card works since its value is subject to an installed game. I'm afraid I don't know a lot about what values do what since the numeric is lengthy and there r potentially hundreds of them. I believe that's how the whitelist v2 works. it's like overriding the value of the metadata indexer on the ps3 which is what's recorded when installing something.

I hope that's helpful.Įdit: scratch that about buying content, because I just remembered u can transfer it to the computer, then back with cma to refresh the app.db.Įdit 2: btw, the numeric within whitelist 2 contains a value, known as a key in the app.db, that's meant to override the normal PARAM.SFO. then, u can transfer the backed up app.db back, just make sure u don't buy any dlc, games from psn or u'll have to rebuild the database for them to be found by the app.db which will eliminate whiltelist v2 or any other hacks done for the app.db. I'd suggest backing up the app.db, then removing the whitelist v2 coding, transferring the app.db back, and playing the game with whitelist v1. it may not be setup to do the same for cart dlc. from what I remember, the whitelist v2 lists a few of them to eliminate some of the PARAM.SFO flags. the problem may be with the PARAM.SFO since it uses id's to differentiate content (i.e. I wasn't aware that carts had this issue.

Soul sacrifice delta dlc list