PS3 [Research] Modifying the Coldboot/Gameboot Sequence (custom_render_plugin.sprx/rco)

Newbie2019 said:
What are you guys trying to do?

Port the Effects of the CFW pro mod to the HEN one?

if yes how is it going? cuz mine cousin's cfw ps3 has it, and i want it so bad, because my hen doesn't has it and the gameboot effects too
Click to expand...

Oh i forgot about the Gameboot too, is another thing by SPRX too
 
LuanTeles said:
The Boson Particles will always follow the same direction, shaking the DS3 will make it only run faster.

About the custom_render.rco...
Click to expand...
Ok, so we can say the particles (all them) are ignoring the dualshock3 sensors completly in the coldboot, right ?

About the <FireEvents> in your coldboot... are the officials, so ok... we can forget about them, they are not the responsibles of the boson magic

LuanTeles said:
But the sprx one have many more effects and doesnt slow down a bit
Click to expand...
In the .sprx the name PARtICLES.mnu only appears 1 or 2 times (im not sure but i bet on it, devil mentioned it as far i remember) because is compiled code, at runtime it changes the path (from inside the qrc structure) to load a different PARTICLES.mnu

But the fact is inside lines.qrc there are 13 different PARTICLES.mnu files (1 for the base + 12 for enviroments)

The patch in the sprx maybe is remapping all them (i guess)... so is "nuking" all them... in plain words is like deleting all them
Dunno, but im guessing is somthing like that
Newbie2019 said:
What are you guys trying to do?

Port the Effects of the CFW pro mod to the HEN one?

if yes how is it going? cuz mine cousin's cfw ps3 has it, and i want it so bad, because my hen doesn't has it and the gameboot effects too
Click to expand...
Well, this thread is like frankenstein laboratory, half of the experiments was failures, and some gave an unexpected results (like this rare boson particle we are talking in the latest posts), lol

But yes, some of the patches used in the PS4 PRO MOD made to an .sprx cant be used in HEN... and we are trying to see if they can be "ported" to apply them in a file named lines.qrc

That file lines.qrc still have a lot of unknown secrets so there is room for improvements in it, in the meantime we are learning how it works :)
 
sandungas said:
In the .sprx the name PARtICLES.mnu only appears 1 or 2 times (im not sure but i bet on it, devil mentioned it as far i remember) because is compiled code, at runtime it changes the path (from inside the qrc structure) to load a different PARTICLES.mnu

But the fact is inside lines.qrc there are 13 different PARTICLES.mnu files (1 for the base + 12 for enviroments)

The patch in the sprx maybe is remapping all them (i guess)... so is "nuking" all them... in plain words is like deleting all them
Dunno, but im guessing is somthing like that
Click to expand...
Im taking a look at it for confirmation... the name PARTICLES appears only one time inside custom_render_plugin.sprx

So that patch in the .sprx was "nuking" all them (the firmware cant load any setting inside any of the 13 PARTICLES.mnu files inside lines.qrc)

To replicate that same behaviour with patches in lines.qrc is needed to apply 13 patches
 
LuanTeles said:
With the SPRX


the only thing i noticed is the particles colors, that my original pro one, have many of them in gold, blue and red... this one is only the white ones, but i can port it later anyways, just following pinks tutorials =P.
Click to expand...

Still about the colors, notice that all the effects are white

now with the original pro .qrc you can notice a lot of blue, gold, and red ones ( in the video it doesn't seem red, but they are) and ofc many white


so probably it has some particles files modded too
 
Last edited:
sandungas said:
About the <FireEvents> in your coldboot... are the officials, so ok... we can forget about them, they are not the responsibles of the boson magic
Click to expand...
Btw, the .sprx had some patch to remap the <fireEvents> ?
you know... the ones you are using in the xml coldboot animations from custom_render_plugin.rco
anim_coldboot_BootBG1
anim_coldboot_BootBG2
anim_coldboot_NormalBG
anim_coldboot_NormalBG2
anim_coldboot_ShowGUI
anim_coldboot_Finished

Incase the .sprx had some of that files remapped now you are missing that effects for HEN
This can be "ported" too for HEN into the custom_render_plugin.rco... just by renaming them in the xml
 
sandungas said:
Btw, the .sprx had some patch to remap the <fireEvents> ?
you know... the ones you are using in the xml coldboot animations from custom_render_plugin.rco
anim_coldboot_BootBG1
anim_coldboot_BootBG2
anim_coldboot_NormalBG
anim_coldboot_NormalBG2
anim_coldboot_ShowGUI
anim_coldboot_Finished

Incase the .sprx had some of that files remapped now you are missing that effects for HEN
This can be "ported" too for HEN into the custom_render_plugin.rco... just by renaming them in the xml
Click to expand...

as far as i know, @DeViL303 only patched the particles, i'll try to check because i sucks at hex/sprx and .qrc

EDIT

I didnt find anything related to FireEvents inside the sprx
 
@sandungas If you could find and apply the PARTICLES_UI remap to this qrc instead it would help us to figure it out., as there are just too many differences too be sure of porting it all to the new qrc.

I checked in HEX with file compare and the only difference in the sprx I can see is that one 3 byte patch adding "_UI" in that one place. But I guess that is equal to all 13 patches in the qrc..idk.
 

Attachments

DeViL303 said:
@sandungas If you could find and apply the PARTICLES_UI remap to this qrc instead it would help us to figure it out., as there are just too many differences too be sure of porting it all to the new qrc.

I checked in HEX with file compare and the only difference in the sprx I can see is that one 3 byte patch adding "_UI" in that one place. But I guess that is equal to all 13 patches in the qrc..idk.
Click to expand...
Is going to take me time, but i got you... we need to step back to isolate "the magic" :)

