If I didn't have homework get done, I would've taken this record from you less than 24 hours after you submitted it to this site. That being said, I think you did a pretty decent run for a "free world record".

NOTICE

I posted this almost exactly two years ago, and now that I'm looking at it again today, the level of cringe and misinformation is unacceptable. Here's the gist of what you should know in January of 2024:

DISCLAIMER: Everything in this post is just my own theory based on my observation of the game. None of it is conclusive, except for the things that are just obviously true.

1. The DS version lags all the time, even on real hardware. The lag is mostly unpredictable and can't be emulated reliably, but there are some things that consistently cause more lag: having more cars on the screen at once, shooting three missiles in quick succession, and simply just driving in certain laggy zones of the track. (In my original post, I mentioned creating dust by turning/drifting, but the real cause was that I was turning/drifting in a laggy zone of the track.)

2. The gameplay and in-game timer are not synchronized by the game, so they sometimes get out of sync.

3. The game speed, meaning both the gameplay AND the in-game timer, are affected separately by the game's lag. One might get slowed down or sped up more than the other.

4. The gameplay appears to be more resistant to lag than the timer. In other words, when the lag gets severe, the timer slows down more than the gameplay slows down.

5. Playing on MelonDS, DeSmuME, or nds-bootstrap affects both how much the game lags and when it lags more. Emulators like MelonDS and DeSmuME reduce lag, which makes the IGT faster, and nds-bootstrap increases lag, which makes the IGT slower.

6. By simply watching videos of speedruns, the changed lag from MelonDS, DeSmuME, and nds-bootstrap cause little human-noticeable change to the speed of the player's car.

7. The key word there is "little". Comparing Jeremy's "this video is an abomination" on MelonDS, my 52.01 (or RTA 53.200) on a flashcart, and my 48:88 (slower than 53.200 RTA) on nds-bootstrap, there's that jump at the beginning which slows down a little on real hardware, slows down more on nds-bootstrap, and doesn't slow down at all on MelonDS.

8. I don't have footage to support this, but from my own experience, I'm fairly certain that flashcarts play identically to a real cartridge, excluding my flashcart's occasional lag spikes that last half a second or so.

9. In my opinion, the differences are small enough to still compare on the same leaderboards with RTA time, as long as emulators and nds-bootstrap are both labeled as such. The only possible reason I can think of to start requiring a real cartridge or reasonable flashcart for top runs is if this game goes viral and attracts a bunch of new runners.

10. However, there are a couple weird things about MelonDS: First, the timer at the beginning of an event counts down too fast. Second, the vehicle selection screen is too slow. As long as the community stays small and none of the top runs use this emulator (Very few runs use MelonDS right now), I don't think these few seconds matter.

My original post is below. Remember, it is from two years ago and contains quite a bit of cringe and misinformation that's unforgivable and unrelatable for my age at the time of posting. For example, my 48.88 was definitely not "really good", and the increased lag is absolutely not a "big advantage" at all. Making a time conversion table is definitely not a good solution because we're supposed to be using real time in the first place. Also, what's with the <strike> tags that don't actually strike through the text? And how do I know for sure that Jeremy is using BizHawk and not either RetroArch or standalone MelonDS? I'm going to reupload my three deleted runs as emulator runs tomorrow with RTA timing.

If you use the MelonDS LibRetro core (through BizHawk or RetroArch), the countdown at the start of a race becomes a lot faster than on real hardware, but the time to load the level and to scroll through the vehicle selection screen takes longer. Here's my lazily made video comparing the MelonDS LibRetro core to real hardware: You can see Jeremy/JowenGrande playing with these issues on BizHawk in this video: Here's a video of Stache playing on a real 3DS:

