[sandungas]

Originally Posted by raddog @sandungas can u change a games language through the sfo....like lets say the games plays with french audio....can it be change to english?

No, the PARAM.SFO can contain the game "TITLE" in different languages... (named as TITLE_00, TITLE_01, TITLE_02, etc...) but this texts are used only to be displayed in XMB
Each number is a language from this list: http://www.ps3devwiki.com/wiki/Conte...iles#Languages

When a game boots.... the language used is the one you have configured in XMB settings column (the system language for the whole PS3)
So if this game is booting in french is because your XMB is in french, change it to english and your games will boot in english

There are a few games that contains a language selector... but even this ones boots as explained before
And some games stores the audio languages in compressed files, e.g:
GLOBAL.STREAM <---- 2GB file... this are the in-game "shared" sounds not language related, like a river, the wind, etc...
DEFAULT.STREAM <--- 1GB file... only in-game english sounds
FRENCH.STREAM <--- 1GB file... only in-game french sounds
SPANISH.STREAM <--- 1GB file... only in-game spanish sounds
etc...

You can remove the "not used" ones (better replace them by a 0kb dummy file with the same name)... or you can rename them
In this example i used.... you can rename DEFAULT.STREAM to FRENCH.STREAM... this way you can keep your XMB in french... but the game will boot using the english files

Edit:
Ops, i forgot other problem... the .BIK (video files)... can contain several audio tracks, that are indexed with a number for each language
If you want to modify language files in a game... this audio tracks needs to be "reindexed" (with rad video tools)

A good question deserves a good answer

[Ada Love Lace]

About BV and WT category, i ll try a guess
BV being the new category instead of AV but i can t imagine why. or only AV needed holidays.
BV was probably already long time ago implemented and was waiting patiently for her turn.

WT is really new in the city, from 3.70, but can t really decide if it s for PSP remastered/PS VITA cross game, or o save data.

Both are HDD content.

May be if Andreus can have somes more clues since it was originally from xmb data base.

Edit
there are for sure an other way than using AV category on param.sfo, to have the apps going to TV col. That can be specific to the user account and probably end up into one of the file of the hdd0/home. But i m lost as this point, need more investigation.

[sandungas]

We need an explain of this category's... are in the wiki too much time ago listed as "unknown"
I personally always thought that are wrong (not disrecpectfull)... but i cant find a place in XMB for them (maybe with photos folders or musics folders, but i think there is no PARAM.SFO with this kind of files)
I think was found in one of the XMB .xml's (inside .rco's)... not inside the XMB database files where i find no reference to them

This last days i been talking with @andreus , next day i will ask him to read this thread to see if he can help to clarify this, i think he is registered in the forum


*The TV column contents are managed by different files (that i dont remember right now) where are listed the channels, paths to icons, url's, etc, etc... is like a "database" of video channels

[sandungas]

From this thread ---> http://www.ps3hax.net/showthread.php?t=41220
Testing XMB In-Game Background Music in old games...

Originally Posted by Ada Love Lace About the table for flags, at first i thought it was better to don t have 2 different tables about patches and one other from bootable. because in that case , the tables don t look complete when in fact it s almost done but need to know them more accurately: in bootable content flags n14-15-16 are empty when in fact they are already used in patches)-----but it s just visual problem

It was a good decission, but we was forced to move them out to his own table because there are a couple of flags that are the same (PCengine.... and... Overwrite Move Controller warning screen)... PS3 decides what the flag "means" because one is for a original game (disc or game.pkg)... and the other is for a patch

So all the other flags for patches works in the same way, and are all together (in the Third Byte of ATRIBUTE)
Patches CANT use the values of the Third Byte of ATTRIBUTE In Bootable content (this means... Install Disc, Install Packages, Game Purchase Enabled, PCEngine, License Text Hidden... CANT be used in patches)... this has sense

Btw... while i was writing this i realized the flag to activate Move Controller Compatible in games.... is the same one used in patches to Overwrite Move Controller Compatible... this has sense also... is one of the things that was "removed" from the table months ago because was very confusing

[Ada Love Lace]

Originally Posted by sandungas It was a good decission, but we was forced to move them out to his own table because there are a couple of flags that are the same (PCengine.... and... Overwrite Move Controller warning screen)... PS3 decides what the flag "means" because one is for a original game (disc or game.pkg)... and the other is for a patch

Yes, i understand now. Something i read fews weeks (what you can not overwrite but was not only about attribut but also others parameters but was lazy to test so didn t get it ) ago about patches now make sense thanks to you.

Originally Posted by sandungas So all the other flags for patches works in the same way, and are all together (in the Third Byte of ATRIBUTE) Patches CANT use the values of the Third Byte of ATTRIBUTE In Bootable content (this means... Install Disc, Install Packages, Game Purchase Enabled, PCEngine, License Text Hidden... CANT be used in patches)... this has sense Btw... while i was writing this i realized the flag to activate Move Controller Compatible in games.... is the same one used in patches to Overwrite Move Controller Compatible... this has sense also... is one of the things that was "removed" from the table months ago because was very confusing

