EnglandThere aren't many games that will allow Dolphin emulator usage due to concerns about accuracy.
Also, is it bad that I eat salt?
Objectively, yes, because that'll likely have a very negative effect on your blood pressure if that's a regular thing.
In that case the focus shifts towards proving that any usage of glitches in a glitchless run was unintentional. The standard methods that you see in runs to achieve tricks and skips are not the only methods, so on what basis could you say someone "Didn't intend" to trigger a zip or level wrap if it were achieved by other means?
I think you're missing the part where I specify "It should never overrule an existing video evidence requirement."
Even if the run itself is legitimate, the submission details can be incorrect. We're much more prone to missing or overlooking our own mistakes compared to when examining others' mistakes. Again, this is what the system exists for, it's healthy to have an extra pair of eyes looking at the data because we're not infallible.
Can depend entirely on the game. Many PC games use autosplitters that directly read the game's memory values to output information on the LiveSplit window.
Whilst this is possible to fabricate through a convoluted Photoshop job, it's a hell of a lot more effort than it's worth, especially if the run in question is just a run-of-the-mill speedrun and not a WR. In these instances I would be quite happy to accept splits as evidence that a run happened, but if there was a video evidence threshold in place I would not accept it as a substitute for video evidence.
My opinion has already been echoed in here; if you're the only mod for the game, then whatever but do try to find another moderator for the game.
If you're not the only mod, don't do that.
Backing up the Sonic Adventure 2 suggestion, though I can't promise you'll personally enjoy it if you've previously been turned off by bad cameras and difficult strats.
"you need a bios image (colors of the game)"
That is... Not what a BIOS is.
A BIOS is a firmware file that basically governs initialisation of the hardware. It's what identifies to an emulator that it's running a "Gameboy Color" as opposed to a "Gameboy", etc. Any time there's multiple releases or revisions of a console, they're differentiated by their own BIOS versions, and this applies to region differences too.
Speedrunning fighting games is generally about figuring out methods for AI manipulation, if Tekken runs are anything to go by.
The CPU characters are meant to behave semi-randomly, so if you can force them into leaving themselves open you'll generally go much faster.
Depending on how this is specifically occurring, it could either be a new issue or something runners deal with quite frequently.
Please be more specific about the crashes you're getting;
Does the game attempt to start up and only bring up a "sonic2app.exe has stopped working" error? Does the game window appear and then throw that error? Do you get to the first/second loading screen and then it crashes?
This question was recently asked in the main forums so you may find an answer here:
As people have mentioned, Desmume is your go-to emulator. It's worth remembering though that just because it's the best option doesn't mean it's particularly accurate. For accuracy purposes, shelling out for DS capture is still greatly preferred.
I would be much more enamored with the concept of a hentai speedrunning website if the domain name was something like "hentaispeedruns.nut"
It's very unlikely that any new routes are going to be found by this point, because many of the loading zones in this game are triggered by specific story flags. For instance, Red Mountain is not accessible until the Kiki has been destroyed; even if you clip through the gate, there's just no loading zone there.
