PS3 [Research] Modifying the Coldboot/Gameboot Sequence (custom_render_plugin.sprx/rco)
sandungas
Developer
It cant be, in patch 5 i was "deleting" only PARTICLES.mnu for coldboot1 and coldboot2
So the other enviroments are not affected (the others should display the same than OFW)
For main XMB there are involved several enviroments (and everyone of them have his specific PARTICLES.mnu)
Are at least 4 enviroments, for the different quarters of the day, named: yoake, day, higure, night
And maybe another 2 more enviroments (i dont know what does this ones) named: black and bright
The .sprx patch was deleting all the PARTICLES.mnu files for all the enviroments that uses them (12 enviroments + 1 of the base = 13 deleted files in total)
Yes.
Edit:
This video is from your .sprx patch devil ?
sandungas
Developer
Ok, and with a lines.qrc file that belongs to an <unknown> firmware version and contains <unknown> modifications
Btw, both your lines.qrc are identical (the sparklyshit and the one luanteles uploded from his ps4 pro mod) and are unknown, all i can say it doesnt belongs to this firmware versions
So is either 4.31 or older
time to move onAnd, i would like to have the original lines.qrc to compare it... without the original is imposible to see what has been modifyed
I only have the lines.qrc file versions marked in red in that table
------------------------
*Btw, i just realized inside the spline.elf and particles.elf it can be seen the SDK version (and revision that is more accurate), who compiled it. And also the GCC version
I guess this is somthing standard for all the .elf files... but i just realized it can be used to compare the lines.qrc files
Last edited:
sandungas
Developer
Yes, if we are going to continue this research we need to move to the lines.qrc 4.60-4.85
At this point we know how to "port" the .sprx patch you was doing to lines.qrc 4.60-4.85 but im not so sure if it will look exactly like the video because the lines.qrc (from unknown version) we have been using as guinea pig probably have others .mnu files modifyed
I can make an accurate list of the modification only if someone uploads the original lines.qrc
Thats the first step to "port" it to 4.85
Also, it would allow us to see how many of the things we see in the screen are custom
I never realized before, but you are right, in the 2 screenshots you made (wth different lines.qrc files so it was after a reboot) the geometry of the waves are almost identical, lol, so it seems the wave always starts exactly with the same parameters (and the particles probably too)
The biggest difference in the wave in your 2 screenshots is the size... but in test5 and test6 i was not modifying anything related with the wave
The only explain i find to that is the wave reacts to the particles (and viceversa probably). The changes of test6 made the particles to look smaller... so the wave became smaller too
Dunno, just a theory
I think one of the main differences with the higgs sprx patch compared to standard official FW animation is the camera position is closer to the wave/particles(zoom), The default value is zoomed in on all environments, and the override is causing a zoom out. I think this is nicer and we could try to copy the default settings into the override if possible.Yes, if we are going to continue this research we need to move to the lines.qrc 4.60-4.85
At this point we know how to "port" the .sprx patch you was doing to lines.qrc 4.60-4.85 but im not so sure if it will look exactly like the video because the lines.qrc (from unknown version) we have been using as guinea pig probably have others .mnu files modifyed
I can make an accurate list of the modification only if someone uploads the original lines.qrc
Thats the first step to "port" it to 4.85
Also, it would allow us to see how many of the things we see in the screen are custom
I never realized before, but you are right, the 2 screenshots you made (wth different lines.qrc files so it was after a reboot) are almost identical, lol, so it seems the wave always starts exactly with the same parameters (and the particles probably too)
The biggest difference in the wave in your 2 screenshots is the size... but in test5 and test6 i was not modifying anything related with the wave
The only explain i find to that is the wave reacts to the particles (and viceversa probably). The changes of test6 made the particles to look smaller... so the wave became smaller too
Dunno, just a theory
Here is the 4.84 OFW lines.qrc attached:
sandungas
Developer
Hmm, this is what can be seen in the spline.elf of the "sparklyshit" lines.qrc*Btw, i just realized inside the spline.elf and particles.elf it can be seen the SDK version (and revision that is more accurate), who compiled it. And also the GCC version
I guess this is somthing standard for all the .elf files... but i just realized it can be used to compare the lines.qrc files
Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00059CC0 47 43 43 3A 20 28 47 4E 55 29 20 GCC: (GNU)
00059CD0 34 2E 31 2E 31 20 28 53 44 4B 33 33 30 2C 20 24 4.1.1 (SDK330, $
00059CE0 52 65 76 3A 20 33 33 37 38 20 24 29 Rev: 3378 $)As far i can see in other lines.qrc files... the SDK version is several monts older than the release date of the firmware containing the lines.qrc
But in this one is very old SDK330... even before the PS3 was hacked (that happened in 3.40)
So... i guess it belongs to 3.40 (the first vulnerable PS3 firmware)
sandungas
Developer
Confirmed, i downloaded firmware 3.40 and im comparing them
sandungas
Developer
I dont know, but im sure the lines.qrc we was using as a guinea pig is from 3.40
The internal QRC structure is identical to the official (this means all the changes was made by "injecting" files in it), and i have a list of all the files that has been modifyed (23 MNU + 11 DDS + 2 TGA = 36 files in total)
Can you upload the latest lines.qrc from your PS4 PRO mod just to be sure ?
Last edited:
Damn 36 files so there are a lot of changes
BTW here you are, the lastest one of my mod
It will not be that different as the one that we are using besides some news colors in it
http://www.mediafire.com/file/m6hzcjgc3x70yhv/lines.qrc/file
sandungas
Developer
Pffff, and some of the MNU files are damaged, im sure it was caused by the tools you used, is like a disalignment because the tool was "injecting" the files at a different offset, let me show you an example
lines.qrc/override/welcome_2/HDR.mnu (official at left, custom at right)
Inmediatly after it is located:
lines.qrc/override/welcome_2/LINE1.mnu (official at left, custom at right)
The officials are perfect... but as you can see some of the customs are broken at begining and at the ending
The "garbage" at begining belongs to the previous file... and the ending is missing (because is located in the next file)
This sucks, because we dont know how the firmware is dealing with that "bugs"... actually in some of the experiments we was doing in this thread in the past couple of days we was breaking that first characters at top of the MNU files (where it tells "#MNU_1.0") and the firmware function related did seems to stop running
Also, is a pita to port it, i was hoping the differences in the MNU files was not going to be so much
Also, some of the settings that are cropped at the ending are valid, lol, as example.... ive seen one where the original value was lets say... =0.123456 and after the cropping is =0.123 (the cropping removed 3 digits, the value is still valid, but is not exactly what you was trying to do, lol)
The only good thing i noticed related with this broken MNU files is the "breakpoint" seems to affect only the MNU files located after that breakpoint
In other words... the MNU files located first seems to be fine... are only damaged the ones located at the end
lines.qrc/override/welcome_2/HDR.mnu (official at left, custom at right)
Inmediatly after it is located:
lines.qrc/override/welcome_2/LINE1.mnu (official at left, custom at right)
The officials are perfect... but as you can see some of the customs are broken at begining and at the ending
The "garbage" at begining belongs to the previous file... and the ending is missing (because is located in the next file)
This sucks, because we dont know how the firmware is dealing with that "bugs"... actually in some of the experiments we was doing in this thread in the past couple of days we was breaking that first characters at top of the MNU files (where it tells "#MNU_1.0") and the firmware function related did seems to stop running
Also, is a pita to port it, i was hoping the differences in the MNU files was not going to be so much
Also, some of the settings that are cropped at the ending are valid, lol, as example.... ive seen one where the original value was lets say... =0.123456 and after the cropping is =0.123 (the cropping removed 3 digits, the value is still valid, but is not exactly what you was trying to do, lol)
The only good thing i noticed related with this broken MNU files is the "breakpoint" seems to affect only the MNU files located after that breakpoint
In other words... the MNU files located first seems to be fine... are only damaged the ones located at the end
Last edited:
sandungas
Developer
Right, im comparing it with the other from devil303... are siamese brothers, separated at birth :P
In between your version and devil version there are only 7 different files
textures/month_bg/rgb/01.dds
textures/month_bg/rgb/02.dds
textures/month_bg/rgb/03.dds
textures/month_bg/rgb/09.dds
textures/month_bg/rgb/10.dds
textures/month_bg/rgb/11.dds
textures/month_bg/rgb/12.dds
sandungas
Developer
Prepare the scalpels dear doctors, i got the recipe to replicate the lines.qrc from the PS4 PRO mod to any other firmware version
Right now i could post an accurate list with all the values that needs to be modifyed in the .MNU files, but let me delay it a bit, we need to make a good plan
Lets make a recap... we are trying to achieve 3 things:
-Port devil .sprx patch (with the higgs boson particle) to lines.qrc
-Isolate the higgs boson particle to have a better control of it and play a bit more with it
-Port the lines.qrc from PR4 MOD to firmware 4.85
The port of the lines.qrc of PR4 PRO mod is something i was trying to dodge (because i knew it was going to be a pita), but at this point i spent a lot of time looking at that files that i decided to do it, also because i noticed several things about your lines.qrc that worths to be discussed, also because both you was using it, also because the PS4 PRO mod is very popular, and that lines.qrc is another good guinea pig for people to play with... so lets "fix" it now and after that we can return to the experiments with the higgs boson
After that we can use that lines.qrc (or the official) for the experiments with the higgs boson, in my oppinion is better to start using the official for the experiments, but we will see
What i want to do is to post the info needed for you to "port" it by using some of the tools that exists (from glowball, brunolee, etc...), i dont know what you are using and im not used to that tools but it should be easy for you and any other people that wants to play around with this, btw if some of you have a favourite tool to modify lines.qrc and want to suggest it please do because it looks some of that tools are broken because they haves the file offsets/sizes hardcoded in them (and belongs to old firmwares), i think this is the reason why your lines.qrc was damaged, i could tell you that file offsets/sizes to "update" the tool to 4.85
Anyway, this is (a shorted) list of the files that was modifyed in your lines.qrc
We need to discuss what we are going to do with them, this will take us some posts, hope all you are fine with it, is also a good timing for you to review everything you did because you are going to see all the changes together in a single list
The 2 characters at left means:
ck = custom, ok
cd = custom, damaged
od = official, damaged
Notes
*Not sure if you have the DDS and TGA files or if the toools you use can extract them, but incase you need them i can upload them
*You had the Noise.tga image damaged, is the official file, but instead of starting with zeroes it starts with the "garbage" taken from the previous file... not sure if the firmware was loading it as valid or it was simply ignoring it because that garbage bytes... anyway this fie was modifyed by mistake (in other words, we dont need to "port" it)
*All the override/welcome_1/*****.mnu and override/welcome_2/*****.mnu are damaged because the "breakpoint" of the QRC structure happens before them, so all them are displaced some bytes, most of them are "od = official damaged", and there are a couple "cd = custom damaged"... as far i see that "cd" was modifyed unintentionally, because well... that "welcome_1" and "welcome_2" enviroments are a bit pointless, im not sure when are used exactly but i guess one of them is used inmediatly when you restore factory settings (or the first time you boot the PS3 after formating the hdd), and the other pretty much the same.. i dont think you was trying to customize that screens, right ?.. so... we can forget about them... in other words the MNU files used in the "welcome_1" and "welcome_2" enviroments doesnt needs to be "ported", right ?
So... this reduces the list of MNU files that needs to be "ported" to the first 15
Right now i could post an accurate list with all the values that needs to be modifyed in the .MNU files, but let me delay it a bit, we need to make a good plan
Lets make a recap... we are trying to achieve 3 things:
-Port devil .sprx patch (with the higgs boson particle) to lines.qrc
-Isolate the higgs boson particle to have a better control of it and play a bit more with it
-Port the lines.qrc from PR4 MOD to firmware 4.85
The port of the lines.qrc of PR4 PRO mod is something i was trying to dodge (because i knew it was going to be a pita), but at this point i spent a lot of time looking at that files that i decided to do it, also because i noticed several things about your lines.qrc that worths to be discussed, also because both you was using it, also because the PS4 PRO mod is very popular, and that lines.qrc is another good guinea pig for people to play with... so lets "fix" it now and after that we can return to the experiments with the higgs boson
After that we can use that lines.qrc (or the official) for the experiments with the higgs boson, in my oppinion is better to start using the official for the experiments, but we will see
What i want to do is to post the info needed for you to "port" it by using some of the tools that exists (from glowball, brunolee, etc...), i dont know what you are using and im not used to that tools but it should be easy for you and any other people that wants to play around with this, btw if some of you have a favourite tool to modify lines.qrc and want to suggest it please do because it looks some of that tools are broken because they haves the file offsets/sizes hardcoded in them (and belongs to old firmwares), i think this is the reason why your lines.qrc was damaged, i could tell you that file offsets/sizes to "update" the tool to 4.85
Anyway, this is (a shorted) list of the files that was modifyed in your lines.qrc
We need to discuss what we are going to do with them, this will take us some posts, hope all you are fine with it, is also a good timing for you to review everything you did because you are going to see all the changes together in a single list
Code:
ck = LINE1.mnu
ck = override/black/LINE1.mnu
ck = override/bright/LINE1.mnu
ck = override/coldboot1/LINE1.mnu
ck = override/day/LINE1.mnu
ck = override/gameboot1/LINE1.mnu
ck = override/gameboot2/BACKGROUND.mnu
ck = override/gameboot3/LINE1.mnu
ck = override/gameboot4/LINE1.mnu
ck = override/gameboot5/BACKGROUND.mnu
ck = override/gameboot5/LINE1.mnu
ck = override/higure/LINE1.mnu
ck = override/initial_setting/LINE1.mnu
ck = override/night/LINE1.mnu
ck = override/yoake/LINE1.mnu
od = override/welcome_1/BACKGROUND.mnu = 9 characters missing at the end (NIGHT WHIT BIAS:float)
od = override/welcome_1/HDR.mnu = 11 characters added at begining, 9 characters missing at the end (DITHER:float:0)
cd = override/welcome_1/LINE1.mnu = 11 characters added at begining, 7 characters missing at the end (FFD SHADE)
od = override/welcome_1/PARTICLES.mnu = 11 characters added at begining, 9 characters missing at the end (glare p2:floa)
od = override/welcome_2/BACKGROUND.mnu = 11 characters added at begining, 22 characters missing at the end (NIGHT WHIT)
od = override/welcome_2/HDR.mnu = 23 characters added at begining (float:0.486059), 22 characters missing at the end (DIT)
cd = override/welcome_2/LINE1.mnu = 23 characters added at begining (t:0.00392157), 22 characters missing at the end (FFD SHADER:int:1)
od = override/welcome_2/PARTICLES.mnu = 24 characters added at begining (ER:int:1), 24 characters missing at the end (gl)
od = textures/TGA/Noise.tga = 9 bytes added at begining (t:8.41834)
ck = textures/month_bg/rgb/01.dds
ck = textures/month_bg/rgb/02.dds
ck = textures/month_bg/rgb/03.dds
ck = textures/month_bg/rgb/04.dds
ck = textures/month_bg/rgb/05.dds
ck = textures/month_bg/rgb/07.dds
ck = textures/month_bg/rgb/08.dds
ck = textures/month_bg/rgb/09.dds
ck = textures/month_bg/rgb/10.dds
ck = textures/month_bg/rgb/11.dds
ck = textures/month_bg/rgb/12.dds
ck = particles/proc_iridescent.tgaThe 2 characters at left means:
ck = custom, ok
cd = custom, damaged
od = official, damaged
Notes
*Not sure if you have the DDS and TGA files or if the toools you use can extract them, but incase you need them i can upload them
*You had the Noise.tga image damaged
, is the official file, but instead of starting with zeroes it starts with the "garbage" taken from the previous file... not sure if the firmware was loading it as valid or it was simply ignoring it because that garbage bytes... anyway this fie was modifyed by mistake (in other words, we dont need to "port" it)*All the override/welcome_1/*****.mnu and override/welcome_2/*****.mnu are damaged because the "breakpoint" of the QRC structure happens before them, so all them are displaced some bytes, most of them are "od = official damaged", and there are a couple "cd = custom damaged"... as far i see that "cd" was modifyed unintentionally, because well... that "welcome_1" and "welcome_2" enviroments are a bit pointless, im not sure when are used exactly but i guess one of them is used inmediatly when you restore factory settings (or the first time you boot the PS3 after formating the hdd), and the other pretty much the same.. i dont think you was trying to customize that screens, right ?.. so... we can forget about them... in other words the MNU files used in the "welcome_1" and "welcome_2" enviroments doesnt needs to be "ported", right ?
So... this reduces the list of MNU files that needs to be "ported" to the first 15
Code:
ck = LINE1.mnu <------------------------- this is the base, i think you should keep it official
ck = override/day/LINE1.mnu <------------- main XMB
ck = override/higure/LINE1.mnu <------------- main XMB
ck = override/night/LINE1.mnu <------------- main XMB
ck = override/yoake/LINE1.mnu <------------- main XMB
ck = override/initial_setting/LINE1.mnu <--- what does this one ?
ck = override/black/LINE1.mnu <----------- unknow usage
ck = override/bright/LINE1.mnu <----------- unknow usage
ck = override/coldboot1/LINE1.mnu
ck = override/gameboot1/LINE1.mnu
ck = override/gameboot2/BACKGROUND.mnu
ck = override/gameboot3/LINE1.mnu
ck = override/gameboot4/LINE1.mnu
ck = override/gameboot5/LINE1.mnu
ck = override/gameboot5/BACKGROUND.mnu
Last edited:
Nice work.
I tried, but at some point we started using your one again as it was still different.
That explains a lot, when I was porting it using hex editor, I came across a jump. I assumed that Sony had edited the qrc and added something which had pushed everything else forward. But it seems like it was just a bad edit by someone beforehand.Pffff, and some of the MNU files are damaged, im sure it was caused by the tools you used, is like a disalignment because the tool was "injecting" the files at a different offset, let me show you an example
lines.qrc/override/welcome_2/HDR.mnu (official at left, custom at right)
Inmediatly after it is located:
lines.qrc/override/welcome_2/LINE1.mnu (official at left, custom at right)
The officials are perfect... but as you can see some of the customs are broken at begining and at the ending
The "garbage" at begining belongs to the previous file... and the ending is missing (because is located in the next file)
This sucks, because we dont know how the firmware is dealing with that "bugs"... actually in some of the experiments we was doing in this thread in the past couple of days we was breaking that first characters at top of the MNU files (where it tells "#MNU_1.0") and the firmware function related did seems to stop running
Also, is a pita to port it, i was hoping the differences in the MNU files was not going to be so much
Also, some of the settings that are cropped at the ending are valid, lol, as example.... ive seen one where the original value was lets say... =0.123456 and after the cropping is =0.123 (the cropping removed 3 digits, the value is still valid, but is not exactly what you was trying to do, lol)
The only good thing i noticed related with this broken MNU files is the "breakpoint" seems to affect only the MNU files located after that breakpoint
In other words... the MNU files located first seems to be fine... are only damaged the ones located at the end
This also explains why this qrc seems to be unique, I tried others and none had the same effects as this one.
So it seems like both the original patches and my sprx both came across something interesting by mistake. Yeah I was using the standard ps pro qrc, Luanteles has replaced some of the dds files in his very latest revision released the other day, that is why you see those differences, they are very new changes.
It would be cool , but I think you don't need to worry too my much about porting the complete pro qrc changes, figuring out what is happening with it is interesting though as it has some really nice effects.Prepare the scalpels dear doctors, i got the recipe to replicate the lines.qrc from the PS4 PRO mod to any other firmware version
Right now i could post an accurate list with all the values that needs to be modifyed in the .MNU files, but let me delay it a bit, we need to make a good plan
Lets make a recap... we are trying to achieve 3 things:
-Port devil .sprx patch (with the higgs boson particle) to lines.qrc
-Isolate the higgs boson particle to have a better control of it and play a bit more with it
-Port the lines.qrc from PR4 MOD to firmware 4.85
The port of the lines.qrc of PR4 PRO mod is something i was trying to dodge (because i knew it was going to be a pita), but at this point i spent a lot of time looking at that files that i decided to do it, also because i noticed several things about your lines.qrc that worths to be discussed, also because both you was using it, also because the PS4 PRO mod is very popular, and that lines.qrc is another good guinea pig for people to play with... so lets "fix" it now and after that we can return to the experiments with the higgs boson
After that we can use that lines.qrc (or the official) for the experiments with the higgs boson, in my oppinion is better to start using the official for the experiments, but we will see
What i want to do is to post the info needed for you to "port" it by using some of the tools that exists (from glowball, brunolee, etc...), i dont know what you are using and im not used to that tools but it should be easy for you and any other people that wants to play around with this, btw if some of you have a favourite tool to modify lines.qrc and want to suggest it please do because it looks some of that tools are broken because they haves the file offsets/sizes hardcoded in them (and belongs to old firmwares), i think this is the reason why your lines.qrc was damaged, i could tell you that file offsets/sizes to "update" the tool to 4.85
Anyway, this is (a shorted) list of the files that was modifyed in your lines.qrc
We need to discuss what we are going to do with them, this will take us some posts, hope all you are fine with it, is also a good timing for you to review everything you did because you are going to see all the changes together in a single list
Code:ck = LINE1.mnu ck = override/black/LINE1.mnu ck = override/bright/LINE1.mnu ck = override/coldboot1/LINE1.mnu ck = override/day/LINE1.mnu ck = override/gameboot1/LINE1.mnu ck = override/gameboot2/BACKGROUND.mnu ck = override/gameboot3/LINE1.mnu ck = override/gameboot4/LINE1.mnu ck = override/gameboot5/BACKGROUND.mnu ck = override/gameboot5/LINE1.mnu ck = override/higure/LINE1.mnu ck = override/initial_setting/LINE1.mnu ck = override/night/LINE1.mnu ck = override/yoake/LINE1.mnu od = override/welcome_1/BACKGROUND.mnu = 9 characters missing at the end (NIGHT WHIT BIAS:float) od = override/welcome_1/HDR.mnu = 11 characters added at begining, 9 characters missing at the end (DITHER:float:0) cd = override/welcome_1/LINE1.mnu = 11 characters added at begining, 7 characters missing at the end (FFD SHADE) od = override/welcome_1/PARTICLES.mnu = 11 characters added at begining, 9 characters missing at the end (glare p2:floa) od = override/welcome_2/BACKGROUND.mnu = 11 characters added at begining, 22 characters missing at the end (NIGHT WHIT) od = override/welcome_2/HDR.mnu = 23 characters added at begining (float:0.486059), 22 characters missing at the end (DIT) cd = override/welcome_2/LINE1.mnu = 23 characters added at begining (t:0.00392157), 22 characters missing at the end (FFD SHADER:int:1) od = override/welcome_2/PARTICLES.mnu = 24 characters added at begining (ER:int:1), 24 characters missing at the end (gl) od = textures/TGA/Noise.tga = 9 bytes added at begining (t:8.41834) ck = textures/month_bg/rgb/01.dds ck = textures/month_bg/rgb/02.dds ck = textures/month_bg/rgb/03.dds ck = textures/month_bg/rgb/04.dds ck = textures/month_bg/rgb/05.dds ck = textures/month_bg/rgb/07.dds ck = textures/month_bg/rgb/08.dds ck = textures/month_bg/rgb/09.dds ck = textures/month_bg/rgb/10.dds ck = textures/month_bg/rgb/11.dds ck = textures/month_bg/rgb/12.dds ck = particles/proc_iridescent.tga
The 2 characters at left means:
ck = custom, ok
cd = custom, damaged
od = official, damaged
Notes
*Not sure if you have the DDS and TGA files or if the toools you use can extract them, but incase you need them i can upload them
*You had the Noise.tga image damaged
*All the override/welcome_1/*****.mnu and override/welcome_2/*****.mnu are damaged because the "breakpoint" of the QRC structure happens before them, so all them are displaced some bytes, most of them are "od = official damaged", and there are a couple "cd = custom damaged"... as far i see that "cd" was modifyed unintentionally, because well... that "welcome_1" and "welcome_2" enviroments are a bit pointless, im not sure when are used exactly but i guess one of them is used inmediatly when you restore factory settings (or the first time you boot the PS3 after formating the hdd), and the other pretty much the same.. i dont think you was trying to customize that screens, right ?.. so... we can forget about them... in other words the MNU files used in the "welcome_1" and "welcome_2" enviroments doesnt needs to be "ported", right ?
So... this reduces the list of MNU files that needs to be "ported" to the first 15
Code:ck = LINE1.mnu <------------------------- this is the base, i think you should keep it official ck = override/day/LINE1.mnu <------------- main XMB ck = override/higure/LINE1.mnu <------------- main XMB ck = override/night/LINE1.mnu <------------- main XMB ck = override/yoake/LINE1.mnu <------------- main XMB ck = override/initial_setting/LINE1.mnu <--- what does this one ? ck = override/black/LINE1.mnu <----------- unknow usage ck = override/bright/LINE1.mnu <----------- unknow usage ck = override/coldboot1/LINE1.mnu ck = override/gameboot1/LINE1.mnu ck = override/gameboot2/BACKGROUND.mnu ck = override/gameboot3/LINE1.mnu ck = override/gameboot4/LINE1.mnu ck = override/gameboot5/LINE1.mnu ck = override/gameboot5/BACKGROUND.mnu
I think you might have trouble porting all the effects though as some of them was probably linked to the corruption.
Last edited:
sandungas
Developer
I made it already, i have the complete list of all the custom settings of that files, well aligned with "tabs" and it can be seen very well what he was doingIt would be cool , but I think you don't need to worry too my much about porting the complete pro qrc changes, figuring out what is happening with it is interesting though as it has some really nice effects.
Im not posting it yet because i want to slow down a bit the speed of the thread, i would like that luanteles agreed with what i said before posting it
Also i would like to suggest some changes in the settings he used, that worths another long post that i will wrote more calmly
sandungas
Developer
Btw, you are right, we dont know if the corrupted .MNU files was triggering "some magic"... but we can reproduce it
The other day we did learn we can break a MNU file (and it seems also the subfunction using it) by reducing his size to 0 bytes... and we can convert it in a valid "dummy" by reducing his size to 9 bytes
I was doing that by patching the QRC structure manually in a hexeditor, but i guess you can do the same in one of the available tools to create waves... just extract contents, open the .mnu file and delete some lines of it... then save the file and compile the .qrc
I guess the result should be the same
Aditionally ive seen some setting (located at the end of the .MNU file) that was cropped, some was still valid because the cropping only removed some decimals at the end, others became an invalid setting, and other where the last setting was removed entirelly
There is also the fact some of that damaged files starts with something different than the standard "#MNU_1.0" i guess we should consider the firmware is ignoring the whole content of that files with "garbage" at his first bytes... so to replicate that we should reduce his size to 0 to trigger the bug, but dunno, i hope the trick to trigger the bug is not going to be needed
*Btw, we are not going to "port" any of the damaged files (incase luan agrees with what i said before)... all them are related with the welcome_1 and welcome_2 enviroments, so is not worthy to work in that
Are a bit pointless and are damaged, so is better to forget about them
The other day we did learn we can break a MNU file (and it seems also the subfunction using it) by reducing his size to 0 bytes... and we can convert it in a valid "dummy" by reducing his size to 9 bytes
I was doing that by patching the QRC structure manually in a hexeditor, but i guess you can do the same in one of the available tools to create waves... just extract contents, open the .mnu file and delete some lines of it... then save the file and compile the .qrc
I guess the result should be the same
Aditionally ive seen some setting (located at the end of the .MNU file) that was cropped, some was still valid because the cropping only removed some decimals at the end, others became an invalid setting, and other where the last setting was removed entirelly
There is also the fact some of that damaged files starts with something different than the standard "#MNU_1.0" i guess we should consider the firmware is ignoring the whole content of that files with "garbage" at his first bytes... so to replicate that we should reduce his size to 0 to trigger the bug, but dunno, i hope the trick to trigger the bug is not going to be needed
*Btw, we are not going to "port" any of the damaged files (incase luan agrees with what i said before)... all them are related with the welcome_1 and welcome_2 enviroments, so is not worthy to work in that
Are a bit pointless and are damaged, so is better to forget about them
Last edited:
Great. Nice work.
Off topic: btw i think we can edit the length of individual values as long as keep the overall length the same and stay within the headers.. Have you noticed these values are not separated by nulls, but by new lines. So I think as long as we respect the over length of each mnu,, we could add a couple of digits to one value, and remove a few from the next value for example as long as we move the new lines to match.
Off topic: btw i think we can edit the length of individual values as long as keep the overall length the same and stay within the headers.. Have you noticed these values are not separated by nulls, but by new lines. So I think as long as we respect the over length of each mnu,, we could add a couple of digits to one value, and remove a few from the next value for example as long as we move the new lines to match.
