Real Time Clock is not updating using libnds time() implementation about melonds

[Jaklyy]

this is fixed in dev builds
although it's worth noting that this is a result of weird implementation by devkitpro. since iirc this rom also wouldn't work on 3ds, due to the way the 3ds handles (or rather, doesn't handle) certain rtc regs
i forget the exact reasoning why (i think it's something to do with alarm regs?)

[IvanVeloz]

Thank you for the fix. I built the main branch and yes, works perfectly.

I might raise the issue with DevKitPro after I get more familiar with their library.

[IvanVeloz]

OK, I thought I was going crazy for a moment.

The latest build as of today works, but only for a few seconds or minutes. After that, it stops working. I tried a lot of things: deleting the build, deleting my copy of the repo, restarting opening different NDS files. I don't know what makes it work again, but it's rare that it starts working again. I think works again when I delete the entire repo, but that makes absolutely no sense to me.

The crazier thing is I thought this was macOS somehow caching the melonDS executable... but... I switched to my Linux PC and got the same result (it did last a little longer though). The Mac is a Mac mini M1. The PC is a Ryzen 3600 running an Ubuntu toolbox container on Fedora.

Are you able to replicate this? I'm at commit c85a2103bbd41e7119e7d41daa5180dee823b591.

[IvanVeloz]

Okay, I found something interesting. If you disable "Boot game directly" on the Emu settings, the homebrew starts working for a while then stops. The difference is that it always starts working.

[Jaklyy]

i can also reproduce this on windows
that's very odd
needs deleting rtc.bin to fix temporarily and then it breaks again

[Arisotura]

huh, that's interesting to know I'll look into it someday (when I'm not in the midst of a big refactor)

…

On Sun, May 12, 2024 at 3:14 AM Jakly ***@***.***> wrote: i can also reproduce this on windows that's very odd needs deleting rtc.bin to fix temporarily and then it breaks again — Reply to this email directly, view it on GitHub <#2038 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAI66O3Z72X6GBWMBRKJTZB27AJAVCNFSM6AAAAABHSIUUBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGA3TSNRSGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>