I’m using: RG35XX-H, 2601.1 FUNKY JACARANDA, build aeaacd43
This happens with both gpsp and mGBA. It also happens regardless of cpu governor set.
It happens without fast forwarding.
While watching the clock in-game, you can see minutes tick fast at roughly 2 in-game minutes per actual 1 minute and 20 seconds.
pkHeX registers the value as ClockInitialhere. It’ll run backwards making it so that the system thinks more time has elapsed vs system time.
To workaround, I use pkHeX to edit the save and set the Initial Time back to the original amount of days—which means to set it one day ahead—and then set hour, minutes, seconds back to 0; this makes it start from an accurate time again.
Initial time in the save file is changed when the game is saved. That is, I can boot the same save, let the clock run fast as described, not save, reset, load back in, and it’ll be the correct time again. If I save in-game, and load back up, it’ll be starting from an incorrect time.
I recognize this may be low priority, but wanted to document it here. Thank you again for your generous service.