PS3 PS3 PRO MOD Release/Information Thread

Status
Not open for further replies.
Everything that gave you problems in HEN you have also removed it in CFW?
Or will you fix it in a future version?

I just fixed the particles, so i'm adding it back to HEN

the only thing i removed in HEN is the Music Wave Customization, impossible at this time.

CFW has full set of features.


I just made a big mistake of replacing a folder from PRO into the 4K PRO, so i lost all the 4K PRO diferrent customizations, i'm remaking it now
 
Last edited:
I just fixed the particles, so i'm adding it back to HEN

the only thing i removed in HEN is the Music Wave Customization, impossible at this time.

CFW has full set of features.


I just made a big mistake of replacing a folder from PRO into the 4K PRO, so i lost all the 4K PRO diferrent customizations, i'm remaking it now

Particles is Awesome. XMB looks beautiful with them.
 
@sandungas @DeViL303 i just replaced the Particules MNU of coldboot 2 to DAY MNU, ALL THE HIGGLES are there =).

And the MNU is unreadable, so i think a corruped mnu that activates this
You mean the higgs particles appeared when doing this ?
Copy:
lines.qrc/override/coldboot2/PARTICLES.mnu (1.296 bytes)
To:
lines.qrc/override/day/PARTICLES.mnu (1.294 bytes)

But if this was the only change needed i guess the other corrupted files was not related ?... i made a table with them somewhere, we need to review them to see which values they was using

Btw, in XForge you can do "right mouse click" in the filelist at left and it have 2 options "Copy Name", and "Copy Size"
This is what i used to copy his paths and sizes in this post, is a handy feature to talk about the files in forums :)
 
Last edited:
You mean the higgs particles appeared when doing this ?


But if this was the only change needed i guess the other corrupted files was not related ?... i made a table with them somewhere, we need to review them to see which values they was using

Btw, in XForge you can do "right mouse click" in the filelist at left and it have 2 options "Copy Name", and "Copy Size"
This is what i used to copy his paths and sizes in this post, is a handy feature to talk about the files in forums :)


I just checked our lines.qrc with the ribbons enabled,

The cooldboot2 MNU is corrupted and what enables the higgs.

so i just extracted it with XForge and Replaced in the Day MNU so it enabled it on the xmb,


It looks completly corruped, its just strange symbons and caracteres.

It's is made by the patch 5 that DeVil303 applied on it, nothing related to the corruped lines.qrc we had before
 
I just checked our lines.qrc with the ribbons enabled,

The cooldboot2 MNU is corrupted and what enables the higgs.

so i just extracted it with XForge and Replaced in the Day MNU so it enabled it on the xmb,


It looks completly corruped, its just strange symbons and caracteres.

It's is made by the patch 5 that DeVil303 applied on it, nothing related to the corruped lines.qrc we had before
But have you tryed to open the extracted file override/day/PARTICLES.mnu in notepad++ and delete all the settings lines, but keep only the first line, so it looks this way:
Then save the file as override/day/PARTICLES.mnu and build the QRC with it
Code:
#MNU_1.0
Im asking about this because this way the .mnu file is legit (the .elf loads it correctly), but there are no settings, so the .elf plays the animation using the default settings (hardcoded inside the .elf)
Is like deleting the .mnu file... but we are not deleting it to prevent problems in the sequence of code that loads it