I don't have a real cartridge for this game at the moment, but whether you're playing on nds-bootstrap, on a flashcard, or on an emulator affects the game speed too. Specifically, when I compared the in-game timer, nds-bootstrap was slower real time, and my 208-in-1 flashcart was faster than real time. As for the emulator, it went a LOT faster than real time: 59.93 seconds on the emulator was the same as 54.48 seconds on my flashcard, or 49.90 seconds on nds-bootstrap! <strike>Oddly, whether I used the flashcart on my DSi or on my 3DS also affected the speed: using the flashcart on my DSi went about as fast as using nds-bootstrap on my 3DS.</strike> From now on, all of my runs will be on a flashcard on a 3DS since that seems to be the "middle ground" and is the most similar thing I have right now to playing on a real cartridge.

Even more interesting, it turns out that my 48.88 is actually slower than my 52.01 if you start both videos at the exact same time because the 48.88 was done on nds-bootstrap, while the 52.01 was done on a flashcart.

What's even more serious is that nds-bootstrap makes the game lag more, in ADDITION to slowing down the IGT. That lag makes precise turning and various shortcuts a lot easier than normal. In many areas, you can basically generate lag whenever you need it by generating smoke from hard turns. That means that even if we did a time conversion table, those runs would still have a big advantage. It's a big shame because my 48.88 was really good even for a run played on nds-bootstrap. I can probably get sub-30 in Hairpin on cartridge though.

For historical purposes (meaning, if someone suddenly cares about this game in the future), here are my 3 runs I deleted from the site:

I made a document going over the speedrun-relevant glitches in the Bedroom area in the DS version at https://docs.google.com/document/d/e/2PACX-1vTNxIyNt0gUZdIPzErxkVRuNPcKKivKg7HNNum4PVSTsaRCrZMfPWC-Fk1OUToZGrFaF8Ja_2ldzLDe/pub (You can also find this on the "Guides" page.)

About that graphical glitch, I haven't had that happen on the Wii version.

I like how this single thread is slowly becoming something of a mini-discord. This might be because I'm temporarily playing on an emulator with a downloaded ROM (I've ordered the game on cartridge and it hasn't arrived yet), but the DS version seems to have some bug or something making it impossible to do certain secondary goals. I'm currently stuck at 4 of 5 flames on Bathroom Break quickrace because for some reason the game won't give me the secondary goal for drifting over the finish line. I'm not really surprised at all considering this is the game where if your save gets corrupted, it says you can press A to clear your save data and restart the game, but it doesn't clear your save data. So I would guess the only way to 100% the game is to do a full run-through starting from a blank save and getting all 5 flames first try on every event, but that's just a random guess.

Two new shortcuts on the first stage for the ds version. If one of us can do the faster one 3 times in a row, it might be possible to beat this stage in less than a minute, but I don't see it happening anytime soon... until I buy a physical cartridge of this game and a better-condition ds to use for speedruns, that is. Still, the console versions are going to stay in the lead for this specific stage until some new game breaking bug is discovered in this game.

Here's a shortcut on Bedroom Brawl: I've discovered other shortcuts in the wii and ds versions, but I don't feel like detailing those right now.

I know I'm 11 months late, but I've found out how glitch shortcuts work on the DS version of the game. As you do a race, the game keeps track of your current progress around the track as a signed 4-byte integer value. The value increases when you go forward on the track, and it decreases when you go backwards. Zero is the start of the race, 1024 is first lap, 2048 is second lap, etc. When you get to 3072, the race is completed. The problem is that you have to be in bounds on the track for the value to increase, and it can only increase by 1 on a single frame, making it impossible to do shortcuts normally. However, if you go through a (non-glitch) secondary path (for example, going under the bed in Floorboard Frenzy) it'll increase your progress to the end of the secondary path, without checking whether you actually progressed all the way to the secondary path the intended way.

Therefore, to shortcut a stage, you have to: 1: start the lap as usual 2: do some glitched shortcuts 3: go through a secondary path 4: continue the lap in the intended way without using any more glitches 5: cross over the finish line to count a lap, and repeat from 1.

Unfortunately, since there is no secondary path in desktop dash, it's not possible to do any huge shortcuts on that stage, but there is a shortcut in that stage on the Wii version which I don't feel like showing right now.

For those who want this "progress" memory address, it's actually different depending on what stage you're on. For floorboard frenzy, it's 02217BDC, and for bedroom brawl, it's 022107FC.