PS3 RCO Mage (Dumping RCO's)

[RandomDude]

Did you try to rebuild the rco with something like this ?

<Text name="msg_ps_rights">TEST</Text>

If the PS3 logo icon still appears in the same position it means the icon is displayed in his position by other means, or the whole text string is loaded from other rco

Another thing you could try is this, maybe this "overrides" it (here im replacing the spaces with TEST)

Sure, will report back asap.

 

[sandungas]

...or the whole text string is loaded from other rco

Try to search for it inside explore_plugin_full.rco

This rco is like the "trash bin" of XMB, it contains lot of stuff that is duplicated in other rco's

 

[kozarovv]

I got the same issue here. I never figured out what's wrong.

 

[ShaolinAssassin]

Try to search for it inside explore_plugin_full.rco

This rco is like the "trash bin" of XMB, it contains lot of stuff that is duplicated in other rco's

I already searched in that RCO, it isn't there.

 

[RandomDude]

Did you try to rebuild the rco with something like this ?

<Text name="msg_ps_rights">TEST</Text>

If the PS3 logo icon still appears in the same position it means the icon is displayed in his position by other means, or the whole text string is loaded from other rco

Another thing you could try is this, maybe this "overrides" it (here im replacing the spaces with TEST)

Tried this, It worked.
It shows Test playstation blah blah

Uploaded pic, sorry for the blur couldn't focus..

 

[ShaolinAssassin]

Black magic ? I'm out of ideas...

 

[RandomDude]

Black magic ? I'm out of ideas...

Idk what's up with sony and their developers

 

[sandungas]

So the trick about overriding the 0x2020202020 works ?, nice
I guess this means there is some code in a .sprx that is replacing the 0x2020202020 by 0xEFA297


Edit:
To verify this theory the rco can be rebuilt using the character code 0x2020202020 several times (and i mean... a lot) in that same text line

In other text lines (or in other screens) maybe is not applyed that replacement of 0x2020202020 by 0xEFA297

 

[RandomDude]

So the trick about overriding the 0x2020202020 works ?, nice

I guess this means there is some code in a .sprx that is replacing the 0x2020202020 by 0xEFA297

That makes sense actually..... But why do they need to do that instead of doing it in the sysconf_plugin.rco itself..

 

[RandomDude]

So the trick about overriding the 0x2020202020 works ?, nice
I guess this means there is some code in a .sprx that is replacing the 0x2020202020 by 0xEFA297


Edit:
To verify this theory the rco can be rebuilt using the character code 0x2020202020 several times (and i mean... a lot) in that same text line

In other text lines (or in other screens) maybe is not applyed that replacement of 0x2020202020 by 0xEFA297

Hmmm I didn't understand the last line you've just said but are you trying to say try replacing the rco with several 0x20202020 to check if it clones the ps3 logo several times?

 

[sandungas]

That makes sense actually..... But why do they need to do that instead of doing it in the sysconf_plugin.rco itself makes no sense...

Yeah, very weird

And what you mentioned about the correct codes existing in luanteles files adds another factor to the mistery
I guess luanteles files was taken from a different firmware version (not the latest 4.83), but it should not be much older
If this is true it means sony have made this change latelly (in 4.82 or 4.83)
Dunno, im just speculating a bit

 

[sandungas]

Hmmm I didn't understand the last line you've just said but are you trying to say try replacing the rco with several 0x20202020 to check if it clones the ps3 logo several times?

Yes, but imo doesnt matters, at this point im pretty sure is going to work

And it needs to be made modifying the xml in the hexeditor... or modify it in notepad++ (adding 5 spaces is easy), but at the end verify in hexeditor that the codes are right

 

[RandomDude]

Yes, but imo doesnt matters, at this point im pretty sure is going to work

And it needs to be made modifying the xml in the hexeditor... or modify it in notepad++ (adding 5 spaces is easy), but at the end verify in hexeditor that the codes are right

Tested this & guess what Ps3 crashed....
The xml edit i made is uploaded.

 

[sandungas]

Tested this & guess what Ps3 crashed....
The xml edit i made is uploaded.

Hmmm, maybe the code can do only 2 replacements ?
Never minds, you was trying to see how to replace that icons and i guess that doubt is solved, just remove the 5 spaces

It seems the code 0x2020202020 represents the same than 0xEFA297 ... at least for the first time where is used


--------------
Btw, im loking at 4.81 CEX and is using the code 0x2020202020 too
So if this was changed in latest firmwares it happened before 4.81

 

[RandomDude]

Hmmm, maybe the code can do only 2 replacements ?
Never minds, you was trying to see how to replace that icons and i guess that doubt is solved, just remove the 5 spaces

It seems the code 0x2020202020 represents the same than 0xEFA297 ... at least for the first time where is used


--------------
Btw, im loking at 4.81 CEX and is using the code 0x2020202020 too
So if this was changed in latest firmwares it happened before 4.81

Interesting... well Thanks a lot for taking a look into this.

 

[sandungas]

Btw, the fact that the PS3 crashed with that test i guess means is actually dealing with that spaces in a "weird" way (probably with some code doing the replacement i mentioned)

I mean... an space inside a text string "should" be treated like a normal character by XMB, you "should" be allowed to write spaces together and "should" not create any problem
But sony made this weird autoreplacement of spaces that is adding restrictions in the way you use them


Edit:
I guess this replacement of spaces only applyes to that string/s for "ps_rights"... or only to the screen where appears that texts

 

[Cypher_CG89]

Btw, the fact that the PS3 crashed with that test i guess means is actually dealing with that spaces in a "weird" way (probably with some code doing the replacement i mentioned)

I mean... an space inside a text string "should" be treated like a normal character by XMB, you "should" be allowed to write spaces together and "should" not create any problem
But sony made this weird autoreplacement of spaces that is adding restrictions in the way you use them


Edit:
I guess this replacement of spaces only applyes to that string/s for "ps_rights"... or only to the screen where appears that texts

This is displayed in the 'Settings', 'System Settings', 'About PlayStation3'.

 

[RandomDude]

This is displayed in the 'Settings', 'System Settings', 'About PlayStation3'.

How else are we supposed to get a peak of it?

 

[Cypher_CG89]

when you dump the rco you will get an xml that is outside the two dumped folders for this rco.

This xml controls everything to do with this RCO. Inside this will be the commands used in this part that your interested in 'About PlayStation3 System'. So when you select it on the xmb it tells the ps3 what to display, in what order, any icons needed an the text to go with it, where to get it all from, any timing and animation to go with it. Its a massive xml file and will take a while to find that part that pertains to this particular part your interested in.

'About PlayStation3 System is a combination of the this xml, the text xml in the text folder, and the images in the images folder, where all these Logos and trademark example are kept. And this also refers to any and all logos that are the property of SCEI, including any text that displays PlayStation on the system, abbreviated or not. There are also many other logos in various other RCO files like the PS3 logo, PlayStation3 logo (used in the old gameboot), S@ny Computer Entertainment Interactive (Only ever displayed once on brand new ps3s or when you have done a full system restore or when you boot the ps3 for the very first time). I have counted 6 RCOs so far with some kind of logo or trademark in them and some are repeated in different RCOs such as the PS Store logo and the PSN logo.

Also the there are only meant to be 2 actual logos displayed in top few lines of text 'About Playstation', the 'PS logo' and the 'DNS' logo. They are tiny but they are in the images folder of the RCO. The 'PlayStation' and 'PSP' are meant to be text. And the divx and other logos are also in the images folder of the RCO.

If you wanted to change the logo displayed in this then replace the png file in the images folder, label it exactly the same as the one you are replacing, re-compile the RCO, put it back in the dev_flash and the PS3 will display the logo you wanted instead, though it may look odd if its not the same size as well as the on you replaced.

If RCO mage is giving you issues dumping them then uncheck the VAG sound conversion box as it can cause issues when there are no sound files in the RCO your dumping, I had issue dumping them until I did this and also use RCO Mage MOD v1.1.2 from the devwiki, it works like a charm on windows 10.

 

[sandungas]

This is displayed in the 'Settings', 'System Settings', 'About PlayStation3'.

How else are we supposed to get a peak of it?

If you mean how to modify other parts of that screen... it seems to be composed by several "blocks"

The first block is a single sentence with the "msg_ps_rights" you was talking about in this thread, this sentence is translated to 20 languages

Then the screen does a "pop" (barelly notable) and displays the second block... is the content of file:
dev_flash\vsh\resource\sysconf\credits\PS3_OSS_Noitice.txt
There is only 1 version of this file (is not translated to 20 languages), is a list of the Open Source Software licenses used in PS3 firmware
Seems to be in html, i dont see any character codes for icons



Edit:
Im not sure... but it looks like there is a third block in between the ones im mentioning