Standard stuff: Specs in signature, build 1.2.1 and latest GIT, plugins default(GSdx AVX, SPU2-X, lilypad, nulls for rest), settings tested at default, memory cards are standard 8mb in size.
This is a minor bug, but a bug nonetheless.
The very first time(per boot) you open the memory card interface in the game, whether to save or load, it tells you "No memory card is inserted" and when you confirm that message, it asks you if you want you cancel your save/load. If you pick no, then the memory card loads normally.
Odd this doesn't happen to me atm. Just tested it out using GIT 1.3.0-734 (PCSX2 1.3.0-20141206195932 - compiled on Dec 6 2014)
I'll download the latest GIT later on and see if it happens there, since this 734 is far from the latest GIT build.
Bah none of my bugs are ever reproducible!
When I get out of the area I'm in I'll make a video, in case I'm doing something strange lol
Hmm, it may depend on the save point, as I can't reproduce it at the current location.
If it crops up again I'll show it.
Stupid esoteric bugs, just once I'd like a reproducible one.
It's like going to the doctor. When you're at home you ache all over, then when you're in the waiting room you're magically cured~
Seriously. I've been noticing this my whole playtime(I'm about to the end of disc 1) and the second I report it, it goes away.
So now I'm sitting here doing strange things like save/load state, turbo, etc to try to get it to reproduce and it just won't.
Could this have anything to do with the "ejecting memory card after loading savestate" feature the emulator has to prevent corruption?
Yea, definitely rule out savestates.
I did rule them out - when it was doing it, it would even do it on the title screen with no states involved.
I even tried to TRIGGER it with savestate, by save stating with the menu open and on save, then loading and immediately opening the interface.
And still couldn't reproduce it.
So now I'm just recording all my gameplay til it happens again
So did this ever reoccur Blyss? Or should we mark the bug as invalid for now?
Spoke to you about this in PM again a while back and the problem didn't reoccur for whatever bizarre reasons.
If it happens again though - Feel free to reopen this one. For now marking it as invalid since we can't reproduce it.