We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's not possible to start POPSLoader from the apps menu in OPL (1.2.0 beta 2165), it just got stuck at the "Loading config" screen forever.
The POPSLoader ELF is stored on the root of a USB drive. And I have the follow line set into "mc0:/OPL/conf_apps.cfg":
POPSLoader (PS1 games)=mass:/POPSLOADER.ELF
The app is seen in OPL, even the correct size is shown, but starting it results in hanging at "Loading config".
POPSLoader does work if started from FMCB directly.
SCPH-50004
OPL 1.2.0 beta 2165
USB
Not a game, but a application, started from the apps menu. This one: https://www.psx-place.com/resources/popsloader.1396/
Expected behavior is that the application just start, like if it was started directly from FMCB.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Checks
Describe the issue
It's not possible to start POPSLoader from the apps menu in OPL (1.2.0 beta 2165), it just got stuck at the "Loading config" screen forever.
The POPSLoader ELF is stored on the root of a USB drive. And I have the follow line set into "mc0:/OPL/conf_apps.cfg":
The app is seen in OPL, even the correct size is shown, but starting it results in hanging at "Loading config".
POPSLoader does work if started from FMCB directly.
Console model
SCPH-50004
OPL version / revision
OPL 1.2.0 beta 2165
In which device(s) have you experienced this issue?
USB
Context and extra information
Not a game, but a application, started from the apps menu. This one: https://www.psx-place.com/resources/popsloader.1396/
Expected behavior is that the application just start, like if it was started directly from FMCB.
The text was updated successfully, but these errors were encountered: