New Category: Respawn Glitch
This "Respawn Glitch" was already known and almost a legend in this game. Some people had already told me that they had done it, but they had no record of it and didn't remember how/where it happened. But until now, this was the first record of this type of glitch. It was done in the "Liddellroch TD" race by a Brazilian and posted on the YouTube channel "RAFAEL RS" on October 18, 2025 (10/18/2025).
The other two tracks that I've been told had this glitch were the tracks: "Red Pass TD" and "Zorkovaska FR". I believe that the "Respawn Glitch" exists in other FR and DT races, the difficult part is discovering the exact location where it happens.
Path of the new category: Levels > Respawn Glitch
- Find a "Respawn Glitch" in the race that cuts at least 50% of the speedrun time of the first-place finisher in the "Levels > Time Attack" category of that same race.
If characters cut the path in the race and your character remains visible at all times or for the longest time, the screen does not go black and there is NO teleportation. Therefore, there was no "Respawn Glitch". If your character falls somewhere that is teleported nearby, but within the "normal path" of the track, it is also not considered a "Respawn Glitch".
It is only considered a "Respawn Glitch" if the screen goes black and your character reappears far ahead in the race. A distance that the character would take at least 10 seconds to cover via the "normal path".
Respawn Glitch 2: Failures of this type that teleport the character for a distance of approximately TWICE the distance of the "standard" impulse of an "ADRENALINE BOOST"
Example video of a "Respawn Glitch":
New rules for PS2 emulator players on PC & SMARTPHONE
Recently the number of players has increased and with this the game has become more competitive.
To ensure that the game does not have cheaters using [TAS], the rule "2.1 - Emulator requirements (Mandatory inputs recording)" was added as a means of facilitating the identification of legitimate Speedruns.
I ask that players check these new rules to avoid having their runs rejected. This measure is standard for super competitive games, such as Super Mario, Ultimate MK3 and others and in some games they have even stricter rules for emulator players.
Tutorial Show Inputs (Emulator): https://www.speedrun.com/downhill_domination/guides/dffqs
The “speedruns” that surpass the top 3 best must be analyzed in detail to avoid errors. And they should be turned away if they don't follow the rules
Players new to speedrun.com:
New records that surpass the top 3 best, by players new to speedrun.com or who do not have a history of being a skilled player (Videos of speedruns that demonstrate skills, in arcade mode, or freeride or mountain cross)
Guidance for moderators, standard response:
1) Slow Motion Game:
You're playing in slow motion for most of the race. This is not allowed. Your time cannot be accepted. Read the category rules.
2) SUSPECTED speedrun using [TAS]. (Warning signs):
You had an incredibly fast time with no crashes. It has no speedrun history and is playing a replay saved on the PC emulator. Your speedrun raises many suspicions of [TAS] use.
3) Proof of legitimate speedrun, player skill. (Guidance for suspected players):
Next time record a video playing the ARCADE, or MOUNTAIN CROSS or FREERIDE mode in full and send the video link in the description of your Record (speedrun).
Suspected players who have their speedrun refused by guidance 1 or 2 must receive guidance 3 and an explanation of why their speedrun was refused.
Agora é possível baixar os Splits para o modo de jogo que você mais gosta de jogar, também tem o Layout speed que uso no LiveSplit e minha configuração do OBS para deixar o LiveSplit transparente. Para baixar os arquivos, vá na sessão "Resources".
Para a categoria Uphill só fiz os splits da Midoule FR para os outros níveis ainda tenho que verificar.
New Category: Respawn Glitch
This "Respawn Glitch" was already known and almost a legend in this game. Some people had already told me that they had done it, but they had no record of it and didn't remember how/where it happened. But until now, this was the first record of this type of glitch.
