[color=#000080]Hello there,
I've been experiencing a weird and rather uncomfortable bug with DolphinQt, build 5.0-6265 on Windows 10 x64 and before. And now I'm almost sure it does not happen on DolphinWX. Currently I've been experiencing it with Rayman 3: Hoodlum Havoc, I've not tested with other games...
When the game saves my progression, I see the message on the top-left corner saying that data had been wrote on Memory Card A (with the correct file path), like expected. If I quit the game without closing Dolphin and launch the game back, I'll find my correct save again.
However, if I close completely Dolphin and then launch it again to launch the game, I'm back to my old save, which was made the last time I executed DolphinWX rather than DolphinQt...
Terribly annoying, isn't it? If this has not be reported yet, I'll report it in a few minutes. Otherwise, if anyone has an idea...
Thanks a lot in advance!
EDIT: So, I've tried out DolphinWX (same build)... and the same thing happens now with the WX version. I'm a little bit confused now, any ideas? I might be doing a bisect anytime soon...[/color]
[color=#000080]EDIT 2: Same thing happens with the latest build (5.0-6276) and other gales (Burnout, Crash Bandicoot: The Wrath of Cortex) as well...
[/color]
I've been experiencing a weird and rather uncomfortable bug with DolphinQt, build 5.0-6265 on Windows 10 x64 and before. And now I'm almost sure it does not happen on DolphinWX. Currently I've been experiencing it with Rayman 3: Hoodlum Havoc, I've not tested with other games...
When the game saves my progression, I see the message on the top-left corner saying that data had been wrote on Memory Card A (with the correct file path), like expected. If I quit the game without closing Dolphin and launch the game back, I'll find my correct save again.
However, if I close completely Dolphin and then launch it again to launch the game, I'm back to my old save, which was made the last time I executed DolphinWX rather than DolphinQt...
Terribly annoying, isn't it? If this has not be reported yet, I'll report it in a few minutes. Otherwise, if anyone has an idea...
Thanks a lot in advance!
EDIT: So, I've tried out DolphinWX (same build)... and the same thing happens now with the WX version. I'm a little bit confused now, any ideas? I might be doing a bisect anytime soon...[/color]
[color=#000080]EDIT 2: Same thing happens with the latest build (5.0-6276) and other gales (Burnout, Crash Bandicoot: The Wrath of Cortex) as well...
[/color]
![[Image: 1535995391-signature-forum-3.png]](https://image.noelshack.com/fichiers/2018/36/1/1535995391-signature-forum-3.png)
MSI Laptop: Intel Core i7-5700HQ @2.7GHz (3.5GHz in Turbo), 16 Go DDR3, Intel HD Graphics 5600 + NVidia GTX970M, 128 Go SSD + 1 To HDD, Windows 10 Professional Insider Preview (Release Preview Ring)... and of course latest Dolphin x64 development build!