PS3 Does anyone have an example of the file PS3SETTINGS.SFT

DeViL303

Developer
PSX-Place Supporter
Does anyone have an example of the file PS3SETTINGS.SFT, or know anything about it?

I know the PS3 searches for this on every boot by watching the socat debug output. Only on DEX FW.

Code:
open_path /dev_flash/vsh/resource/custom_render_plugin.rco
open_path /dev_flash/vsh/module/custom_render_plugin.sprx
open_path /dev_hdd0/game_debug/settings/PS3SETTINGS.SFT

I know examples exist as I saw one referenced in a file list for a copy of a Call of Duty game on a google search once, black ops I think. I can not find this reference now though.

This would be a debug file, Maybe some here has found one of these on a DEX console they received with some files on it? Or maybe it got packed into some retail game disc by mistake.


Any information would be great. I am just interested to know what it does and how it works as there seems to be no info about it online. I suspect it could be important as its one of the very first things referenced in DEX vsh.self.

Thanks.
 
I noticed this file before on one of my systems. I believe it's debug settings themselves stored as that file if you were to use the ProDG Target Manager.
 
I noticed this file before on one of my systems. I believe it's debug settings themselves stored as that file if you were to use the ProDG Target Manager.
If you can find an example that would be great.

I see Arcade FW also looks for lots of SFT files, different names though.
Code:
%s/PS3/UPDATE/PS3SETRG.SFT
/dev_hdd0/game/SCEEXE000/ARCDIR/PS3SETRG.SFT
/dev_hdd0/game/SCEEXE000/ARCDIR/PS3RTC.SFT

/dev_hdd0/game/SCEEXE000/ARCDIR/PS3PROFILE.SFT

/dev_hdd0/game/SCEEXE000/ARCDIR/PS3SETRG.SFT
/dev_hdd0/game/SCEEXE000/ARCDIR/PS3SETRG.SFT.bak

I found it strange there are no references on google.
 
Nice one, thanks. Its kind of what I thought. A plain text version of xregistry, kind of.
No problem, glad to help out. :-p Tbf i always wondered what it was myself, because everytime you set something from ProDG, it sends it over to the ps3's hdd after you've set the settings. Originally its stored in your appdata folder before ProDG sends it over to the system.
 
I notice its very similar to the DebugSetting_20210108_023649.txt that the checker plugin dumps. Almost the same. I find it strange its not referenced anywhere like on the wiki etc.
 
So turns out if I take the DebugSettingsxxxxxx.txt that the checker plugin dumps, I can rename that to PS3SETTINGS.SFT and use it to update the xregistry at boot time. Quite interesting. This could be useful maybe.

So far I have only succeeded in changing the system nickname, and changing the behavior for the circle button from cancel to enter, and changing the network settings to manual IP. The file gets deleted when its loaded, but the settings stick after a reboot so it must be transferring them to the xregistry, I think

This could be a new way for webMAN Mod to update the xregistry.sys for example, just write the setting to PS3SETTINGS.SFT and reboot. More testing needed. Some settings changes are causing a blackscreen.
 
I can also toggle the internet connection in network settings using PS3SETTINGS.SFT. I will keep updating this post with more settings as I find working ones.

Confirmed Working:

Internet disabled
Code:
[Network]
enable=0

Internet enabled
Code:
[Network]
enable=1


Set circle button behaviour to cancel
Code:
[System]
buttonAssign=0

Set circle button behaviour to enter
Code:
[System]
buttonAssign=1


Set PS3 System name
Code:
[System]
nickname=xxxxxx/code]
 
Last edited:
Im checking some of the settings listed in wiki (not complete) https://www.psdevwiki.com/ps3/XRegistry.sys
And im realizing all the names in the PS3SETTINGS.SFT sample file uploaded by @dazzaXx appears in the list... literally with the exact same names (but in lowercase)
https://www.psdevwiki.com/ps3/XRegistry.sys

The other settings that appears in the PS3SETTINGS.SFT but doesnt appears in wiki... is because the list in wiki is not complete, there are hundreds more settings that nobody found
Are the kind of settings that are only added to xregistry.sys "under requirement", as example the PS3 have identifyers for some sony walkman models (it seems sony was doing some digital versions of the walkman before it died and they decided to add support to it in the PS3, and even a icon, lol)... probaly the xregistry.sys can store settings specific for it

This same rule applyes to all of the other settings... only exists if at some point the firmware got a "request" to create the setting, like the settings for debug (is not posible to create them by official means in the xregistry.sys of a retail PS3 model)
With all this i mean... it seems PS3SETTINGS.SFT could allow to add a lot of settings to the xregistry.sys
 
Last edited:
Ohhh, and a very important detail.... inside the xRegistry.sys internal structure there is still an "unknown" value (used by every setting) that seems to be some kind of "hash" (of the setting string itself and maybe his value both together ?) or "index" (related with the hierarchy of the internal structure)

We (the PS3 scene) never gave a flying f#%" about that unknown because is posible to modify the setting without "updating" the unknown... and the PS3 seems to load the modifyed setting correctly
But in theory that procedure is wrong, we are modifying something that is unknown and that could not make any good :D
The only way to be 100% sure we are not doing anything weird is by identifying that unknown

-------------
Well... the file PS3SETTINGS.SFT could help in that matter, because it allows to update a single setting (used as a guinea pig) multiple times (or adding new settings) and see what the firmware does with the unknown
You know, if is a hash is needed to get a bunch of samples of it to try to deduce how the hashing algorithm works
 

Similar threads

Back
Top