OPL (Open PS2 Loader)

PS2 Open PS2 Loader v1.1.0

IGR has coloured debug screens as well. Since the colour is drawn as the background, it sometimes appears as a border around the (last) image drawn by the game.

Anyway with the build you linked IGR perfectly works with all games I tried from SMB!!

Every game but Ultimate Pro Pinball … I can IGR-PowerOff from this game. But performing the normal IGR It ends in a BSOD (I can see the colors on the border: Yellow, blu, green, then BSOD).
 

I don't think it's really possible to make it exactly the same. SMB is quite heavy.
At least because our IOP is like a PC from 1989 lol.

Indeed I can see it's a matter of bandwidth: in the main menù (where's the CG girls that comes and goes) the music has problems, but entering i.e. the option menu (that only have some writes) the music becomes perfect.

It's not a big problem. Btw you think there's a way to solve that??
 
Made some tests with r1277 from SMB, with Ps2 slim (75004)...

Can you also test all devices with upcoming OPL 1282 (after pull request will be merged) or with new test version?
Not just only SMB.

Here's the ELF that I used, in case something weird is happening with the ps2sdk: https://www.sendspace.com/file/rnppvs

I've tried Shadow Man: 2econd Coming (SLES_504.46) with this build, but I still cannot boot this game through HDD.
I'm getting BSOD after debug colors.
Game should works without any compatibility modes through USB & SMB.

With Ultimate Pro Pinball (SLES_535.08) through HDD I'm still getting BSOD after debug colors.
Game should work without any compatibility modes through USB & SMB.
IGR still is not working with game (BSOD after triggering IGR).

However Ridge Racer V (SCES_500.00) at least works through USB & HDD.
Through SMB it needs in my config mode 2
or every 10-15 sec I'm getting short stuttering in intro or in menu.
After triggering IGR I'm getting BSOD.
Previously IGR was not working at all (I haven't even got debug colors).

Tested with OPL 1281 (OPNPS2LD-b2925a9.ELF).

BTW IGR is not working with Tekken 5 SCES_532.02.
 
Last edited:
I have adjusted the padhook to support SDK release <1.6.0, so IGR should now work on early games.
Ooohohooo! That's great!
It might work on quite some more games now and might have even fixed an incompatibility-issue in some games (who knows).

I have rolled back the change that replaces the built-in SPU reset code with CLEARSPU as the old problem with CLEARSPU has come back to bug me. Now I understand what's happening: CLEARSPU will register an interrupt handler for the SPU, which will jump to a another callback. However, the callback is never set, so it jumps to 0x00000000.
I don't know what this means. But this weird quirk seems to be around in CLEARSPU in all ROMs. :eek:
It might have been a feature leftover from debugging or is incomplete. Perhaps under normal circumstances, it will never be a problem because the SPU2 is not doing anything.
The 'jump to... but it's never been registered' sounds like some 'dangling pointer', with the difference of not having a valid 'link' ([de]reference/etc.) to begin with, because there is nothing 'set up' where it is linking to, right from the beginning.

It's a feature of FMCB, since v1.90.
Oh! I didn't knew that!

It does not seem to clear the digital effect settings.
Well... If that is the case, then... it probably should or not?

I wonder what would happen, with switching the TosLink on or off and if there is a difference in sound and etc. for users of either output-method.

The new patch should already take care of all games with the same mistake as in Half Life.
True, but since this abnormal state is seemingly invoked my the hacked OSDSYS and it also seems to be only happening when the user is starting ELFs instead of discs, it should be fixed where it is caused, IMO.

Like I said, this is something which would probably fix the coldboot-issues for these games on old rev's as well + AFAIR there were some Homebrew-Apps which had issues as well. Flashback? Dave Gnukem? I can't remember, sry.

It wasn't supported because there was no code for such early versions of libpad.
Does it support REALLY old versions of it now? That addition might fix a lot of games and is worth to be mentioned in the IGR-Bughunt-Thread, IMO.
 
Last edited:
This may be a silly question, but may someone direct me to info on the adp files in the misc folder of the repo? I recognize the file structure and would like to know what I may use to edit/create/view a file of this format.

EDIT: DOH. I went to apps for opl and found the converter. Nevermind lol.

Double Edit: Oh, OH... OOOOHHHHHHH!
 
True, but since this abnormal state is seemingly invoked my the hacked OSDSYS and it also seems to be only happening when the user is starting ELFs instead of discs, it should be fixed where it is caused, IMO.

Most probably it's related to the OSDSYS itself. It would probably happens even if you boot to the official OSDSYS, than boot Half Life without showing the Ps2 Logo.
But it's impossible to reproduce (maybe with a chipped Ps2 that doesn't hack the OSDSYS in any way?).
 
I think the cause lies in the difference between how it starts an ELF and how it starts a disc...

