PS2 mini-OPL v1.0

Krah said:
Can you try one last thing for me out of curiosity? In game settings there is an option to have a custom game id.. afaik this option is no longer useful but can you try change it.. to anything.. I imagine it will white screen which could be the cause of jsnepos problems.

I don't think my version will be used anyway, it seems like akuhak is leaning towards a full init but I'm still curious if that was the problem he had, as white screen in syshook.c means the elf failed to load and all I can gather from that is the file name is wrong.. which leads me to that setting.
Click to expand...
I tried setting the game id to all 1s and the game booted & played just as before. Made sure to save it was too.
I'm starting to think jsnepos is having maybe a user error or setting not being set right. Maybe KELF not loading right?

Personally, I prefer your version as it's like the older MiniOPL & just as fast. It's just that I'll like to have a black screen or PS2Logo before games start vs debug color. For the games that don't work on older MiniOPL, I'll most likely use this var.
akuhak said:
@vash32 @Berion new version is up. Now with AutoRefresh forced on. Hope this will be enough.
Click to expand...
Just tested it out and somehow this time the game list was not updated but AutoRefresh was on.
However, one game got updated to the game list. It auto-started for me on the next boot. (Game tested was Ico)
Krah said:
I don't think you can auto refresh hdd, think it's needs to be done manually by the user hence
https://github.com/ps2homebrew/Open-PS2-Loader/blob/master/src/hddsupport.c#L264
Click to expand...
Yep, My working setup has this problem but once the list is updated it works. Just an other thing that makes your nicer in my eyes.
 
I know I said I wouldn't do anything further but it irritates me knowing this should work.
@vash32 ps2logo should be fine on this one..provided its enabled in cfg on hdd
 

Attachments

Krah said:
@vash32 ps2logo should be fine on this one..provided its enabled in cfg on hdd
Click to expand...
I just tested it and this time it boots up and shows debug colors, does the PS2logo then starts the game.:cool:
I think the OPL Launcher KELF may be doing the debug colors part at it looks to be doing it for both var. & it's off in the config.
 
Report from battlefield:

KRAH OPL: Ico works with default settings but logo off (didn't try with logo on), Grandia stuck o white screen. With my config, black screen on both and HDD led is on fire.

AKUHAK OPL: Booting to OPL and staying there on both configs.
 

Attachments

spammed your inbox with some test versions, found some issues with cfgs hopefully all is well now. akuhaks version does boot games but you need to refresh the games list after installing the new game because its using the list to boot said game.
 
hello how I do for installing one game on BBnavigator Install the game with this __.gamename.
and this PP.gamename ?with Boot Kelf ? there is someone can explain how i read the github of OPL launcher but
I can't figure out how to do it
 
@Fanhais
  • Games that can be launched from HDD OSD or BBN must have partition name prefix "PP.". Any other will be ignored (will not showed in menu).
  • For such game, You must insert signed OPL-Launcher (detailed how to is in readme for OPL-Launcher).
  • Launching OPL-Launcher from games PP partition, will launch "hdd0:/__common/OPL/OPNPS2LD.ELF" (it works only with v1.1.0 and newer) which seeking two things: "hdd0:/__common/OPL/conf_hdd.cfg" (which tells him where is partition with resources) and game config (to know with what options use for this specific game).
 
Berion said:
@Fanhais
  • Games that can be launched from HDD OSD or BBN must have partition name prefix "PP.". Any other will be ignored (will not showed in menu).
  • For such game, You must insert signed OPL-Launcher (detailed how to is in readme for OPL-Launcher).
  • Launching OPL-Launcher from games PP partition, will launch "hdd0:/__common/OPL/OPNPS2LD.ELF" (it works only with v1.1.0 and newer) which seeking two things: "hdd0:/__common/OPL/conf_hdd.cfg" (which tells him where is partition with resources) and game config (to know with what options use for this specific game).
Click to expand...
I THINK u are wrong with the paths


AFAIR, OPL Launcher searchs the HDD partition config file..

Then it mounts that partition and launches OPL.

It follows the same logic than OPL custom partition loader.

If partition name starts with + search on hdd0:/$PARTITION/OPNPS2LD.ELF else hdd0:/$PARTITION/OPL/OPNPS2LD.ELF
 
my files structure are this way on My BBN
__,SCES-50760..ICO (iso)

other system partitions LOL

PP.SCES-50760..ICO (paste res)
what i'don't understand is on system.cnf i think
BOOT2 = pfs:/EXECUTE.KELF .... this path how i can say where OPL lancher boot the game?

on HDDOSD is easy boots well when I tried do this on BBN lol the game don't boot and go back to BBN LOL



​
 
@El_isra Perhaps and probably You have right. But this doesn't matter for end user as everything else is the same (conf_hdd which telling the app where is OPL resource partition and stuff needed to written into APA).

@Fanhais Every partition on APA scheme contains two area: Attribute Area and FileSystem Area. OPL-Launcher must be written into Attributes, not FS area with PFS because this one is occupied by disc image... Read the readme for OPL-Launcher, there is step by step guide... Your BOOT2 is wrong...
 
Berion said:
@El_isra Perhaps and probably You have right. But this doesn't matter for end user as everything else is the same (conf_hdd which telling the app where is OPL resource partition and stuff needed to written into APA).

@Fanhais Every partition on APA scheme contains two area: Attribute Area and FileSystem Area. OPL-Launcher must be written into Attributes, not FS area with PFS because this one is occupied by disc image... Read the readme for OPL-Launcher, there is step by step guide... Your BOOT2 is wrong...
Click to expand...
The end user must know that because the path where OPL launcher looks for OPL can change depending on the prefix
 
Looks like the latest OPL-Launcher is broken. Can somebody test it? https://github.com/ps2homebrew/OPL-Launcher/releases/tag/latest

But if we are talking about the stable release.
@Berion @El_isra @Fanhais
OPL-Launcher supports 2 ways of setups: classic, when OPL-Launcher is injected into attributes area, and PSX DVR/BBnav setup, when PP. is pfs partition with files inside

so minimal setup if you want to stick with +OPL partition:
Code: 
+OPL:/OPNPS2LD.ELF
place here latest OPL
a) inject OPL-Launcher into PP. partition with HDL game installed. Inject
Code: 
BOOT2 = PATINFO
and OPL-Launcher with hdl-dump.
b) rename PP. partition into __. partition. Create PP. partition of type pfs (with wLe for example) with the same name as __. partition. Place OPL-Launcher into the root of PP. partition with name EXECUTE.KELF. Inject
Code: 
BOOT2 = pfs:/EXECUTE.KELF
and OPL-Launcher with hdl-dump.

