κ. — Yesterday at 7:37 AM
I set a new KC WR (1:54.911) about two hours ago on CTGP, but the ghost data was not saved on my SD card even though the text on the finishing time screen said it did. I will share the video evidence and provide a timeline explaining what happened in each of the videos.


Google Drive Link to all sources: https://drive.google.com/drive/folders/1XN0L9-MOodCcIzbi4x91c35prDf2E_nx?usp=sharing

There are three videos: two replay buffers (6 minutes each) and one regular recording.
The first replay buffer (Replay 2025-12-06 20-04-49.mp4) was saved after I set the 1:54.911. After that, a bug caused my controller to disconnect, and while I was trying various ways to reconnect it, I started a regular recording (2025-12-06 20-09-02.mp4) in order to preserve evidence.
The second replay buffer (Replay 2025-12-06 20-09-16.mp4) was saved shortly after the regular recording began, to cover the portion that was not captured in either the first replay buffer or the regular recording.
Google Drive
-------------------------------------------------------------------------------------


1st Replay Buffer (Replay 2025-12-06 20-04-49.mp4):

0:00–3:35: Failed attempts
3:35–5:36: World-record run
5:40–: The music that normally plays after setting a PB starts, but it cuts off almost immediately.

2nd Replay Buffer (Replay 2025-12-06 20-09-16.mp4):

0:00–1:30: Same content as the latter part of the first replay buffer
1:34–: The moment the TOP5 screen disappears, the controller’s connection suddenly drops for some reason. I tried to reconnect it for about 10 minutes but it never worked. (This continues into the third, regular recording.)
For clarity: the “No Signal” message that appears at one point happened because I accidentally touched the HDMI cable while unplugging and reconnecting the controller.
Regular Recording (2025-12-06 20-09-02.mp4):

0:00–6:15: Attempting reconnection and testing other controllers
6:15–6:48: Although I already knew this, I had Mitch confirm that the ghost is saved at the moment you cross the finish line. After confirming, I rebooted the Wii U.
6:48–8:00: Booting into vWii + launching the CTGP Channel
8:00–10:05: Checking within the CTGP Channel to see if the ghost was saved; couldn’t find it
10:05–14:40: Returned to the main menu, removed the SD card, and checked the data on a PC; still couldn’t find it
14:40–15:57: Connected the Wii U to the internet via tethering and launched the CTGP Channel. Hoping the ghost was simply saved in an odd location, I tried uploading it, but the screen showed 0/0.
15:57–: Launched MKW and completed KC once to confirm that ghosts save correctly and to check whether my WR (1:54.911) appeared on the TOP5 screen. The ghost saved normally, but the WR time did not appear in the TOP5.

κ.
 pinned a message to this channel. See all pinned messages. — Yesterday at 7:38 AM
κ.
 added
Mitch
 to the group. — Yesterday at 9:46 AM
Mitch
 added
Cole
 to the group. — Yesterday at 9:46 AM
Mitch
 added
Ultra_Pear
 to the group. — Yesterday at 9:46 AM
MrBean35000vr — Yesterday at 11:32 AM
Dang, unlucky, sorry to hear that this happened!
So, that looks like an IOS crash. The IOS is responsible for interacting with almost all the physical hardware on the Wii, like the disc, the SD card, the network, USB devices, etc. If the IOS hangs up for some reason, the game keeps running, but any attempt to interact with these devices fails and the game will wait forever for them to start working again. This is why the music cuts out, because it can't read it from the disc, it's why the ghost didn't save (couldn't write it to the SD), and why your controller disconnected (couldn't read from the USB). Unfortunately the "Ghost data was saved!" message is and always has been a lie, that message actually means that the game intends to save the ghost and doesn't actually indicate success - vanilla MKW was also like this, but usually by the time the message has popped up, the ghost has already saved, but not always.
When it comes to regular TTs, CTGP also attempts to update the game's save file, in fact, it does this first before attempting to write out to the SD card. If you're lucky, the ghost may have had time to write out to the main save before the IOS crashed. If you don't use the "Save game to SD card" feature, then you could check simply by booting vanilla MKW and looking for the ghost. If you do use the "Save game to SD card" feature, you'd need something like Riivolution or a PC tool to load it up and check.
As for why the IOS crashed in the first place, I don't know. It could indicate an issue with aging hardware, an SD card fault, or similar. It could also be a completely random occurrence based on electrical interference, and the hardware could be totally fine. It's clearly not a common issue as this is the first instance I've had of it being reported. Unfortunately if the ghost is not in the save file, there's not much we can do - at least you have a video of it, we can work from there.
κ. — Yesterday at 11:44 AM
just checked the rksys.dat from my SD card, but the ghost wasnt there unfortunately
Image
Image
MrBean35000vr — Yesterday at 11:53 AM
Yeah, unfortunately in that case there's no way to recover the actual ghost, other than using the video to recreate it frame by frame. Practically speaking, I think assuming everyone is happy with this, we just acknowledge it, link the video on mkwrs and the like, and I can create a missing ghost record on the Chadsoft website linking the video (as in, it'll show up on our leaderboards as if you had sent the ghost, but attempts to download it will fail - same process as what we did when we first made the Ghost DB and imported runs that were missing their ghosts).
Unrelated, but we appear to have some Ghost Database issues, so it's going to be a while before the Chadsoft website updates regardless...
κ. — Yesterday at 11:58 AM
An IOS crash may have just occurred. I opened the Homebrew Channel, but the apps on the SD card were not recognized, the Wii Remote wouldn’t connect, and I couldn’t even power off the console. It’s exactly the same symptoms as when I set the WR. It might be a hardware failure.
MrBean35000vr — Yesterday at 11:58 AM
Yeah, certainly sounds like it.
κ. — Yesterday at 11:59 AM
Understood. If others are also in agreement, I’m fine with proceeding in that direction as well.
MrBean35000vr — Yesterday at 11:59 AM
A corrupted IOS could also do it. If you can find a way to reinstall the IOSes, it may help? That'll need some kind of homebrew tool.
κ. — Yesterday at 12:01 PM
I'm not very familiar with homebrew stuff. Are there any good tutorials out there?
MrBean35000vr — Yesterday at 12:02 PM
Honestly I don't tend to mess around with IOS stuff much, so I'm not sure.