Emulator Issues #1255
closed
Problem importing japanese .gci saves ?
0%
Description
I dumped saves from my real japanese Gamecube on an SD card (using both
MCBackup and GCMM, the same issue), it gave me .gci files (attached to this
post in a .zip)
I wanted to import these files into Dolphin R3943 : Tools => Memcard manager
I opened the file MemoryCardA.JAP.raw, then I pressed the "<- import GCI"
button => selected a .gci => no result...
It dont seems to work at all, nothing change...
Can someone please correct this issue ? may be it because of japanese
characters in the files ?
thanks :)
Updated by lpfaint99 over 15 years ago
- Status changed from New to Accepted
I'll look into it, thanks for the gci files
Updated by lpfaint99 over 15 years ago
also, was MemoryCardA.JAP.raw formatted by a game or by the memcard manager? (memcard
manager formats as a usa/pal card)
Updated by kamel.benlahrech over 15 years ago
hi, and thanks for your time :)
I tryed to format the MemoryCardA.JAP.raw within the same game (Baten Kaitos 1 disc 1
Japanese), and I started a new game and saved. Here's the raw file in attachement.
Like you can see in memcard manager, the text seems to be corrupted. And when you try
to import .gci files in it (from my first post, AF-GKBJ-BKData-000.gci and 001), it
does nothing...
does it matter what position it was saved in the real gamecube ? (first block ect.)
that could also be the problem...
thanks again :)
Updated by lpfaint99 over 15 years ago
do you happen to have panicalerts disabled? if so, this and issue 1257 are similar.
Updated by kamel.benlahrech over 15 years ago
Yep, I disabled it :p
OK, I've tryed to enable it, and now it gave me this error message : "file could not
be opened or does not have a valid extension"
I've tryed to rename the file to "1.gci", same problem
Updated by lpfaint99 over 15 years ago
caused by switch to unicode, I'll fix it here soon
Updated by lpfaint99 over 15 years ago
Issue 1257 has been merged into this issue.
Updated by lpfaint99 over 15 years ago
- Status changed from Accepted to Fixed
This issue was closed by revision r3945.