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

One receiver will cause memcard Pro errors, and the other will not #2

Open
SoukinOKATU opened this issue Oct 20, 2023 · 3 comments
Open

Comments

@SoukinOKATU
Copy link

The same receiver(RetroScaler BlueRetro Wireless Game Controllers Converter Adapter For PS1 PS2 ), with a transparent shell, can cause memcard pro read and write errors, while a black shell will not
Unable to read/write SAVE files in memcard pro, such as'Akumajou Dracula X ',It will display a bad memory card(Japanese:不良)or 'no card',Occasionally, SAVE files are displayed, but there may be read errors.
Strangely, with another black shell receiver (with the same model and firmware version), everything returned to normal

@egparadigm
Copy link

I think I have the same issue. I already had a Memcard Pro, a brilliant product that makes saving games a breeze. I bought a BlueRetro adapter for my PS1 after being really impressed with it on my N64 (which includes a similar save function to MCP). I immediately had problems with my PS1 (xStation) saying the card was not formatted. After a bunch of testing, it appears this will happen if both MCP and Blue Retro are plugged into port 1. I'd be happy to have them in different ports, but unfortunately it appears some (if not all) PS1 games expect the memory card to be in port 1 and will not recognise controllers in port 2 (except multiplayer).
This seriously sucks. Is there a possibility this could be fixed?
I thought it could be a power issue, so I tried adding power with the USB micro but same problem.

@RetroScaler
Copy link
Owner

RetroScaler commented Feb 27, 2025 via email

@egparadigm
Copy link

I contacted 8bitmods who pointed me to the latest beta for BlueRetro which fixes this issue - very happy about it!
Apparently it was broken by the latest release.
See here, which includes a link to the latest beta:
darthcloud/BlueRetro#1170

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

3 participants