"I mean, load times are inaccurate for all disc games." I thought you were saying for all games. So if there was a region exclusive game, it wouldn't have anything else to compare to. Like I thought you were saying "well the mechanical parts in one person's wii might operate a few nanoseconds faster than someone elses and this could add up to a few milliseconds" or w/e lol.

When I said "writing down a 10 digiti timer tho after each thing while running and recording and splitting might be tough tho man" I was just expressing a possible counter-viewpoint, not necessarily saying it's my opinion. Writing down the times isn't that hard, adding them up though can be kinda tedious. And the time you spend writing it down you could be spending thinking about things about the next track . ie: "i mess up a lot here last month, be extra careful" "it's really easy to mess up on this particular mushroom, be careful as you havent played in a year" or w/e lol. It'd suck if you wrote something too sloppily and didn't have video footage so you couldnt get an accurate time and ruined the whole run, so you have to be extra careful and ¤mindful¤ while writing.

''^^ Dolphin has faster loads for most GC games and slower loads for most Wii games.''

not this game apaprently \

I';m not sure how I feel about editing all the old times if a switch occurred, or what shortcuts there are to bypass or shorten this.

Thanks frikkinfriks! I just got an 8:05.750 mushroom cup. normally idve submitted as 8:06 and had a 3 way tie for WR, but now I've got the WR all to myself. Thanks man! rounding IS ''unnecessary and retarded''!

Does stuttering makes runs longer? Or do you just see less frames but it's still played in realtime?

Oh sorry, I thought you just rounded up. Technically, the best option would be to just round properly. ie a .9 rounds up, a .1 rounds down. (technically, anything above .444 rounds up :P )

but i guess we're all going with just basically skipping whatever the last digits say

idk i just never would assume a 8:03.95 to be considered a 8:03 but if everyone else is doing that then im fine with it

@Insane: be mindful that if you improve ur nitro rn and get a new video, you'll need to still have the musrhoom cup descprition link to the old nitro cup vid

also, i left comment on that vid on youtube!

also @editing programs: windows movie maker?

Do you need XSplit to ' record'?

You can find out what console they used on the leaderboard. so say System 1 was 20 sec faster than System 2, and someone on System 2 had a run that was 10 seconds slower, you'd really know that this was the most skillyfully produced run and the one to learn the most from and mentally consider it WR.

writing down a 10 digiti timer tho after each thing while running and recording and splitting might be tough tho man

What is stuttering in dolphin tho and how would it affect what were talking about here?

I had accused insane of being mistaken about his time, perhaps typing in the wrong digit at one point. turns out I was wrong. He had left in 2 hours of failed attempts in there which, despite being odd, is of course fine, but it confused me. He did this instead of editing it out, and I had made a mistake, so sorry about that.

However, there's minor things though. Insane cross the line at ~8:03.95. It says ''Edited to 8:03 because you can pause when i finish the run and it's 8:03". It's very clearly a ..95, in which case I believe you would round up. I've landed .5's and rounded up before on previous submissions. So it should be 8:14. Not 8:13.

