So I've done some testing with loading times in between courses (that is, the time it takes between the player selecting "Next Race" to the time that the cinematic of the next track begins) and discovered some interesting stuff. I compared the loading times of my Wii to the loading times of other Wii's and Wii U's both irl and via videos submitted on this site, and the discrepancies are troubling. The track for most systems will usually load in about 6 seconds, give or take around .2 seconds, but I've recorded times of up to 7 seconds on certain Wii's. I understand that every Wii and Wii U has a minorly different disc drive loading speed, but over the course of, say, a 32 track run, the difference becomes larger and larger. If your disc drive loads courses in about 5.8 seconds (the fastest I've seen) and someone else's disc drive loads courses at around 7 seconds (the slowest I've seen), the time gap between two 32 track runs that are exactly the same otherwise is roughly 30 seconds, just because of loading time. I realize that adding a "Time without loads" column to all of the leaderboards would be a huge hassle and would probably invalidate a lot of runs, but I thought it was important to bring this up.
What I'm really trying to say here is that the run times for this game should be measured without loading times. As it is now, players are at an unfair advantage if they are lucky enough to have a system that loads slightly faster than others.
I know what you mean. I added up the times of two 32 track runs in order to compare the difference in loading times a couple days ago and it took me a painfully long time. I suppose I'm content with the current leaderboard format, just for the sake of convenience. But I still think that people who take this game really seriously would be mad if they lost a chance for wr because of loading times. oh well
Twitch has recently announced that effective April 19, 2025, they will be imposing a 100-hour storage limit on Uploads and Highlights, and if surpassed, Twitch will automatically remove highlights/uploads to stay under the limit.
Going forward, all runs requiring video should be submitted with a vi
