I just tried it with Gambatte-Speedrun (r614) and a v1.0 rom and it worked right out of the box. Here are the steps I took:

1. Add Autosplitter component to the layout (Edit layout -> + -> Control -> Scriptable Autosplitter
2. Activate the script (Edit Splits -> Activate)
3. Save the layout (otherwise you'll have to set it up again each time you start LiveSplit)
4. Start the game (splits should start as soon as you hit Start on the title screen)

This is pure speculation, but maybe you could give this a try. I don't have the autosplitter set up myself, but I just had a quick look at the actual code of it. If I didn't miss anything then it doesn't discriminate between different versions of the game (there's v1.0 and v1.1). Maybe the wram addresses simply don't match up. So as a fist step in troubleshooting, just try the other version of the game. If that doesn't fix the issue and nobody else has a good idea, I'll try it out myself and see what's going on.

Apologies for the delay and thank you for your offer! Callumbal and proto will be helping with verifications in the future.

It's just as Jumpyluff said. Sometimes it just takes me a while to get to the verifications and Ark isn't around anymore these days. Callumbal and proto have offered to help out with verifications and I'm happy to accept those offers. Apologies for the delays in the recent past!

Scroll up. [quote=BFrobber]virtual console is fine but it loses around 9-12 seconds over one hour against console due to framerate[/quote]

The actual amount is hard to quantify because on the other hand it gains back a little by having less lag.

Keyboard usage on console games is always a delicate matter, since it allows not only atypical remapping, but also input sequences that are impossible on a controller altogether (e.g., alternating directional inputs in very short succession, or even - if not explicitely disabled in the emulator settings - opposite directional inputs at the same time). In practice, most communities allow keyboard as long as there's no obvious tangible shift on the leaderboards due to some kind of technical advantage. It's the same here, I suppose. If some technique would emerge that would vastly benefit the keyboard input scheme, keyboard submissions would simply be disallowed at that point or put in a separate category. As long as keyboard submissions are insignificant they're simply tolerated.

tldr; So my answer to your question would be: It's a grey area.

5 of the 6 games in this series have completely empty boards. Please either add runs or delete them. Adding games just for completeness is not a good practice.

@phxxd I've written a short instruction on what to record for my comparison: https://pastebin.com/YxZFkCuu Would be nice if you contacted me about this via Discord or Twitter so we don't clutter this thread unnecessarily.

As hinted at before, and as you probably are aware yourself, the GB micro lacks backwards compatibility on its own, hence the rom conversion. I don't know of any instance where this has been done before in a speedrun context and I'd at least be interested in the results, although I share the concerns about the accuracy and the categorization of such a setup in general. That said, I have a simple test setup for framerate and loadtimes (in SML2), so feel free to hit me up if you're willing to do some recordings for my GB platform comparison with your setup.

All valid points. Good to see that the board seems to be in the hands of someone who cares.

My point still stands, though: especially because mobile games usually already suffer on the quality side, intrinsically*, we're trying to at least have their speedrun representations meet some basic standards. It should be in the interest of mobile game runners to do something against the stigma that stems from too many similarly poorly set up and/or populated boards. (Note that there are many console game boards meeting those criteria as well, but it's the sheer number and nature of mobile games that's causing the issue of how they are perceived on the site.)

[quote=not an actual quote ;-)]* Life cycles of mobile games, among other modern game formats, tend to be much shorter and turnover rate much higher than conventional games, so there's less focus on fleshing them out as a game.[/quote]

This board has been up for over 3 years and yet there is not a single full-game run on it. Nowadays, a game with only individual level runs wouldn't even get accepted in the first place. I strongly recommend getting full-game runs on the board. Many mobile and web game boards are poorly set up and don't meet the standards of boards of more conventional platforms. Since you're even tracking the DS version here you should try to meet those standards even more. As it is now, the board sets a bad example for mobile/web games on the site.

It's been over 3 weeks since this board was accepted. All categories are empty and no rules have been defined. Please set up the board asap or it will be deleted.

Funny how things can change: https://www.speedrun.com/sml2/full_game#Beat_Wario °--°

[quote=mugg1991]Back in the day, I did low glitch runs[/quote] Any chance you still have a recording you want to add to the leaderboard?

^this

And as for my personal opinion: while such kill/collect all categories are certainly fun to watch in a TAS video, they tend to be a drag to do RTA. This one doesn't seem appealing to me at all. It'd be more of a challenge run than a speedrun in practice.

Potentially irrelevant, but when I verify runs, I download them via a 3rd-party program and do the verification process in a video editing program. Probably would bypass Youtube's statistics(?)

I think you're massively overthinking this topic. I appreciate your positivity and motivation, but on this particular point you're barking up the wrong tree, trust me. The effort - usefulness relation would be heavily skewed towards effort.

If you're (general you) streaming GB speedruns on Twitch, there's a high chance that someone from the GB speedrun community will show up in your chat in no time and point you in the right direction. It's a small community, but a very caring one that is willing to help. If you have any general questions, feel free to contact me on Discord (Oh_DeeR#2685), since that would lead this discussion off-topic.

Some comments from me on those topics:

3DSVC is 100% software emulation, optimized for fluid display on the 3DS - i.e. not optimized for accuracy to the original release platform(s). My own testing has shown that 3DSVC runs original GB games at around 100.17% speed - which is significant enough to warrant a time conversion, especially since there are accurate emulators out there that don't have that issue. Please note that the analysis only focuses on bare clockspeed and not on differences in loading times or lag.

Pointing a camera at a handheld screen is generally acceptable as long as the gameplay can be seen well enough. It's obviously a suboptimal solution, seeing how many alternatives there are out there, but it's better than nothing.

SGB2 is - along with the Game Boy Player for Nintendo GameCube - the established standard for GB speedrunning. In the casual community it might very well be fairly unknown, simply because accuracy and comparability is not a crucial factor. However, in the GB speedrunning community this is (mostly) common knowledge. ;-)

I don't see the need for per-10-line splits. If anything, it just distracts you from the game. The separate splits would also not provide any meaningful information in something as short as a 100 lines category.

Just wanna add this: SGB1 runs have always been acceptable, too. It's common practice in the GB community to just convert the times according to https://kb.speeddemosarchive.com/Super_Game_Boy_timing If you don't want to convert the times manually, there's a neat web converter provided by Nudua: http://nudua.com/convert