And i guess im going to do what you suggested, im going to remap only this ones:
lines.qrc/PARTICLES.mnu
lines.qrc/override/coldboot1/PARTICLES.mnu
lines.qrc/override/coldboot2/PARTICLES.mnu
 
We need to be sure we are remapping the correct way too, is making TWO "PARTICLES UI" entries and NO "PARTICLES" entry in the sprx the same as remapping PARTICLES to PARTICLES_UI in the qrc. I have a feeling it not. Think about it,

With the sprx patch:
  • Either everything that calls on "PARTICLES" will instead calls on "PARTICLES_UI"?
  • Or everything trying to call on "PARTICLES" gets nothing as there is no "PARTICLES"?
 
sandungas said:
FILE: https://www.sendspace.com/file/jb54nv

It have 3 patches applyed:
SEARCH
000833200000050E = PARTICLES.mnu
00001C0000000510 = override/coldboot1/PARTICLES.mnu
0000276000000510 = override/coldboot2/PARTICLES.mnu
REPLACE
000838D00000017D = PARTICLES_UI.mnu
Click to expand...
Sweet, thats it. :) Working, higgs boson and all.

Now I wonder can we use the rco with a coldboot animation looping to get them on the normal XMB too :)
 
I am just testing, it it hard to know if the controller shaking always had an effect on the coldboot particles as there is not really any particles there normally in during the coldboot in OFW. The controller definitely has a big effect now with this patch applied.

BTW the higgs boson particles seem to be static animations and look exactly the same every time if I dont shake the controller.... interesting.
 
DeViL303 said:
Sweet, thats it. :) Working, higgs boson and all.
Click to expand...
Nice :)
Probably we can reduce the patching to only 2 patches instead of 3... for this test i patched the PARTICLES.mnu (base file) and PARTICLES.mnu for coldboot1 and coldboot2, but probably is just needed to patch coldboot2 (the modern coldboot, not the old one)

DeViL303 said:
I checked in HEX with file compare and the only difference in the sprx I can see is that one 3 byte patch adding "_UI" in that one place. But I guess that is equal to all 13 patches in the qrc..idk.
Click to expand...
Yes, im checking it to have a confirmation, only 3 bytes patched in the .sprx to rename "PARTICLES" to "PARTICLES_UI" :)
it should be the same than applying 13 patches in lines.qrc

DeViL303 said:
We need to be sure we are remapping the correct way too, is making TWO "PARTICLES UI" entries and NO "PARTICLES" entry in the sprx the same as remapping PARTICLES to PARTICLES_UI in the qrc. I have a feeling it not. Think about it,

With the sprx patch:
  • Either everything that calls on "PARTICLES" will instead calls on "PARTICLES_UI"?
  • Or everything trying to call on "PARTICLES" gets nothing as there is no "PARTICLES"?
Click to expand...
In my oppinion (not sure) both afirmations are right, at coldboot the firmware cant load any settings from the originals PARTICLES.mnu, but we are "feeding" it with the contents of PARTICLES_UI
And i think the firmware ignores the contents of the remapped PARTICLES_UI

In other words... we could do the remapping using as a target other .mnu file (or a dummy), i think the result should be the same

DeViL303 said:
Now I wonder can we use the rco with a coldboot animation looping to get them on the normal XMB too :)
Click to expand...
I dont get why the boson appears only in the coldboot... this is somthing some of you mentioned before

But main XMB have his own "enviroment" files... with his specific PARTICLES.mnu
We could remap them too... not sure if we tryed this before
 
Hmm, i just imagined a way to verify what is doing the firmware with the settings from the remapped PARTICLES_UI

The idea is... the values we are using for the SEARCH/REPLACE patterns are composed by offset+size, as example:
000833200000050E = PARTICLES.mnu
00001C0000000510 = override/coldboot1/PARTICLES.mnu
0000276000000510 = override/coldboot2/PARTICLES.mnu

