OPL (Open PS2 Loader)

PS2 Open PS2 Loader v1.1.0

Go to download
Overview Extra info Updates (4) Reviews (8) History Discussion
I really love these new additions, but just 1 thing to "monger about"! ;)

These config-updates would not be necessary, if instead of having "2 switches" to turn on a feature and select if 'per game' or 'global' settings are used, I think this would be a better way, IMO:
  • Instead of heaving "2 switches", IMO a more appropriate way would be having "1 switch" with 3 selections (Off/Per-game/Global). --> The example is just like XYZ-Page Off/Manual/On... ;)
  • The new config-variable XYZ-Source, could be left out and rather the "Enable XYZ"-Function gets a third selection! (0=Off, 1=per-game, 2=Global) --> The result of this would be, that (1.) old configs remain compatible without an update to the config, or apps(!), (2.) Per-game-settings would still be "active" on every game, where it was already "set"(!), 3. etc.

I'm just stating my opinion. I can certainly live with 2 switches as well! I am just bringing it up, due to the force of a config-update, where it wouldn't be needed (IMO).
 
There is only 1 switch with 2 selections currently (Global/PerGame)...

If it would not default to Global then there is no point in the feature (if it were to default to OFF or even PerGame).. if the user needs to go into the menu and make a selection of Global for each game then that defeats the whole purpose of Globals, they might as well just set per game settings at that point since they've already had to go into each games menu.

That's just my opinion anyway, currently everything can be done through the GUI the Batch Scripts aren't required.. it's just to make it easier for people that already have a large collection of Per Game CFGs they wish to still use by default, all newly made Per Game CFGs will of course not be affected by this.
 
An info for a friend that's using FHDB:

He's booting OPL from HDD. It's possible to set the IGR path in OPL settings??
 
Since @kozarovv brought up the XPARAM module here, this reminds me that I don't actually know where that module gets loaded.
I unpacked PS2LOGO (extract the data in .data, which is actually a .zip file), to get the uncompressed cex.bin file that loads at 0x00100000. It can be seen loading rom0:XPARAM, which could mean that loading PS2LOGO may be beneficial for game compatibility on the slim PS2s...
 
I'm using OPNPS2LD r1406 right now and it just freezes when I push the power button while it's displaying the HDD list.

Is that an expected behavior? It's forbidden to push the power button while on the HDD list?
 
Last edited:
New 1436 version is out.

Changelog:
  • Optimise gfx/new logo
  • Multiple default/overlay/attribute image texture support for internal theme
  • Reset colors button in Display Settings
  • New English/Polish fonts
  • Update internal theme to Korium by Berion
  • Font scaling fix
  • Reorganise Menu options
  • Updated About page
  • Modes fix
  • 4-bit/8-bit/1024x1024 PNG support
  • Info Page attribute text keys now translatable
More info is in detailed changelog.

Grab it from attachment or currently from here:
https://www.psx-place.com/resources/automated-daily-build-system-for-opl-wle-fceumm-ps2.702/.

If you want previous Plasma theme, you can get it from here:
https://www.psx-place.com/threads/gui-overhaul-part-2.26928/page-4#post-224850.
 

Attachments

Last edited:
Hi guys . I hope I could reach here someone into the developing team of OPL. I am a noob here, but I posted previously asking about some 3 interesting ideas to add to it, so I was wondering if that would be possible.
-includes adding an Optical dirve reading option (with all the OPL options included)
-Related to the first one, the chance to add a 1 buttom on / off widescreen check per game
-And finally, with a simple tool for some frames of delay, a chance to make the lightgun games compatible with LED tvs , again; as the NES modding scene was able to fulfill.

I hope I am not broking any forum rule here, but just in order to not repeat everything again, please let me paste the link of the Thread I started here. If you guys are from the developing team, please give a chance to read about this ideas :)

https://www.psx-place.com/threads/some-really-nice-apps-ideas-for-opl.28027/
 
I've notice strange thing with separate bars on 1440:
New-issue-OPL-1440.png

They seems to fall in green like some kind of a problem with graphic.

Everything is fine on OPL 1436:
New-issue-OPL-1436.png


BTW: Sorry for low quality photos.
BTW 2: Problem with "printing screen" seems to be gone in 1440.
 
Yes, i noticed this also, but i thought the design would be like this when i saw that nobody
was saying anything, and i usually use the plasma background, although it seemed
odd because those lines appear as corrupt.
I think it happens with any resolution you choose.
I hope they look at it and fix it.

Best regards.
 
@El_Patas I have also checked OPL (currently 1440) from automated daily build system:
https://www.psx-place.com/resources/automated-daily-build-system-for-opl-wle-fceumm-ps2.702/.

And... it seems like everything is fine from this build system.
I mean I do not have got any graphical glitches in OPL menu.

So I downloaded once again beta revisions from github,
but unfortunately the problems with graphical glitches still exist.

To sum up.
Everything is fine with OPL 1440 from automated daily build system.
Graphical glitches exist only in OPL 1440 beta from github repository.
 
I not changed nothing in my setup for compile the OPL, and in the previous OPL revisions
the problem do not happens.
I don't know what can happen, maybe the automated daily build system compiles
in a different way the latest commit changes in the repository.

Best regards.
 
@sp193, do you remember why does the word "dirty" appear next to the version when the OPL is compiled?
I remember that it did not always exist, but i do not know why it appears and for what,
and if it should be removed to publish a new version.

Best regards.
 
  • Like
Reactions: TnA
El_Patas said:
@sp193, do you remember why does the word "dirty" appear next to the version when the OPL is compiled?
I remember that it did not always exist, but i do not know why it appears and for what,
and if it should be removed to publish a new version.

Best regards.
Click to expand...
It will appear when either:
1. the working directory is not clean (git diff --quiet will give a result and return a non-zero code in this case)
2. the .git directory does not exist
 
I use ubuntu linux mint on virtual machine with windows 7 for compile the OPL.

And i use 'make clean' always in the opl folder files on my virtual ubuntu, and when i compile it next time, always appear.
Mmm, i don't know too much about linux, i don't know how i could look if the .git directory exists.

Anyway this 'dirty' is nothing important no?

Best regards.
 
You must log in or register to reply here.

Similar threads

Back
Top