Skip to content
New issue

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

[PS2] PicoDrive core doesn’t work since RetroArch 1.14.0 #15800

Closed
ghost opened this issue Oct 15, 2023 · 3 comments
Closed

[PS2] PicoDrive core doesn’t work since RetroArch 1.14.0 #15800

ghost opened this issue Oct 15, 2023 · 3 comments

Comments

@ghost
Copy link

ghost commented Oct 15, 2023

Description

Hello. Since version 1.14.0 PicoDrive core shows version as 1.99-unknown and after launching any game just “crash” to PS2 browser.

Expected behavior

Games should run properly as they did with version 1.13.0 and below.

Actual behavior

Games "crash" to PS2 browser.

Steps to reproduce the bug

  1. Launch PicoDrive ELF
  2. Launch any MegaDrive/Genesis game

Bisect Results

Since retroarch 1.14.0.

Version/Commit

1.14.0, 1.15.0, 1.16.0

Environment information

PlayStation 2 90008. Also tested on PCSX2 emulator.

9830ecda5352be9f74d9534babfdb39a09b460ed

@zoltanvb
Copy link
Contributor

I have found the reason for the "unknown" version issue, and will submit a pull request, but that is probably less important.

But I can not reproduce the crash with current versions on PCSX2. I have experienced strange things when config file was shared between versions, but in a fresh install (when there is only raboot.elf, cores/ and info/ in the respective directory), it has worked always.

Maybe it is still content related, can you name a few ROMs that exhibit the fault?

@ghost ghost closed this as completed Oct 22, 2023
@ghost ghost reopened this Oct 22, 2023
@zoltanvb
Copy link
Contributor

Thanks for the check. The sound fix is awaiting merge: #15827

@ghost
Copy link
Author

ghost commented Oct 24, 2023

The problem is missing "retroarch-salamander.cfg" file and you need to disable "Always Reload Core on Run Content" in core settings.
(Sorry I accidentally delete my previous comment about this solution)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant