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
[FR] VMC with CIV like sd2psx #1212
Comments
The CIV (Challenge IV) is part of the magicgate technology, yes. but if I understood correctly from what I've read from SD2PSX firmware, CIV is used to formulate the responses for the card authentication commands. RE4 calls security commands related to the Card ID tho. I dont think CIV will help there... |
pcsx2 creates virtual memory cards, but doesn´t have this problem, I think that the problem is the way of vmc is created, something is missing I tried to make a copy of my official 8mb mc with MC Annihilator, but OPL fails to start the game using this image as vmc If opl could use vmc from pcsx2, sd2psx and memcard pro 2, I think it can solve the problem |
theres one difference. PCSX2 is emulating the mechacon and all the other hardware. they can deal with these issues in a very different way |
so what if using the vmc created by sd2psx or memcard pro 2? |
I don't think it will help, the MC id is not on the card data, it's something the mc controller sends as a response for a command emitted by the SECRMAN driver |
@hardlevel, check out this and this. |
Checks
Describe the FR
Some games have problems with OPL's vmc, like Resident Evil 4.
Maybe these problems can be solve if the VMC have the CIV data. I know the CIV is copyrighted, so... What if OPL look for CIV file generated by the user, and if the file is found and have the corrrect HEX, apply it to the VMC?
Describe the solution you'd like
Apply CIV from file on root of usb to the VMC file when it is being created by OPL
Describe alternatives you've considered
Instead of looking for a file, a text input on vmc settings to include the hex manually
Additional context
No response
The text was updated successfully, but these errors were encountered: