Release WiiRTC fork

dkabot

.
Joined
Apr 3, 2021
Messages
7
Likes
5
Hiya! I think this is my first thread.

While working on an Ashida (that I'll post in Cutting Edge eventually), I came to a terrible realization: We installed an MX but have no way to set the time!
The only known ways to do so are the System Menu and the sntp homebrew; the former requires a compatible display output (VGA ain't it) and the latter requires a network (no WiFi relocation in the cards).
Removing mode and using composite is an option... but we already killed one wii and PMS doing that three years ago, so we're not about to try that again.

While wondering if I could fork sntp to simply hardcode a time, I checked for existing forks, and... someone already did that.
So while poking at building it, I was wondering, "Can I do better?"

Yes.

Enter WiiRTC fork, v0.98!

I've tested it loads and doesn't die in Dolphin, and that it sets the time as expected on my Ashida and a random other Wii.
I'm not really here to make any promises of function or updates, but if you're totally in a pickle, maybe this'll be useful for you.
Check the releases tab or post attachments if that's you.

Not sure how helpful this'll really be in the wide scale of things, given it seems MX relocation isn't too popular, but I figure it's better to publish it than not.

EDIT: Major functional changes have occurred versus the initial release. You originally had to place a timestamp file on the USB drive for your Wii; this is no longer required and will no longer be read. Simply use your controller to set the time.
 

Attachments

Last edited:
Some people still opt to relocate MX for games like Animal Crossing and Pokemon Channel that utilize the RTC. I seem to remember hearing that Aurelio may be adding in proper RTC support without requiring an MX relocation, but that's just pure speculation. Even if it does get added, this is still a great option to have and could have some very specific niche use cases for people who aren't even trying to make portables.

I went ahead and tested it out, but I wasn't able to figure out how to set by the minute. Is there any support for that in here? Or does it only support setting by the hour? Nice work either way!
 
It uses a Unix timestamp in a file to get an exact time. You can use a site like https://www.unixtimestamp.com/ to get a value and paste it in the cfg file. I don’t do any checks on the file, so please be careful.

The hour adjustment is meant to be for time zones, and is inherited from what it’s forked from.
 
Hiya! I think this is my first thread.

While working on an Ashida (that I'll post in Cutting Edge eventually), I came to a terrible realization: We installed an MX but have no way to set the time!
The only known ways to do so are the System Menu and the sntp homebrew; the former requires a compatible display output (VGA ain't it) and the latter requires a network (no WiFi relocation in the cards).
Removing mode and using composite is an option... but we already killed one wii and PMS doing that three years ago, so we're not about to try that again.

While wondering if I could fork sntp to simply hardcode a time, I checked for existing forks, and... someone already did that.
So while poking at building it, I was wondering, "Can I make it read a time from USB?"

Yes.

Enter WiiRTC fork, v0.95!

I've tested it loads and doesn't die too much in Dolphin (it dies if you press A too much), and that it sets the time as expected on my Ashida.
I'm not really here to make any promises of function or updates, but if you're totally in a pickle, maybe this'll be useful for you.
Check the releases tab or post attachments if that's you.

Not sure how helpful this'll really be in the wide scale of things, given it seems MX relocation isn't too popular, but I figure it's better to publish it than not.

Excellent work! I'll be sure to recommend giving this a try to anyone that goes through this issue!
 
I've realized that ASCII colors work in this text environment, and that I can abuse too many switch statements, so I've pushed a v0.96 that starts based on the offset file (or hardcode) and allows manual adjustement thereafter.
It does assume months are 30 days and years are non-leap, though, so it's still a little awkward to adjust. The output should be correct, in theory.
 
Back
Top