RetroArch has this run-ahead latency reduction that is supposed to reduce input lag, and so I’m wondering if it is allowed to be used as an emulator (using the Nestopia core)
Is there any way of getting it allowed or is there just too much of a possibility of cheating using RetroArch?
Also, if you check this thread (https://www.speedrun.com/smb1/thread/xctnd) it states that RetroArch on mobile is allowed due to it having a Nestopia core
As far as I know, RetroArch is not allowed because it can be used to remove lag, meaning if there are situations like 6-4 where there are a lot of Bowser hammers, the settings can be tweaked to be able to completely avoid lag which would provide an unfair advantage
RetroArch isn't allowed because it has been shown to have the potential for a performance gain over that of the NES console and standalone emulators. So the focus isn't so much about "cheating" per se, but it's more about an unfair performance gain whether it be intentional or not.
If you'd like to read into an example, you can peruse this thread: https://www.speedrun.com/dt2/thread/fx85w
We do need to rewrite the rules to clarify that it's not allowed, we just need to figure out how to phrase that to keep people from trying to poke holes in the rules. We post a whitelist of accepted platforms, meaning if it's not on the whitelist, it's not permitted.
Would RetroArch be allowed with specific settings that have to be set? I read in the thread you linked that 1 frame of input lag runahead comes close to what the actual console can output
There are lots of good emulators to choose from - I can guarantee RetroArch will not be approved in any way. Just choose a different one.
@sam1370 I feel like the part where it talks about the RetroArch run being faster than a run with better execution was ignored based on your response.
That's the issue. It's not the reduction in input lag by itself. If you can get a better time over console with worse execution, that's a problem. That's a big problem.
Asking people to change settings that aren't the default and to provide proof is also an issue. It's difficult enough to get people just to read the rules period, let alone ask them to do something that adds complexity.
I just don't think there's a reasonable way to accommodate RetroArch at this time.
Any% (NTSC) runs below 4:57.000 must now fulfill additional requirements in order to be verified.
- The run's full session must be included in the submission description.
- For emulator runs below 4:57.000, some form of input display must be visible for the duration of the run. A hand-cam or input