Retroarch Desktop lrps2 core won't load! (win7)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Hello there,
I am trying to get the core to work I followed the instructions here!
I downloaded pcsx2 portable installed it copied everything over except the .exes I created the bios, cheats, cheats_ws, & memcards folders I placed all my multiple bios in the bios folder, They are matched up according to how the guide says they should be. The path is correct retroarch/system/pcsx2/bios all lowercase.
I've tried opening it with d3d11 as it says all I get in retroarch is failed to open libretro core.
The core is there in cores folder so idk why this is happening. I've tried using the functions in online updater update core info files, update assets, update databases, & update overlays & I still keep getting this error. I am not sure what to do at this point.
Expected behavior
No response
Steps to reproduce the bug
Load content
select ps2 game
select lprs2 core
Version/Commit
1.20.0
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Windows 7
Affected Cores
LPRS2
Environment information
No response
Relevant log output
[ERROR] Failed to open libretrocore "C:\RetroArch\cores\pcsx2_libretro.dll"
[ERROR] Error(s): The specified proceducre could not be found
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 reproducing the failure when loading a PS2 game with the pcsx2 core on Windows 7, then inspect how RetroArch opens cores/pcsx2_libretro.dll. Use the reported error, “The specified procedure could not be found,” as the initial investigation point; done means the core loads successfully instead of producing that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100