You can buy a webcam for pretty cheap and plug it in to your computer so you don't have to use your phone. You can also buy a capture card for about $50 if you already have an original DS and install the board yourself (not too hard) from http://3dscapture.com/ds/order.html . If you don't already have an original DS or don't want to install it yourself, it will cost more.
So should we have a vote or something on separating the leaderboards?
That's definitely a problem with splitting the leaderboards and why I thought there should be only one, but I think a solution would be having a note on the top of the VC and emu boards saying about how much faster they are, if people want to compare times.
We should probably just make separate leaderboards
We've been using the time without loads for a while, and it has a lot of problems- namely it being really confusing/annoying, and intimidating for new runners.
I think there's a better way to do it. There would be a second column called "DS timing" / "adjusted timing" / "adjusted loads" or something. VC would have 45 seconds added to the new column, emu would have 38 seconds added to the new column, and DS would be the same in both columns. The extra time is added because VC and emu loads are about 45 and 38 seconds faster than DS loads, respectively.
Pros:
- The main one: SO much easier and quicker than taking out load times
- I think the way we have it now is also kind of intimidating to people wanting to run this game, so it would be better for them, too
- Don't need to go back and count how many/which load zones you went through, which is annoying to do, and a problem for runs that don't have a recording
- Harder to mess up: since the way we have now is so complicated, I'm sure there have been/could be mistakes when calculating the load times. Adding a fixed amount of time is much less prone to error, and much easier for a mod to verify
- A simple solution is usually better than a really complicated one
Cons:
- Slight Inaccuracy. The difference between load times is 45 or 38 seconds if the runs go through the same exact load zones. As the number of load zones increases, the difference in load time increases too. HOWEVER: the change would only become significant in runs that go through a lot more load zones (a lot more load zones = have a lot of deaths = time doesn't need to be as accurate anyway)
- Somewhat arbitrary / not the usual way of dealing with load differences
- May look weird to have 2 columns with the same time in them for DS runs, then adjusted for vc and emu (we could change the formatting or something though)
It wouldn't have to be exactly as I said here; please make suggestions for improvement, tell me if/why you don't think we should change, etc.
It's pretty lenient here because it's harder to record DS than other consoles. You can record with a camera, and if you can't, you can just go without video and put your splits in the comment.
You don't need to reset over not getting the blue shell in 1-2. Getting it from the toad house is 100% consistent and only loses 10 seconds. Just run to the right and hit the bottom right corner of the box and you will always get the shell.
And for the bowser jump: you run to the right a bit, do a medium height jump, and you need to hit the right side of bowser jr. Very important to hit the right side. The bowser jump is hard and takes practice to get down well, so you should try to have an extra fire flower in your item box to use if you mess up the jump.
Here's a clip of it from one of koffing's videos (at 1:00):
cros, are you talking about the end of 1-1? Because there is a consistent way to do that.
Not many people run the categories besides any%, so we don't take off the loading times for them. We just use the real time.
I think it should all be in seconds. If there are two runs very close to each other we could retime them or work something else out. Otherwise, ms is pretty pointless. I also agree that it makes the lb look clunky
Yeah milliseconds are pretty useless anyway, I agree with rounding
Since we already know about how long each door, pipe, etc. takes on average, we could just count the number of each in the run to get a rough estimate. Also, I found a way to go through videos frame by frame at 30 fps, so I plan on retiming for a bit more accurate number.
I'm conflicted on having separate tabs. Not many people run this game, so a lot of the tabs would only have a few runs in them, and I think it's better to have it unified. Splitting runs by system can work for something more popular like MK64, but other games with a smaller community and load differences keep it as one and take out the loading times (Super Mario Bros: the Lost Levels for example).
That being said, I completely understand people not wanting to deal with loading times. Maybe on the run submission form it can have something that says you don't need to do your own loading times, but it's appreciated or something. I'm open to other ideas.
I'm guessing the best way would be audio cues in the music, but if you mess up there's not a good way to save that
Have you looked at the Google doc about converting the time? What are you confused about?
Do you mean converting your time to time without loads?
This looks great and very well layed out so far! If you want help, we will definitely work on this with you. Thanks.
Nope. Both versions run the same.