melonDS-emu
RTC Improvements
Adds various features
Adds ability to either use emulated or real time. Adds ability to select a fixed time on boot, or use current time instead. Adds ability to change the clock via firmware (closes https://github.com/Arisotura/melonDS/issues/208) And for any other frontends (e.g. BizHawk), the ability to set a custom RTC callback, which overrides time options.
The way that the options work is fairly simple:
Fixed boot time will allow for the select time to be used on boot, if it's disabled then whatever the current real time is used on boot.
Real time more just makes it so the advancement of time will correspond to real time, not necessarily that time is locked to your current time (although without fixed boot time and assuming you never change the clock in firmware, it's effectively locked to your current time). This still allows for a user to change the clock in firmware, while letting them not have speedup/pausing affect time accordingly.
continuing from https://github.com/Arisotura/melonDS/pull/1237#discussion_r733865082 for better visibility.
yeah, but having to close and reopen the program is just not a good solution. The underlying problem is that melonDS has no distinction between those two kinds of resets.
continuing from #1237 (comment) for better visibility.
yeah, but having to close and reopen the program is just not a good solution. The underlying problem is that melonDS has no distinction between those two kinds of resets.
I see. This is an odd case, it's preferable to not have time resetting when a reset happens, although having the frame counters set to 0 on init seems icky. Not sure how to proceed with this.