PS2 OPL freeze on black screen when launching a title

N

Nadoriadoga

Member
So I updated OPL to 1.2.0.6-1996 (from Grimdoomer's github) so I can use an exFAT formatted hdd. I got seemingly everything set up. Only points of notice being that there are two game lists named "hdd games", one with all my hdd games and the other empty. Apart from this, whenever I press X on a game, the screen goes black and stays that way.
Any helpful ideas?

Update: I turned on debug color, and now it freezes on a pink/magenta screen
 
So I just a game started, but I had to go through uLaunchELF to boot OPL through USB in order for OPL to launch a title without freezing. Doing the same from my FMCB mem card, it freezes still. Setting the boot directory for OPL on the browse screen through FMCB configurator to launch through USB only restarts PS2 when attempting launch OPL
 
I'm not quite sure I understand what you mean. The games are on the HDD and start fine when launched using OPL started from mass directory, just not when playing from fmcb. The game addresses and the names are the same for both scenarios. Only difference was how OPL was booted.
If you feel you know the issue at hand, please do share, but I assume I'll just have to wait until this is resolved in a future build of OPL, seeing as the one I'm using is only a beta.
Thanks for all you've done so far though :)
 
Try the following:

1.-Make a backup of your USB device.

2.-Download the free software "MiniTool Partition Wizard" edition "Home User Partition Wizard Free" from the following link:

https://www.partitionwizard.com/

3.-Once installed, open it and identify your USB device, in my case it is "disk3".

4.-Right click and select delete partition.

partitionwizard1.png


5.-On the left side select "Apply".

partitionwizard2.png


6.-Right click again on your device and create a new partition by choosing "Create".

partitionwizard3.png


7.-Choose the options shown in the image and click accept.

partitionwizard4.png


8.-On the left side choose "Apply" when the process is finished, close the program.

partitionwizard5.png


9.-Place your backup back on the device and connect it to your PS2.

10.Check that your issue has been resolved.
 
I followed this thoroughly, but now my mass content doesn't even show up in either the FMCB configurator or wLaunchELF. You sure it's supposed to be exFAT? seems to be the cause of the problem as FAT32 is working...
 
fat32 has always worked, that's why I recommended changing the OPL version at first.
Now let me see if I understand you.
Did you leave your USB device on fat32 with the program?
or did you do the following
Did you choose fat32 in the program and then use the Windows tool to format it exfat?
I put "exfat" in the options because that was what you wanted, right?
 
My harddrive is formatted to exFAT, which is what I wanted. Now it seems that OPL only works when started through USB. My games are still on HDD.
Right now, the only issues I have that might have solutions are that when putting the OSDSYS OPL directory through mass, console restarts. And when playing some games, it loads for a long time and crashes.
Edit: Bully crashed once. Subsequent attempts did lead to game starting after waiting for 2-3 minutes of loading.
 
Last edited:
So did the previous procedure help solve your initial problem?
Now you have other problems, make sure to use FMCB to the most updated version.
 
My initial problem was already resolved. The procedure unfortunately did not help, but thanks for trying and making it easy to follow.
I have FMCB 1.966, which is the latest version from what I gather. I'll try updating ulaunchELF and see if that changes anything. Though right now I'll try just waiting for grimdoomer to update OPL and hope I won't need a nested USB stick.
 
Right!
So initial problem: starting a game through OPL 1.2.0.6 beta build would freeze on black screen (or magenta if debug colors turned on).

Solution: put OPL on mass storage and open it using uLE/wLE and then game would start.
 
But your problem was that you couldn't open games with OPL using FMCB. so the problem has not gone away.
Now let me ask you, were you using an internal hard drive?
My fault for not asking you before.
 
I am currently satisfied my temporary solution and have other things to focus on. And seeing as I don't want a USB nested I to the console, as I want the USB slots available for a Bluetooth adapter to use a ds4 using pademu, alongside other accessories, I will be keeping an eye on updates and hope this is resolved with an update later on.
Thank you so much for all of your help though! :)
 
You must log in or register to reply here.

Similar threads

Back
Top