Video is required, yes. And your settings should be verifiable too..

As no one objected and @TenkaTenka also agreed, I made the adjustments from above and moved the runs that do not fit into the updated rules to the Any% categories.

Edit: Done as of October 1st 2022

The current rules require the game settings to follow the original Arcade, that is the HP and some others like Ring Size need to be set to a specific value. Unfortunately this made the whole board a pain to manage as literally half of the players didn't submit valid runs or configured wrong settings..

Long story short, the current rule set for non-Arcade games is apparently too complicated, so my plan/proposal is to simplify them to the following:
- only difficulty can be adjusted, rest of settings stays at default values
- runs with any other custom settings like HP or Ring Size etc. goes to the Any% category

If no objections or other suggestions occur within two weeks I will proceed with the said adjustments. The currently verified runs will be moved into fitting categories.

@NintenLewNintenLew
I think its enough to add it to the PS2/PS3 category.. I added as additional platform there.

Sounds good, so we have the offset if we know the placement (which is in address 0x9e114).

Now if we can get the addresses for the actual loading screens (not menu and end results etc.) and pause timer during those loading screens, we would get a "perfect" loadless timer for full-game runs. And then we can ignore the ingame-time altogether, maybe just keep it for the sake of it..

Forgot to mention, it looks like the ingame time in RR gets rounded which Livesplit doesn't. Also a time with e.g. .35 could end up being either .3 or .4 because of tiny difference. If we could find the address of the RR-ingame timer that would be nice..

Another problem was that if you activate the RTA setting, it always adds a small chunck of time to the game time..

Don't know what to do about it, the isLoading() seems to come after so always a bit of time will pass before the time is paused.

The ingame time is not accurate unfortunately, but I found another address which gave pretty accurate times now. Also removed the delay.

Script:
state("ROADRASH"){
byte hasFinished : 0xC3DFC;
//byte hasFinished2 : 0x6D980;
//byte hasStarted2 : 0xC7498;
byte raceStarted : 0xB7ECC;
byte isPaused : 0x753B8;
byte levelId : 0x6A660;
}

startup {
settings.Add("startOnLevelLoad", true, "Start on level load");
settings.SetToolTip("startOnLevelLoad",
"When disabled timer will start after pre-race countdown ends which is useful for ILs.\n" +
"When enabled timer will start as soon as any game level loads."
);

settings.Add("removeLoadingChecks", false, "Remove loading checks");
settings.SetToolTip("removeLoadingChecks",
"Current Big Game mode ruleset states that RTA is to be used\n" +
"This setting will treat RTA as IGT to account for that without layout changes\n" +
"Or just use Real Time comparison in LiveSplit settings"
);
}

init
{
vars.inLevel = false;
vars.raceFinished = false;
vars.raceActive = false;
}

update
{
vars.inLevel = current.levelId < 6 && current.levelId > 0;
vars.raceFinished = (old.hasFinished != current.hasFinished) && current.hasFinished == 1;
vars.startedIngame = old.raceStarted == 2 && current.raceStarted != 2;

if (vars.startedIngame)
vars.raceActive = true;
if (!vars.inLevel)
vars.raceActive = false;
}

isLoading
{
if(settings["removeLoadingChecks"])
return false;
if(!vars.raceActive || current.hasFinished == 1)
return true;

return false;
}

start
{
if(vars.inLevel)
{
if(vars.startedIngame)
return true;
if(settings["startOnLevelLoad"] && vars.inLevel)
return true;
}
}

split
{
if(vars.inLevel && vars.raceFinished)
return true;
}

Hi and nice work! I will test it this weekend and post results later.

In Full-game runs your goal is to complete the level(s) which is marked by unlocking the next (or finishing the season if Level 5). For that you are required to qualify on each track.

For ILs of course it doesn't matter since you only want to get the fastest time on a specific track..

If it is only at the start then it is not a big deal, but make sure you read the rules before submitting a run. I would also just disable the cutscenes, you don't need them for speedruns.

Btw I also use OBS and I have the problem that I can't use game capture with Win10.. so I play it with DxWnd and then record with window capture. I don't have this short black screen issue there.

Since a request to add the Level 5 category came today, I added this category with some additions to timing rules because it was not clarified there: RTA timing still applies in case you don't display your IGT screen or you had to restart a few races. Also renamed "Careed Mode" category to "Big Game Mode" since that is what it is actually called in the game.

I think it should count there too, unless some major difference is found.