Here you can see the PARTICLES.mnu for coldboot1 and for coldboot2 are located at different offsets... but have the same size (0x510)

So... we can replace the 0x510 by... zero
This way when the firmware reads the lines.qrc structure will not load them (and also it will not load the contents of the PARTICLES_UI we was remapping to them)
 
sandungas said:
Nice :)
Probably we can reduce the patching to only 2 patches instead of 3... for this test i patched the PARTICLES.mnu (base file) and PARTICLES.mnu for coldboot1 and coldboot2, but probably is just needed to patch coldboot2 (the modern coldboot, not the old one)
Click to expand...
Yeah, or maybe just one patch even on the correct coldboot section.
sandungas said:
Yes, im checking it to have a confirmation, only 3 bytes patched in the .sprx to rename "PARTICLES" to "PARTICLES_UI" :)
it should be the same than applying 13 patches in lines.qrc
Click to expand...
Cool.
sandungas said:
In my oppinion (not sure) both afirmations are right, at coldboot the firmware cant load any settings from the originals PARTICLES.mnu, but we are "feeding" it with the contents of PARTICLES_UI
And i think the firmware ignores the contents of the remapped PARTICLES_UI

In other words... we could do the remapping using as a target other .mnu file (or a dummy), i think the result should be the same
Click to expand...
Maybe but not sure. We could do some tests to figure that out.

sandungas said:
I dont get why the boson appears only in the coldboot... this is somthing some of you mentioned before
Click to expand...
Yeah. Maybe it was a special effect they programmed but then changed their mind and used over overrides to get of it, now we have disabled the over rides and can see it like it was meant to be :) It sounds cool anyway :-p

sandungas said:
But main XMB have his own "enviroment" files... with his specific PARTICLES.mnu
We could remap them too... not sure if we tryed this before
Click to expand...
If you want to try I don't mind testing, it would be cool to have the occasional higgs on the main XMB too, but if is going to be a static repeating animation then its not great.
sandungas said:
Hmm, i just imagined a way to verify what is doing the firmware with the settings from the remapped PARTICLES_UI

The idea is... the values we are using for the SEARCH/REPLACE patterns are composed by offset+size, as example:
000833200000050E = PARTICLES.mnu
00001C0000000510 = override/coldboot1/PARTICLES.mnu
0000276000000510 = override/coldboot2/PARTICLES.mnu

Here you can see the PARTICLES.mnu for coldboot1 and for coldboot2 are located at different offsets... but have the same size (0x510)

So... we can replace the 0x510 by... zero
This way when the firmware reads the lines.qrc structure will not load them (and also it will not load the contents of the PARTICLES_UI we was remapping to them)
Click to expand...
We can try if you want.
 
sandungas said:
FILE: https://www.sendspace.com/file/jb54nv

It have 3 patches applyed:
SEARCH
000833200000050E = PARTICLES.mnu
00001C0000000510 = override/coldboot1/PARTICLES.mnu
0000276000000510 = override/coldboot2/PARTICLES.mnu
REPLACE
000838D00000017D = PARTICLES_UI.mnu
Click to expand...

God damn @sandungas you did it, looks really nice, now it is missing only the xmb effects, maybe there are some more places to be patched, the colorful particles are in the coldboot now but there are not present in the xmb
 
Please try this one, is a test to see if the theory i wrote before is right... incase im right the result should be exactly the same than the previous file i uploaded (when i was remapping PARTICLES to PARTICLES_UI)
FILE: https://www.sendspace.com/file/2h1u7r

The patches applyed in this test are (im replacing his size = zero in this 3 files):
SEARCH ---> 000833200000050E = PARTICLES.mnu
REPLACE ---> 0008332000000000

SEARCH ---> 00001C0000000510 = override/coldboot1/PARTICLES.mnu
REPLACE ---> 00001C0000000000

SEARCH ---> 0000276000000510 = override/coldboot2/PARTICLES.mnu
REPLACE ---> 0000276000000000
 
sandungas said:
Please try this one, is a test to see if the theory i wrote before is right... incase im right the result should be exactly the same than the previous file i uploaded (when i was remapping PARTICLES to PARTICLES_UI)
FILE: https://www.sendspace.com/file/2h1u7r

The pathes applyes in this test are:
SEARCH ---> 000833200000050E = PARTICLES.mnu
REPLACE ---> 0008332000000000

SEARCH ---> 00001C0000000510 = override/coldboot1/PARTICLES.mnu
REPLACE ---> 00001C0000000000

SEARCH ---> 0000276000000510 = override/coldboot2/PARTICLES.mnu
REPLACE ---> 0000276000000000
Click to expand...

Surely i'll but i can report only by tomorrow evening, i'm going to bed now

Thanks for your efforts guys
 
You must log in or register to reply here.

Similar threads

Back
Top