PS3 PS3 PRO MOD Release/Information Thread

Status
Not open for further replies.
DeViL303 said:
Cool, If you need any help let me know, I am using that installer for a long time, you can also set it up so it will only install on certain FW versions if that is required. Also worth noting, whatever files you put in the installer, well it will back those files up before overwriting them in the destination, all automatically. then you can use the installer to restore the backup if need be later on.
Click to expand...

Think am going to have a shuffty at this as well....
 
Cypher_CG89 said:
Think am going to have a shuffty at this as well....
Click to expand...
Yeah, its kind of hard to explain, but when you see the folder names it will make sense. basically you can just fill it up with files, destinations can be mixed between hdd and flash, and it does the rest. its genius bit of software IMO.

You can make sub folders too if you want sub options in the menus, and you can add lots of options, so for example your menu could have 10 items with 2 sub options in each, enable and disable for example, with different file sets in each folder.
 
DeViL303 said:
Yeah, its kind of hard to explain, but when you see the folder names it will make sense. basically you can just fill it up with files, destinations can be mixed between hdd and flash, and it does the rest. its genius bit of software IMO.
Click to expand...

Defo worth a look, I have been looking all sorts of source code, compiling it and learning from it, though the one am doing now has my head battered to bits. I always love having a look at how things work and what it does.
 
Guys i have a huuuuge problem, i cant decompile my sysconfi plugin (the Side Bars animations)

when i decompile it under rcomage , the rcomage stop to work, due to my huge size xml. ( i deleted my source code)

Any work round? cuz i dont want to write the whole xml again, that took me about 5 hrs + due to system resources limitations, testing it after everyline i added
 
Other question, there is any way to make my installer install and set the p3t automatically?

will making an editit to the xRegistry.sys set it?
 
you can create a pkg with the edat or p3t. there doesn't seem to be a limit either beyond the normal, system limit of 256? themes. you can even have edats and p3ts as part of one pkg. if you extract the themes, afaik, you won't have issues with encryption.
 
LuanTeles said:
Guys i have a huuuuge problem, i cant decompile my sysconfi plugin (the Side Bars animations)

when i decompile it under rcomage , the rcomage stop to work, due to my huge size xml. ( i deleted my source code)

Any work round? cuz i dont want to write the whole xml again, that took me about 5 hrs + due to system resources limitations, testing it after everyline i added
Click to expand...
Are you sure rcomage is crashing because the bytes size of the main xml ?
In that case im imagining a (very dirty) trick that should work, you can modify the "atributes names" inside the file objattribdef-ps3.ini

Im going to show you an example from the rcomage psdevwiki mod, this ones are the definitions for a "Plane" object
Code: 
[Plane]
; -- BEGIN STANDARD ATTRIBUTE DEFINITION --
positionX = float
positionY = float
positionZ = float
colorScaleR = float
colorScaleG = float
colorScaleB = float
colorScaleA = float
sizeX = float
sizeY = float
sizeZ = float
sizeScaleX = float
sizeScaleY = float
sizeScaleZ = float
anchorMode = unk
onInit = event
positionOverrideX = unk
positionOverrideY = unk
positionOverrideZ = unk
sizeOverrideX = unk
sizeOverrideY = unk
sizeOverrideZ = unk
; -- BEGIN SPECIFIC ATTRIBUTE DEFINITION --
planeImage = image
planeResizeMode = int

And you need to modify it like this:
Code: 
[Plane]
; -- BEGIN STANDARD ATTRIBUTE DEFINITION --
AB1 = float
AB2 = float
AB3 = float
AB4 = float
AB5 = float
AB6 = float
AB7 = float
AB8 = float
AB9 = float
AB10 = float
AB11 = float
AB12 = float
AB13 = float
AB14 = unk
AB15 = event
AB16 = unk
AB17 = unk
AB18 = unk
AB19 = unk
AB20 = unk
AB21 = unk
; -- BEGIN SPECIFIC ATTRIBUTE DEFINITION --
AB22 = image
AB23 = int

This is going to reduce the xml bytes size a lot :encouragement:

*Im using the name "AB" because this can be made with all the other objects... and i used the object "Plane" in this example because is the most commonly used, so maybe doing it just with "Plane" is enought... but if is needed do it with others
Good candidates (because are repeated a lot) are the objects with a name derivated from "menu", "list", and "item" (as example the object "IList")

*Also, im using an unique name for every attribute (like "AB12") because after the rco extraction you can use notepadd++ do make automatic "search-and-replace" to fix the names and restore them
 
Last edited:
sandungas said:
Are you sure rcomage is crashing because the bytes size of the main xml ?
In that case im imagining a (very dirty) trick that should work, you can modify the "atributes names" inside the file objattribdef-ps3.ini

Im going to show you an example from the rcomage psdevwiki mod, this ones are the definitions for a "Plane" object
Code: 
[Plane]
; -- BEGIN STANDARD ATTRIBUTE DEFINITION --
positionX = float
positionY = float
positionZ = float
colorScaleR = float
colorScaleG = float
colorScaleB = float
colorScaleA = float
sizeX = float
sizeY = float
sizeZ = float
sizeScaleX = float
sizeScaleY = float
sizeScaleZ = float
anchorMode = unk
onInit = event
positionOverrideX = unk
positionOverrideY = unk
positionOverrideZ = unk
sizeOverrideX = unk
sizeOverrideY = unk
sizeOverrideZ = unk
; -- BEGIN SPECIFIC ATTRIBUTE DEFINITION --
planeImage = image
planeResizeMode = int

