VBA is way faster than normal. There are some areas that make the game lag for 30 frames. Also pausing takes similarly long.

In VBA each of those things only take 1~2 frames. I think throughout the game VBA might save about 2 minutes due to this wrong emulation.

I saw mgba core in bizhawk emulates the game correctly.

I'm asking you to use an emulator that emulates the screen transition lag correctly.

Emus that don't (like in this run http://www.speedrun.com/run/7z07r24y ) should not be allowed in the future.

I took it upon myself to go check what is the margin of difference between transition lag and no transition lag. I followed Ryu's route.

VBA-rr v24 = 141 lag frames (no transition lag) Bizhawk 1.11.3 mgba core = 2348 lag frames (with transition lag)

In a playthrough that follows the route of Ryu's current run, 141 lagframes are accumulated on emulators that don't emulate the transition lag, and 2348 lagframes are accumulated on emulators that do emulate it.

The difference between both is 2207.

2207 / 59.7275005696058 (GBA native framerate) = 36.95 sec difference.

If you apply that time span as a penalty on all current emulator runs (all of which don't emulate transitions lag) on the leaderboard, then the leaderboard changes as seen below. There is a margin of error because some runners may take different routes, pause the game more or less frequently, etc. so this is assuming everyone took Ryu's route.

Current leaderboard:

#1 24:04 RyuLetsPlay (emu) #2 24:19 ultraubernes (emu) #3 25:06 Khead161 (emu) #4 25:22 oeji (emu) #5 25:55 lil_duke_duke #6 26:01 enermaster123 #7 30:03 FanaticDreamer (emu) #8 34:17 Daniel (emu) #9 42:24 n0vafrost (emu)

37 sec penalty:

#1 24:41 RyuLetsPlay (emu) #2 24:56 ultraubernes (emu) #3 25:43 Khead161 (emu) #4 25:55 lil_duke_duke #5 25:59 oeji (emu) #6 26:01 enermaster123 #7 30:40 FanaticDreamer (emu) #8 34:54 Daniel (emu) #9 43:01 n0vafrost (emu)

Interesting read, nice work mugg thanks. VBA not emulating lag correctly is nothing new, I mean that's the reason why the Metroid GBA community is not treating VBA runs as WR and is just allowing in-game time for runs done on emulator. Knowing that emulators have an issue with emulating this game properly, this community might want to overthink its use of specific emulators and maybe switch to console or at least change the ruleset and ban all the bad emulators from future submissions.

1 we have rules on emu and other emus that are used are banned on submitting

This is a really late reply but in future runners information:

Mugg is right that emulators do not emulate correct screen transitioning. What this means is that any time something new shows up on screen pause menu, new map, loading a save, ect. On console its much slower you see a white screen for a certain amount of time vs. emulator witch is almost instant. Mugg has posted what time is lost according to one persons run. This is really hard to accurately find out how much time someone gained on emulator Vs. console. So in order to not abolish emu and to be fair to older runs and to make thing easier than to calculate every single one i have separated them. If there are any other issues please let me know.

Just try to have people run the game on bizhawk w/ mgba core in the future. Many other games (e.g. SML2) actually ban emulators that emulate lag behavior/timing incorrectly, so you might consider doing it likewise.

Also your name is on Ryu's all quest run on the leaderboard, which if I didn't know better looks like you have accomplished that run. That's something you may want to discuss with speedrun.com forum so that Ryu's name is on the run, not yours. As far as I know, you can actually submit other people's runs and put their name and then select the 2nd option in the dropdown menu as such:

Player 1: RyuLetsPlay

You Are:

1. " "
2. "player 1"

This is a small speedrun so i dont really wanna ban emulators. I know the mario kart 64 people do it this way where VC N64 and emu is split. I also wanted to be far to old runs and the fact speedrunslive has VBA the only on listed as allowed emu. i can make bizhawk allowed but that would be silly if if vba is allowed. if later on or if ever this game gets super popular i will revise it but for now i think this separation is ok

I did that when i re submited all of the runs. if you look my name should show me submitting all of the current runs on legacy of goku. When i did put down that i am player one it would remove the name i put and just use mine. so i just left player blank. Ryu all quest still shows his name. but i do see a duplication when u click a person name it keeps the old run and then the ones i resubmitted. how do i get rid of the old ones.

I didn't say that we ban all emulators. But I want bad emulators banned. (Btw, there are many games even smaller than dbzlog and they do all care about good emulation and ban bad emulation.)

Why should we care about speedrunslive's race rules? When a few players want to race the game over speedrunslive, I can see it makes sense they all use the same emulator, whether it is VBA or something else. But when it comes to those runs counting for anything, I urge everyone to use the most console-accurate emulation there is available. New runs made on VBA with the bad timing/lag emulation shouldn't be accepted anymore. Unless you don't care about console accurate speedrunning on this leaderboard. I hope that you do.

I think it would be best to keep the current emu runs on the leaderboard, maybe edit in a note for each run saying which emu the run used, but reject future VBA submissions. We aren't being unfair to those new submissions. We are being just, and it's up to the speedrunners to educate themselves about the current rules.

That Ryu thing sounds like a site bug. Might want to report that to speedrun.com staff.

There is no reason to ban it out when most of the runners have used the emu. If VBA was banned there really wouldn't be any runs. So in my vew i think what the admins of this game was right making its on leader board.