10-16-2011, 05:10 PM
(10-16-2011, 04:36 PM)Itaru Wrote: Okay, I think I've found the problem. In r2345, you registered the cryptSavedataSettingsListener in the constructor for CryptoEngine. The problem with that is if the game has already been decrypted and the CryptoEngine is not used during game load, that listener is never registered and therefore the emu.cryptoSavedata setting is always disabled. It needs to be put somewhere else where it will always be registered since the encrypted savedata setting is not dependent on whether the game's encrypted or not. This explains why that setting works in some of my games and not in others.Good catch! Thank you for your code review!
Fixed in r2355...
Always include a complete log file at INFO level in your reports. Thanks! How to post a log