The table i had in mind was to add one or two column for patches (so there are only one table for all the differents attribut) ---(i will not edit the wiki but may be try it on talk page or more probably send you on PM)

From what it look like, there are still somes attributs in patches to be discover...

when it will be more clear how parameters/attributs from different game category are working with update (cumulative or not)...the other playground will be the eboot param sys thing and the ps3 data base file.
( i will need couple of days but there are something i wanted to get, the specific title registered in the data base/ tool ( that i have example... the SFO eating automatically my attributs) and from how to activate and link to other category ( TV or Home) from the eboot (and in that case not yet registered)
Thanks you for this work (and i now how update can be annoying to test compare to classic DG/HG)

[sandungas]

Originally Posted by Ada Love Lace The table i had in mind was to add one or two column for patches (so there are only one table for all the differents attribut) ---(i will not edit the wiki but may be try it on talk page or more probably send you on PM)

Hmm, i think i understand you perfectly, i like the idea, but will make the table too width... and will be needed to move all the notes to the bottom
Casually today i imagined a way to make the table a bit smaller by moving the "required flag" inside "flag" column
Is a big change, lest wait a bit to see if there are ways to reduce the size without losing info

Originally Posted by Ada Love Lace From what it look like, there are still somes attributs in patches to be discover...

The rules of the game are the same
Are ordered chronologically, and we know the last ones was used, so the older ones was used too
Appart of the choronologicall order maybe are ordered by what value affects: parameters at top.... and ATTRIBUTES at bottom (remember the first games doesnt have ATTRIBUTE ?.... heheh... this was implemented later)
The last thing we know is the olders "uknowns" overwrites "simple" values that was present in the firmware lot of time ago (probably at the same time the patches was implemented).. this ones are simple parameters, maybe things like TITLE, PARENTAL_LEVEL, etc...


--------------------------------------
I hate to admit that what i wrote today about patches in the wiki is not accurate, there are things that are obvious right (e.g. there are values taken from the original sfo.... and other taken from the patch sfo)... but there is also a problem that makes all my explain invalid... and this sucks but is the only way for me to update the wiki, we will se later how to close the circle to give all a sense

The problem is the update for "heavy rain" patch v2.00... it adds support for the move controller (+ 3 warning screens)
Compare the flags with the tables --_> http://www.ps3devwiki.com/wiki/PARAM...UTE_in_Patches (the ATTRIBUTE is marked in yellow in the pictures and matches with the column "Little Endian" in wiki tables)

Original from disc (APP_VER = 01.00)


From the move patch (APP_VER = 02.00)


If the explain i wrote today is correct... to activate the Move Controller Compatible flag its needed to activate one of the "overwrite flags for patches": Overwrite ATTRIBUTE flag: Move Controller Compatible... no problem with this ones because is the same, there are no conflicts with other flags, maybe the ps3 is taken the value 2 times wich is correct

There are also 3 more flags activated for the "warning screens": Move Controller, Navigation Controller, Eye Cam (warning screens), but are not using one of the "overwrite flags for patches" so there is a problem here
Edit: is very difficult to explain with my english sorry... please go to the tables in wiki and compare the flags used in the "heavy rain move patch v02.00" with the other flags that are "supposed" to be used to "overwrite" the move features... and you will see that in this patch the "overwrite" flags are not used


I need to take a look to a good amount of patches to understand this with examples... but patches are one of the most time-consuming things left in the PARAM.SFO wiki page... and there are other things related with patches that i would like to add to the page, so for me understand "patches" is like a separated project for itself
With this i mean im not going to get crazy with patches now, but if i see somebody interested in it, making tests or updating the wiki i will keep helping, giving ideas, or writing notes in wiki pages

Edit: btw... the next thing i want to do is a huge clean up of both PARAM.SFO pages (front and talk)... i will "erase" all the obsolete content from talk page, then move all speculation from "front"... to... "talk" ordered by sections... and last i will update the main page with some eyecandy (some sections of the front page has not been updated in months)

[Ada Love Lace]

Originally Posted by sandungas Edit: btw... the next thing i want to do is a huge clean up of both PARAM.SFO pages (front and talk)... i will "erase" all the obsolete content from talk page, then move all speculation from "front"... to... "talk" ordered by sections... and last i will update the main page with some eyecandy (some sections of the front page has not been updated in months)

As usual, if you see any of "my" edits who need to be deleted/reversed...please do it (i was thinking the x category need to be reduced to minimal, i ll probably do today but before that need to give one other reason why one table can be also fine ...i ll try it and send you on PM with wiki format if i have time and still stick to this idea)

[sandungas]

Originally Posted by Ada Love Lace As usual, if you see any of "my" edits who need to be deleted/reversed...please do it (i was thinking the x category need to be reduced to minimal, i ll probably do today but before that need to give one other reason why one table can be also fine ...i ll try it and send you on PM with wiki format if i have time and still stick to this idea)

I dont want to erase things... i will only move things to the "talk" page, the size is not important

But for this is needed the "erase" all the old contents from the "talk" page... after this we can make a new "index" with separated sections to add whatever thing people consider are interesting "notes" that helps understand how things works (e.g: its needed a section for "patches"... and another for "X categories"... and another for "undocumented categories", and lot more, etc...)
In other words.... i would like to have an "index" in the talk page with separated sections for speculation and to add whatever notes or brainstorming we find eventually... most of the sections will be tiny but the point is to be able to see a list of all them in the "index" of "talk" page

-------------
With the "subsections" in ATTRIBUTE... and the decission of join together all them...

Actually are not in the correct order... i ordered this way to left an empty area at the bottom of the last one to use as our "speculation backyard laboratory" (all the texts after X categories explains)... but if we move this to the talk page, then the sections can be reordered this way:

4.5 ATTRIBUTE
    4.5.1 ATTRIBUTE In Bootable content
    4.5.2 ATTRIBUTE in Patches
    4.5.3 ATTRIBUTE in SaveData
    4.5.4 ATTRIBUTE in Discs Subfolders

I think is better ordered this way, is one of the things i want to change

[Ada Love Lace]

Originally Posted by sandungas I dont want to erase things... i will only move things to the "talk" page, the size is not important

I added recently the folder as CrossBuy (this is the new feature Sony announced for ps3 and ps vita), SHOPDIR etc.. but may be don t have to be there.

About attribute, (after thinking, it s much better to have them separate from category than my intial idea) the little thing is about X0 PCEngine. The flag N22, i call it X maker, and so X0 as flag N22 + byte N4 : 00. And X category can stand up as eXtra game ( but that is just from me).

I m looking about the "new" page for SF0, waiting a little more and i ll copy the way you did and add it for eboot.pbp ( and i wanted to make clear about one specific category on .pbp before also, otherwise it will be nothing new or really related to ps3 but for the wiki s harmony and history on SFO)
Hope you don t mind

[sandungas]

Originally Posted by Ada Love Lace I m looking about the "new" page for SF0, waiting a little more and i ll copy the way you did and add it for eboot.pbp ( and i wanted to make clear about one specific category on .pbp before also, otherwise it will be nothing new or really related to ps3 but for the wiki s harmony and history on SFO) Hope you don t mind

Of course you can copy this colors, tables, templates, etc in other pages
Actually i think all the pages that we where editing can be improbed a bit with eye candy
But wait a bit because im not 100% happy with the new templates i added yesterday (this blue icon templates i added in all sections... also i need another modification of this template for "code")

And is important you know there is a problem with the templates that are created by default when the wiki was "installed"... some of this templates are broken, i have no idea how to fix them and are several ones

By now we can make our owns manually by coping others:
Use this page for taking a look at all the templates to look for the interesting ones
http://www.ps3devwiki.com/wiki/Category:Templates
And use this page to make tests (and publish it if you build something interesting)
http://www.ps3devwiki.com/wiki/Wiki_Sandbox_Test

The problem.... is we cant make new complex templates replacing the broken ones (even if we can... is not good to do it)... this needs a good repairment and a cleanup/update of the template database in wiki
This things uses to break others when updated, i bet this is what happened time ago

Originally Posted by Ada Love Lace I added recently the folder as CrossBuy (this is the new feature Sony announced for ps3 and ps vita), SHOPDIR etc.. but may be don t have to be there.

Yesterday when reordering the page i noticed this "CROSSDIR" but i was not sure if you added it... interesting... i listed in the "talk" page with the other "unknown", i have no idea what is it

Originally Posted by Ada Love Lace About attribute, (after thinking, it s much better to have them separate from category than my intial idea) the little thing is about X0 PCEngine. The flag N22, i call it X maker, and so X0 as flag N22 + byte N4 : 00. And X category can stand up as eXtra game ( but that is just from me).

When reordering the ATTRIBUTE table i was all the time thinking in your idea of joining together all the flags for other tables (all the ATTRIBUTE flags for all contents together)... looking at the table now.... you can see the problem are the 2 columns at the right: (firmware-date) and (flag nº flag required)

flag nº flag required
The way we have assigned this numbers to the flags is completly wrong, i think there is no identification of them by this number neither in pc editors... neither in ps3 firmware
Also... this is not the chronologicall order when them was implemented

So in resume... this column in not accurate, but is very intuitive to use this numbers when talking about them
Also.... is the only way in the table i see to "relink" some flags to others (using this "flag x requires flag y" and the colors)

firmware-date
This info is needed to understand the order how the flags are cummulated in the table.... and is the chronologicall order

Note that this 2 columns are related ONLY with "flags in bootable content"
By removing this 2 columns we can join all the flags together (we need 3 more columns for "atribute in savedata", "atribute in discs", and "atribute in patches", but in my mind doesnt looks too pretty, im not sure but i will not forget the idea

---------------------------
About X0-X7... im sure we will understand some day without effort, we just need to wait for sony to use some of this "reserved" flags, hehhehe
By now looks very incomplete, but all the test we did (trying to find the other flags related with X0-X7) was epic fails, so there is not much to do with them by now

The day we understand how this works we can decide what to do with this flags (maybe a table appart for them or a section)