You can read the rules if you go to the Leaderboard and press 'View Rules'.

Also Important: the switch to using IGT was to avoid the impact of loading times and not to grant you free breaks. So continue on to the next level with haste. Else we need to think of some other timing method if this turns out not to work. Remember this is a speedrun board, so complete your run as quickly as possible.

@kyletx500kyletx500 I think the focus should be on doing the runs as quickly as possible (thats why it is extra underlined in the update post). Introduction of IGT was not meant to change the nature of the speedrun itself but only to neglect loading times, so I would consider it as an interruption.

@Zero169Zero169 The timer was never needed to begin with, but it helps if it is onscreen. You also do not need to stop your run and type in numbers if you want to know your pace. Just use the timer as usual and pause it on crossing finish lines and unpause on level starts.

Btw a timer onscreen doesn't prove that a run is legitimate and done in one go. It is simple to edit in a timer afterwards..

@K-PatchK-Patch What changed is that there are multiple people running this game now and there is some competition. Since loading times even on same hardware are so far apart, it is the only somewhat convenient way I see to preserve fairness. Best thing would be some sort of autosplitter that does the job, but it doesn't exist.

Rules update for Level 1 category (13.12.2020):
As discussed in the "Timing Method for 3DO Runs" topic the rules for Level 1 runs were adjusted for a more fair competition, while still keeping in mind that this is about speedrunning.

The adjustments are as follows:
- In-game time (IGT) is used as timing method but:
- No pausing allowed
- No IGT manipulation allowed
- No breaks on level transitions allowed (possible cutscenes should be skipped and the next level selected/started right away)

Legacy runs (aka runs before this update) are not affected by the no pausing allowed rule and the in-game time was left blank when it couldn't be verified (counted only one case)!

Hmm, true. His stream doesn't have it either.. but he can also improve it I guess. x)

@K-PatchK-Patch: Sorry, but thats the best compromise I could come up with. Keeping the main part that seperates skill (races) competitive while still supporting the speedrun idea (with those restrictions).

@MooreaMoorea: I only saw Bunny666Hunters run that didn't have it, but I don't know how you can precisely time it. IGT seems to only correlate with real time on PC version and I don't want to post guessed times here. IGT will probably be left blank and he will need to improve it.

About the Career mode you would probably want to restart if you get busted or fail since it will mess up your whole route or mean a huge time loss. But there is no current neccessity to think about it, no one has done a run yet.

@valdemarkavaldemarka If I remember correctly screen was wobbling all the time without it in Direct3D which is quite irritating. Probably because of the fps thing. Also colors look more ambient imo.

I played with 1024x768 resolution I think and used DgVoodoo with Direct3d. I also never payed attention to the doors.. but doesn't look like a major thing to me.

Original hardware is irrelevant tbh as you can always use an emulator and in the future original hardware of old consoles will become more and more of a rarity anyway..

So back to the topic: Given that the difference in loading times can be that huge I think we need to switch to IGT. But not to get the wrong idea, the IGT should serve as means to provide a more fair competition and not to replace the importance of your real time performance. A speedrun should be a speedrun after all.. so in other words just because we will switch to IGT, doesn't mean you are now free to take coffee (or any other sort of) breaks during your run!

I propose those rules for full-game runs:
- Ingame time is used as timing method, but:
- No pausing allowed (was already introduced)
- No IGT manipulation allowed (don't know any in this game besides maybe deliberately running your game slower on emu, but just to be on the safe side)
- No breaks on level transitions allowed (possible cutscenes should be skipped and the next level selected/started right away)

For Big Game Mode(Career Mode) time during the menu for buying a bike should be added manually. I don't see a way around it.. but it isn't urgent anyway. Probably will adjust rules later when there is really need for it..

If there are no objections or other suggestions to the proposed rules (majority appears to support switching to IGT here), I would make the changes in one week. For retiming I would probably make a spreadsheet or something that automatically calculates those typed in times. And those rule restrictions would only concern future runs (I know one run that used short pausing, but I think retroperspectively "ban" a run is unfair to the runner, unless screen with the IGT is missing).

And about the ILs, you can get any bike in Career Mode, even the fastest one in Level 1 if you repeat races enough. Adding those Level 1-4 tracks to ILs would result in people using the fastest bike anyway. So I don't see the point since those are just shorter versions of the same repeating tracks. But if there really is a need for that, it might be added later. Btw the bike you get in in Thrash Mode Level 5 is only the second fastest bike (on PC version at least and I assume same for consoles too?).