Scenario "b" seems more complicated but it is necessary for BBNav and PSX DESR gen1 users. For HDD OSD users you can choose either scenario a or scenario b.
 
Last edited:
akuhak said:
EXECUTE.KELF. Inject
Click to expand...
ok need put this file on PP. through hdl dump or copy paste with this name to folder and in the end on the name ,inject ?
akuhak said:
BOOT2 = pfs:/EXECUTE.KELF
Click to expand...
my doubt what i write in this file this ?
BOOT2 = pfs:/EXECUTE.KELF
or this
BOOT2 = pfs:/__.nameofgame/EXECUTE.KELF
because when i did this the game don't launch go back to BBN
so I came here to ask some tips XD
 
@akuhak, from my early tests with stable release I remember hddGetHDLGameInfo returned with no error even if partition has PFS and no game. That's why @Nameless32 experienced white screen issue when OPL-Launcher was ran from a PFS partition with no game in it.

So, I guess it's necessary to make a revision of OPL-Launcher for the case of BBN. First, if partition has PFS, we need to check if corresponding __ partition exists to launch OPL passing __ partition information as argument, otherwise OPL is launched with no arguments to avoid white screen.
 
Fanhais said:
ok need put this file on PP. through hdl dump or copy paste with this name to folder and in the end on the name ,inject ?

my doubt what i write in this file this ?
BOOT2 = pfs:/EXECUTE.KELF
or this
BOOT2 = pfs:/__.nameofgame/EXECUTE.KELF
because when i did this the game don't launch go back to BBN
so I came here to ask some tips XD
Click to expand...

Are you using stable release or latest development build? With stable release you'll likely get a white screen with EXECUTE.KELF and with latest development build you should get OPL GUI.
 
alexparrado said:
Are you using stable release or latest development build? With stable release you'll likely get a white screen with EXECUTE.KELF and with latest development build you should get OPL GUI.
Click to expand...
I'm using what HDL-Batch-installer has i think is the latest development build and i use this app and hdl dump for modify_header in PP
What I did was
install the game
__.game
and
PP.game with execute.elf injected and copied on the folder root
and when try boot the game the behavior is back to PSBBN so i think i'm doing something wrong
on system.cnf on the path for sure because i think but can i be wrong i need to tell to PP.game
to boot __.game on my though PP.game is the arguments to boot __.game but i can be wrong
 
You must log in or register to reply here.

Similar threads

Back
Top