Insane technically doesn't even need video proof according to the official rules/'standards' chart sticky. Which, I'm actually advocating against now (see here: http://www.speedrun.com/mkw/thread/c029i/1#pi0as ). I think I/anyone_in_this_time_range ¤should¤ require a video. Probably 8:30 or lower for SKIPLESS. Even though I don't have one atm. But I'm currently following the current rules, so that's all that matters. Speaking of which, if the rules DO change, would my older runs get invalidated that were set before this discussed new ruleset took effect?

And Insane, if you see this: what do you use to record so long? And in your vid: 2:05:40 stop shrroming for a bit so the blue shell can catch up :P just a tip

8:01 on mushroom cup beats current WR no skips, yet wouldn't require video proof. seems problematic, no?

Leaf cup 10:15 is quiteee a strong time skipless and requires no video proof also.

shouldnt we have glitch ¤and¤ no glitch standards?

Savestates wouldn't work for that - even if you scripted something to make savestates, you wouldn't be able to use the savestates - it'd be in video of you using them!

what kind of scripts/inoputs are you talking about that would go undetected on stream? asking because i dont see how thats possible,

THESE RUNS DON'T HAVE SKIPS.

Can someone please move them?

Know what, nevermind. Instead of a mod moving them in 5 sec, I just spent 15 minutes resubmitting them all. These are done with no skips, items on. I want them where they should be.

^Yeah but...with live recordings now being mandatory for the top runs, wouldn't savestates/cheated runs be impossible?

Ah gotcha.

1. you say "tend to". Which charts (or runs) are counterexamples of this?

1. Do NG+ times usually have shorter or longer times than regular game?
2. I meant was NG+ itself in the GCN version, not that chao key clitch.

Having to type out your entire 10 character time format thing after each race while in the middle of a speedrun sounds really tedius, distracting, and difficult, and I suspect you have to do it that way with Livesplit.

"We can't change the leaderboard with these estimates"

you're pretty much right, but you could use those esitmates to find the highest ranges of difference. ie "itll NEVER be slower than 32 sec and it'' NEVER be faster than 28 sec" so you could use that gap to have a leaderboard with gaps but i dont think it's feasible, but bloody hell it'd be accurate

and i was basically asking what stuttering is in dolphin

"games that allow emulator runs have identical performance between console and emulator. "

so why would dolphin be banned if the times are the same??

im sorry what? im just confused at that wording

^I'd like to know if that's true or not first before I menualyl do it.

Also, idk why a mod won't just move it for me. It's not really me being lazy, since they'd have to reverify anyway

Haha, idk where to submit this, so I'm making a thread.

I'd like my "Skips" runs all into the "No Skips" category, please.

Better yet, I'd like them in BOTH skips and no skips leaderboard if possible, but if not, w/e.

I even noted in the description of my runs that these didn't use glitches, but they weren't moved once the glitchless charts were added.

Oh, and Star Cup only DOES use glitch.

Anyway here're the runs.

Haha did you cheat but purposely slowed down so you'd get exactly 38:00 so you wouldn't need a video?

Anyway shouldn't this thread be updated to include..... uh........ example times for itemless/skip indiv cups?

Thanks for that video, must've been hard to make.

"What's more likely to happen is we time using the in-game timer instead of RTA."

And essentially mandate spreadsheet programs to add up times? :/

"improved stuttering"

Does that make runs 'faster'?

"There is no constant number to add to create an equivalence in load times between versions. "

True, but say the difference between loading times is 4-6 seconds. I still think it's perhaps useful to note that to some degree, even if you cant find the specific value between the 4 and 6 second mark. This wide gap, although flawed, is still useful IMO, because it still allows viewers to make a generalized difference between two runs without watching them in full.

For example, PLAYER wants to watch a fast speedrun around the 5th place mark as PLAYER believes he wants to attain a 5th place position. 5, 6, and 7th places are all tied, and on different console types. Using these generalised time gaps between loading differences, PLAYER can find out the best run to watch for tips etc for his time range as the one on console that has the slowest loading time would produce the fastest, most skilful speedrun. So he watched that one and learns more and gets a more realistic sense of the pace he needs to be at. Not an exact pace, but fairly accurate pace. Useful!

Now, say one console saves roughly 28 to 32 seconds. A player uses this console, and an equally skilled player on another console attains a time 25 seconds slower. It's still obvious that the player who got 25 seconds slower is still ACTUALLY THE MORE SKILLFUL RUN, because the time range is 28 to 32 seconds faster. 25 is much lower than the most severe time range thing of 28 seconds. 25-LOWER-THAN-28. xd

tl;dr console differences don't have to be exact and are still useful and should probably be noted as they are still able to provide useful time range differences. However it's not exact enough to break leaderboard ties down to the millisecond or anything like that, but it still provides a useful time range comparison.

Yea you need a spreadhseet program to add up the times effectively basically :P