In any case of a normal disc-boot, you get some kind of 'stage-refresh' (kind of) i.e. due to re-init... (PS1CDs go through PS1DRV, PS2-Discs through PS2Logo, Video-DVDs atleast start the DVD-Player (where there might be something invoked [UDNL?] to change something).

Sooo... I think there is something (possibly SPU2-De-Init after OSDSYS had been started) wrong, before an ELF is started, but while/after the OSDSYS is/gets terminated/exited.
 
I think the cause lies in the difference between how it starts an ELF and how it starts a disc...

In any case of a normal disc-boot, you get some kind of 'stage-refresh' (kind of) i.e. due to re-init... (PS1CDs go through PS1DRV, PS2-Discs through PS2Logo, Video-DVDs atleast start the DVD-Player (where there might be something invoked [UDNL?] to change something).

Sooo... I think there is something (possibly SPU2-De-Init after OSDSYS had been started) wrong, before an ELF is started, but while/after the OSDSYS is/gets terminated/exited.

But with the latest builds, the problem is already gone. I tested it:

Half Life Now works fine, even booting the OSDSYS (Ps2 Logo disabled) :encouragement: IGR works fine with this game.
 
But with the latest builds, the problem is already gone. I tested it:

Right... But it is not fixed, where it is caused!
FMCB/FHDB seems to have a problem and not OPL itself...

Maybe another separate thread just for 'coldboot-issues' (or actually vice versa 'OSDSYS-boot-issues'), might be appropriate.
 
Right... But it is not fixed, where it is caused!
FMCB/FHDB seems to have a problem and not OPL itself...

Maybe another separate thread just for 'coldboot-issues' (or actually vice versa 'OSDSYS-boot-issues'), might be appropriate.

I too had this idea. But I thought sp193 solved this problem root.
 
Well, technically the SPU-Deinit might be the proper fix, but the placement of it within the app, instead of the thing which loads the app (and other apps) is what I question, because it seems weird.

Placing that in the code which loads apps/ELFs (from OSDSYS), would just make more sense IMO, because it is meant to have the same compatibility!

In fact, some people thought we could just remove the button-launch and auto-launch, 'to spare boot-time' and handle it all via the OSDSYS... As we can see, it was good to keep it...
 
Well, technically the SPU-Deinit might be the proper fix, but the placement of it within the app, instead of the thing which loads the app (and other apps) is what I question, because it seems weird.

Placing that in the code which loads apps/ELFs (from OSDSYS), would just make more sense IMO, because it is meant to have the same compatibility!

Well, it sounds good to me... But I don't have the knowledge to judge :D
 
The sound bug in Half Life should not be a problem with this. I noticed that setting the digital effects volume (EVOLL & EVOLR) of SPU2 core 1 to 0 would mute the buzzing. The same thing happened when digital sound effects were disabled.

Clearing the SPU2 digital effects with libsd seemed to work, so I guess this small patch module should fix all games like that.

As for why it was ever a problem, I think it's caused by their gbxcd.irx module doing sceSdInit() with the hot init option. That option also causes digital effects to be enabled.
I didn't try proving whether the game uses digital sound effects or not, but this can allow the old settings from previously-run software to be used with the game.

I'm curious to see if that change make some differences on games with audio problems (like DoA2, Gungrave, Klonoa 2, etc...).
 
Placing the fix (IF the SPU-Clearing and/or Deinit is the proper fix) into FMCB/FHDB would then likely also fix it for older OPL-Versions as well...

The thing is just... There is a different behavior of Button-launch and launching ELFs from OSDSYS, to begin with! The normal user should not need to care about that kind of stuff!
 
Placing the fix (IF the SPU-Clearing and/or Deinit is the proper fix) into FMCB/FHDB would then likely also fix it for older OPL-Versions as well...

The thing is just... There is a different behavior of Button-launch and launching ELFs from OSDSYS, to begin with! The normal user should not need to care about that kind of stuff!

Yes, It seems great. I hope it is doable too :D
 
Well, it entirely depends on 'if' this is the real cause and proper fix...

If it really is a de-Init/re-init-issue with specific game-libs being unable to initialize it properly again - after it had been loaded - , then this should be feasible for the hacked OSDSYS...
 
I am btw. also interested, if this does fix the issue of sound in some games but I suppose as long as you started them without entering the OSDSYS, it would not make a difference!

But if it behaves differently, that's certainly interesting!
 
I'll test it for sure. Btw my latest tests were with OPNPS2LD-b2925a9 (r1281 as you said).
Made some tests with r1277 from SMB, with Ps2 slim (75004)...

I'm not sure if I understand you correctly?!

Anyway.

If you made a test with OPNPS2LD-b2925a9 (r1281) everything should be the same also with upcoming OPL 1282,
because all the changes should be the same.
 

Similar threads

Back
Top