[PSP] libretro fails to load files
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
I know I should report this to the libretro/NP2kai repo, but the issues section is disabled there, so I'm posting it here. This problem probably only occurs with the NP2Kai core - I tried using the Commodore - C64 (Frodo) core and it actually loads without exiting to the XMB (a C64 game I downloaded doesn't work though).
Expected behavior
After selecting the NEC - PC-98 (Neko Project II Kai) core and loading a content, the game should start. Running the core without any content should result in a visible CLI interface.
Actual behavior
RetroArch exits to the XMB.
Steps to reproduce the bug
- Download the latest stable version of RetroArch from retroarch.com.
- Extract the downloaded file to
ms0://PSP/GAME. - Copy all required files for np2kai (BIOS files) to
ms0://PSP/RETROARCH/SYSTEM/np2kaiand game files (e.g. any of the first 5 Touhou games) toms0://PSP/RETROARCH/DOWNLOADS. - Run RetroArch from the XMB.
- Select the core (
NEC - PC-98 (Neko Project II Kai)). - Load the content.
You can also start the core without any content, the result will be the same.
Configuration information
- RetroArch: 1.16.0
- Hardware: PSP-E1004 (PSP Street, European version)
- OS: 6.61 PRO-C
- Compiler (as reported in "System Information" section of RetroArch): GCC (11.2.0) 32-bit
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached retroarch__1970_01_01__19_30_05.log and reproducing the failure with RetroArch 1.16.0 on the PSP-E1004 using the NEC - PC-98 (Neko Project II Kai) core. Compare loading content and starting the core without content; done means the core no longer exits to the XMB and presents its expected interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100