From 9a88cbce09c9b25a34a31fd9da58431e57783184 Mon Sep 17 00:00:00 2001 From: Stenzek Date: Thu, 13 Jun 2024 18:31:31 +1000 Subject: [PATCH] Pad: Fix incorrect card mismatch OSD message --- src/core/pad.cpp | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/core/pad.cpp b/src/core/pad.cpp index 45cebefc5..300064ce8 100644 --- a/src/core/pad.cpp +++ b/src/core/pad.cpp @@ -307,16 +307,10 @@ bool Pad::DoStateMemcard(StateWrapper& sw, u32 i, bool is_memory_state) fmt::format("card_load_warning_{}", i), ICON_FA_SD_CARD, fmt::format( TRANSLATE_FS("OSDMessage", - "Memory card {} from save state does match current card data. Simulating replugging."), + "Memory card {} from save state does not match current card data. Simulating replugging."), i + 1u), Host::OSD_WARNING_DURATION); - // this is a potentially serious issue - some games cache info from memcards and jumping around - // with savestates can lead to card corruption on the next save attempts (and may not be obvious - // until much later). One workaround is to forcibly eject the card for 30+ frames, long enough - // for the game to decide it was removed and purge its cache. Once implemented, this could be - // described as deferred re-plugging in the log. - WARNING_LOG("Memory card {} data mismatch. Using current data via instant-replugging.", i + 1u); s_memory_cards[i]->Reset(); }