And you need to modify it like this:
Code: 
[Plane]
; -- BEGIN STANDARD ATTRIBUTE DEFINITION --
AB1 = float
AB2 = float
AB3 = float
AB4 = float
AB5 = float
AB6 = float
AB7 = float
AB8 = float
AB9 = float
AB10 = float
AB11 = float
AB12 = float
AB13 = float
AB14 = unk
AB15 = event
AB16 = unk
AB17 = unk
AB18 = unk
AB19 = unk
AB20 = unk
AB21 = unk
; -- BEGIN SPECIFIC ATTRIBUTE DEFINITION --
AB22 = image
AB23 = int

This is going to reduce the xml bytes size a lot :encouragement:

*Im using the name "AB" because this can be made with all the other objects... and i used the object "Plane" in this example because is the most commonly used, so maybe doing it just with "Plane" is enought... but if is needed do it with others
Good candidates (because are repeated a lot) are the objects with a name derivated from "menu", "list", and "item" (as example the object "IList")

*Also, im using an unique name for every attribute (like "AB12") because after the rco extraction you can use notepadd++ do make automatic "search-and-replace" to fix the names and restore them
Click to expand...


Still doesnt work

here is my sysconf https://www.mediafire.com/file/gafd7u52xx595l4/sysconf_plugin.rco/file
 
LuanTeles said:
Also @pinky i saw a time ago u commenting about reboot system without xai_plugin, but i cant find it anymore lol
Click to expand...
<Pair key="icon"><String>/dev_flash/vsh/resource/icons/tex_power_off.png</String></Pair>
<Pair key="title"><String>Power Off</String></Pair>
<Pair key="info"><String>Shut Down the PS3 Console</String></Pair>
<Pair key="module_name"><String>poweroff_plugin</String></Pair>
<Pair key="module_action"><String></String></Pair>


Found this from devil303's post
edit: nvm, I didn't read you saying reboot
 
Last edited:
sandungas said:
Not sure with how many objects you did what i suggested, but if you did it only with one try with more (or with all them)
Thats the only thing i could do to try to fix it, but you can do it too

If it doesnt works then it means the problem is not caused by the xml size (in bytes)... but caused by other reason
Click to expand...

I tried manually dumping his sysconf file with rcomage & it didn't crash. These are the errors I've got:
Capture.PNG


And while compiling...
2.PNG
 
Last edited:
In your screenshot there are 16 warnings at the time of extracting... is because you just copyed a few (so there was more warnings), or thats all ?

At the time of compiling it seems there are multiple errors, and doesnt seems to be related (everyone seems to be a different mistake), but maybe this is caused because the xml was "broken" when it was extracted in the previous step
 
RandomDude said:
I tried manually dumping his sysconf file with rcomage & it didn't crash. These are the errors I've got:
View attachment 15302

And while compiling...
View attachment 15303
Click to expand...

The error when compiling is that the generated xml file is incomplete, u can see the file created is not a complete one, it only generates half of it due to its errors, that's why i cant edit it anymore.

and when decompiling i dunno why those errors, i got the same here, the rco works perfectly and when i compiled it it showed no errors. so i deleted the source and now i have no way to edit it back other than rewriting the xml
 
I've never encountered this issue unless something (image) was missing. however, I have encountered errors when compiling coldboot's vsmx script. decompiling the script causes chinese characters to appear at random lines. I can't recall if it's only white, colored, or both scripts where this can happen. I think someone was trying to develop a better app where this doesn't happen

edit: btw, deleting those lines works.
 
sandungas said:
In your screenshot there are 16 warnings at the time of extracting... is because you just copyed a few (so there was more warnings), or thats all ?
Click to expand...

What I've sent was all the warnings shown in the console. While compiling and while dumping.
 
Last edited:
When you use the code (rcomage dump sysconf_plugin.rco - )
It shows the text in the console. This is weird because in the xml which got dumped it showed less. But in the console it showed more number of planes.

see this:
Capture4.PNG
As you can see page_display_config_deep_color_output is the last plane in the xml and it does not even end.

Look at this console now:
Capture3.PNG


There are a lot more planes after the page_display_config_deep_color_output plane. ex: display_config_deep_color_output1 which is not even there in the xml file.

I used this code from rcomage: rcomage dump sysconf_plugin.rco - --images Images --text Text
 
Well, yeah, is the same "break point" rcomage was indicating in your first image, at line 1924
2-png.15303

Im not sure how much accurate is that error warning about line 1924... actually it should not be much because if something is not properly "closed" then rcomage cant deduce where was supposed to be closed

But overall is finding the break point well, in this screenshot you posted the last extracted lines was 1920 and 1921... actually rcomage is pointing to line 1924 becaue is a "children" object of 1920 and 1921
capture4-png.15309


So the break point is around there... page_display_config_deep_color_output (line 1920) or one of his childrens
But what is broken exactly ?... i dont know

It looks by using rcomage in command line with the command you suggested you can show some of the "broken" lines... thats good i guess because you could redirect the command line output > log.txt (to keep a record of it and try to reconstruct the xml manually later)
 
Status
Not open for further replies.

Similar threads

Back
Top