------------
What you did is pretty much the same than if you edit override/day/PARTICLES.mnu in notepad++ and you replace all this contents by
Code:
><(((()ª>

I think this is not correct, the line with the #MNU_1.0 is like a control check just to know the info that comes next is valid, when we remove it (and the firmware tryes to load the fish) it gets an error

-------------
The other way is to really delete the file (so the .elf cant find it), to do this you need to delete the line for it in the xml control file located at root of the extraction path when you choose [Extract All] in XForge
As probably you realized at this point in the few days you has been using XForge that rebuilding method is inspired in rcomage :D
First you extract all (and it creates a xml control file)... and then that control file is the "boss" that is used when XForge builds the QRC file

So you know... is just a matter of deleting the line where appears the name lines.qrc/override/day/PARTICLES.mnu inside the xml control file... and when you create the QRC is ignored completly (not included in the QRC)
Code:
<file src="override/day/PARTICLES.mnu" id="override/day/PARTICLES.mnu" compression="False" />
 
Last edited:
But have you tryed to open the extracted file override/day/PARTICLES.mnu in notepad++ and delete all the settings lines, but keep only the first line, so it looks this way:
Then save the file as override/day/PARTICLES.mnu and build the QRC with it
Code:
#MNU_1.0
Im asking about this because this way the .mnu file is legit (the .elf loads it correctly), but there are no settings, so the .elf plays the animation using the default settings (hardcoded inside the .elf)
Is like deleting the .mnu file... but we are not deleting it to prevent problems in the sequence of code that loads it

Oh it enabled the higgs, but a litte different

I mean i applied this in the colboot 2 and day

Our patched lines, just enables the higgs in the coldboot and looked cool

this one it enabled A LOT of particles going all over the screen in the coldboot, not isolated as before, and on the xmb is pretty similar that we have with Devil303 sprx patch.

I think this is not correct, the line with the #MNU_1.0 is like a control check just to know the info that comes next is valid, when we remove it (and the firmware tryes to load the fish) it gets an error

-------------
The other way is to really delete the file (so the .elf cant find it), to do this you need to delete the line for it in the xml control file located at root of the extraction path when you choose [Extract All] in XForge
As probably you realized at this point in the few days you has been using XForge that rebuilding method is inspired in rcomage :D
First you extract all (and it creates a xml control file)... and then that control file is the "boss" that is used when XForge builds the QRC file

So you know... is just a matter of deleting the line where appears the name lines.qrc/override/day/PARTICLES.mnu inside the xml control file... and when you create the QRC is ignored completly (not included in the QRC)


Oh i didn't know that, nice to know , i really like this kind of system, i will check this out
 
Last edited:
We can add more files too, is just the files with custom names are going to be ignored by the official firmware, and in CFW/HEN we dont have any custom code intended to load custom files from inside QRC containers

But i just remembered something, in that talks weeks ago when devil was looking at the strings fron inside custom_render_plugin.sprx decrypted in hexeditor if i remember right he found the name RAYS.mnu
That files doesnt exists inside the official QRC files... but now we can add them, is just we dont know anything about them and we are not sure if the firmware is going to load them, but are easy to add :D
 
We can add more files too, is just the files with custom names are going to be ignored by the official firmware, and in CFW/HEN we dont have any custom code intended to load custom files from inside QRC containers

But i just remembered something, in that talks weeks ago when devil was looking at the strings fron inside custom_render_plugin.sprx decrypted in hexeditor if i remember right he found the name RAYS.mnu
That files doesnt exists inside the official QRC files... but now we can add them, is just we dont know anything about them and we are not sure if the firmware is going to laod them, but are easy to add :D





Oh Rays.mnu i wonder what it does, very interesting
 
That was in an older lines.qrc/sprx that I saw the rays.mnu, there is also a rays.fpo and rays.vpo there too iirc. Maybe those or some of the settings from them swapped in place of something else...idk
 
@LuanTeles try to add a file named override/day/RAYS.mnu with this contents
Code:
#MNU_1.0
RAYS:int:1

Incase it works... full party... in the next test you should include the other settings i mentioned in the post of the link, there are some, and seems to be specific for RAYS.mnu
We dont know the data types or the valid range of values for them though
Code:
RAYS
LIGHT FOV
LIGHT ASPECT
LIGHT POS X
LIGHT POS Y
LIGHT TARGET X
LIGHT DEPTH
SPEED 1
SPEED 2
SPEED 3
START
END
RAYS STRENGTH
 
And btw, there are 4 different files for the hours of the day:
override/yoake/RAYS.mnu
override/day/RAYS.mnu
override/higure/RAYS.mnu
override/night/RAYS.mnu

For the tests you should modify all them , just incase your clock enters in a "time zone" where the settings from the MNU file are not applyed... or the values "merges" with other MNU file... or that kid of things that could confuse you when looking at the results of the tests
Is better to have the same exact values in this 4 files, this way you know your changes are applyed the 24 hours of the day (so your clock settings doesnt matters)
 
Here is the rays.vpo/fpo from 0.91 DECR FW.
Cool, that shaders was another important piece of the puzzle :)
But you need to indicate his path, in the way you are uploading them it looks they was located at the root of the QRC container ?


Edit:
Ok, i found it, the paths are:
lib/moyou/rays.fpo
lib/moyou/rays.vpo

There seems to be more:
lib/moyou/newrays.fpo
lib/moyou/newrays.vpo
 
Last edited:
Cool, that shaders was another important piece of the puzzle :)
But you need to indicate his path, in the way you are uploading them it looks they was located at the root of the QRC container ?


Edit:
Ok, i found it, the paths are:
lib/moyou/rays.fpo
lib/moyou/rays.vpo


There seems to be more:
lib/moyou/newrays.fpo
lib/moyou/newrays.vpo

Thanks, i'll mess with it when i wake up, because i'm dying here hahah
 
LuanTeles updated PS3™ 4K Pro with a new update entry:

v5.0

-Added: Automatic Enable HEN to HEN Enabled after a XMB Reload.
-Added: BD/DVD .ISO Folder in Video Column (Requires WebMan).
-Added: Built-in Uninstaller.
-Added: Clear History in PlayStation™Network Column.
-Added: Custom HEN for Categories to Reload after Enabling it.
-Added: Customization Options.
-Added: DECR Firmware 0.90.002 and Classic PSN User's Avatars.
-Added: Flash Games.
-Added: Gameboot Sound for HEN.
-Added: Headset Game Sound for HEN.
-Added: Improved Wave Particles for HEN...

Read the rest of this update entry...
 
Status
Not open for further replies.

Similar threads

Back
Top