PS2 FMCB/FHDB v1.9 series release thread

Thanks, but I prefer to not work on PlayStation 2 related projects at the moment. I've got no energy nor time to spare.
There's no need to credit me for this project, since it wasn't mine.

Just sharing for knowledge: I changed how the logo was stored and loaded to save space. It's possibly a 16-bit bitmap, but with a custom header and the pixels were already flipped into the right orientation for direct transfer into GS memory.
It didn't seem to help save on storage space as much as I hoped, but that was done first before I found out anyway. I guessed it was because the logo portion of the logo (which was originally a full-screen graphic) wasn't really compressible, so cutting out the padding around didn't result in much savings.
 
No need to keep working on that, just recompile it with the new splash. Also, the old splash from 1.8 was already cropped and was not full screen.
And the project is maintained by you, so you deserve credits as well.
 
I cannot say which is better because it point to Discord which I really don't like to log-in (I hate 2FA). ;)

Recompilation doesn't mean everything is ok. Always and every binary must be... tested before the release. At least this is how things looks in old days, because in currently, often "new generation devs" realising stuff "as is" and doesn't care about quality, which also often is just low and full of unexpected bugs. So QA tests means time consumption and time consumption means time wasted if someone have much important priorities in real life (family, job, other hobbies etc.).
 
Recompilation of the same source compiled using the same SDK version under the same environment should not give issues @Berion
If something changed on that, then it should be tested, but even on that case scenario, is very unlikely something will fail if no source code was changed.
 
In theory, in perfect world, for sure, but i.e compilers have their own bugs and issues which are impossible to predict/known all. So even if every part of the operating system is the same, and every part of the SDK and source code is the same, plus image have the same dimensions and is in the same file format, then in theory we should get "safe binary". But we are living in strange none deterministic world, where even... neutrino can mess some bad luck electron causing disaster in our binary. I'm acolyte of QA-necessary philosophy no matter what. :D
 
One undocumented difference between the v1.953 and v1.96 was that FMCB was no longer packed with the packer that does multi-layering scrambling. Maybe this triggered some patching by modchips.
For those who actually have an "incompatible" modchip, would you want to try this: https://www.sendspace.com/file/0x7slj

There should be no difference in functionality between the previous v1.966 release and this. Unfortunately, I had to modify the linkfile because FMCB could not be compiled with my SDK from December 7th 2019, for some reason.
 
sp193 said:
One undocumented difference between the v1.953 and v1.96 was that FMCB was no longer packed with the packer that does multi-layering scrambling. Maybe this triggered some patching by modchips.
For those who actually have an "incompatible" modchip, would you want to try this: https://www.sendspace.com/file/0x7slj

There should be no difference in functionality between the previous v1.966 release and this. Unfortunately, I had to modify the linkfile because FMCB could not be compiled with my SDK from December 7th 2019, for some reason.
Click to expand...

hi
FMCB v1.966 (2019/04/13)
installation is successful
but when I enter LAUNCHELF and FREE MCBOOT CONGIGURATOR I get a black screen.
 
jolek said:
Any chance for more info?
Console version (SCPH-XXXXX)?
modchip brand?
...
Click to expand...
both MATRIX 1.93
PS2 SLIM 77006
PS2 FAT 50001
EDIT:
Update 2018/12/08: v0.985 (FMCB v1.965)
version 1.95 works perfectly

what I liked most about version 1.96 was the options
restart system
and
shutdown system
 
So to sum up.
You have tested FMCB 1.966 from 2020/07/18 and from 2019/04/13
on SCPH-77006\SCPH-50001 with Matrix Infinity 1.93.
When you enter wLaunchELF or Free MCBoot Configurator you are getting black screen.

However FMCB v1.965 from 2018/12/08 is working fine.
 
jolek said:
So to sum up.
You have tested FMCB 1.966 from 2020/07/18 and from 2019/04/13
on SCPH-77006\SCPH-50001 with Matrix Infinity 1.93.
When you enter wLaunchELF or Free MCBoot Configurator you are getting black screen.

However FMCB v1.965 from 2018/12/08 is working fine.
Click to expand...

exact,
[181105]FMCB-1965-bin
this works perfectly

@jolek k
I apologize the tested version was [181105]FMCB-1965-bin
 
Last edited:
Zwei said:
what I liked most about version 1.96 was the options
restart system
and
shutdown system
Click to expand...

If you mainly use your Ps2 for playing games with OPL, I suggest you to set it as Autolaunch in E1 hotkeys on FMCB_Configurator (for having the Ps2 to directly boot into OPL).

OPL has the option to shutdown the Ps2.
As for restarting the console you can list the reboot.elf as an App: https://www.psx-place.com/resources/reboot-reboot-elf.348/
 
HWNJ said:
https://www.psx-place.com/resources/power-off-ps2.658/
Click to expand...

now it's the way I want it

Tranks
@Peppe90
@HWNJ
@jolek

OB1QP.jpg
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top