It's not accepted/published yet.

It's not accepted/published yet.

Well, obviously. I'm just wondering what chance this might have, what with a fairly large no:yes ratio and whatnot.

I'd assume no based on the 30-40 second possible improvement, let alone the large number of no votes.

This has an awful lot of no votes. What is the record for %votes being no whilst still being accepted/published?

I'm pretty sure I mentioned it in the thread, but isn't it Phils 2 min SMB run. The River City Ransom one is pretty high as well, but it still seems likley that it'll be published. Looking across the workbench more and more games are getting No/meh voted than ever before, but the technical quality of movies being submitted is significantly higher than the past, conclusion peoples expectations and tastes/standards have risen dramatically from the past. It also should be noted that many people vote no/meh because of dislike of stylistic choices (this does not relate to goals of any movie e.g. takes damage to save time).

This has an awful lot of no votes. What is the record for %votes being no whilst still being accepted/published?

Might be this.

Might be this.

Wow. Jesus, more no votes than yes votes and it still was published? Unless those came after it was published, I can't see how that was accepted.

Just want to say that the best video pluggin setting is Jabo 1.6. I get the feeling that some have watched it use gln64 which is complete no no for this game as its very poor at (or cannot) handling sprites. The one thing that has surprised me slightly is that I fully understand why many people are confused as to whats happening, but yet no one has asked any questions relating to what/how/why.

I watched it using Jabo 1.6 and it was still really laggy.

I watched one of the WIPs for this movie, and now the completed submission. And I learned something. This movie becomes a lot more enjoyable (for those of us who have experienced lag), when you crank the Mupen speed up to around 175%. Although this makes it seem like Duke is moving a little fast (although it didn't seem like too much), the watchability went way up, because I was actually able to see where he was going. So at least I was able to figure it out this time. As for my vote, I'm torn several ways. It was damn fast. That makes me want to say yes. The emulation is poor (but could probably be tweaked by encoding at a faster rate and then slowing down the AVI or something). That makes me want to vote meh. There has already been confirmation of a substantial improvement being possible- big no. If I hadn't found the Mupen speed quirk it would have been an easy no because I would have no idea what I had just seen, but because of that, and because it was well played, I give it a meh (with the hopes of an encoded AVI that makes it watchable).

The emulation is poor (but could probably be tweaked by encoding at a faster rate and then slowing down the AVI or something).

I don't think it's possible. The frames are being dropped, not duplicated, so a speedup will only make it less comprehendable.

The emulation is poor (but could probably be tweaked by encoding at a faster rate and then slowing down the AVI or something).

The emulation is actually very accurate, more so than most N64 games as well as other consoles, it does desync slightly although not nearly enough to frustrate me, and it always happens in games where the frame updates are irregular. The game generally slows down in area where hoards of enemies are firing machine gun based weapons at you, the mini battlelords come to mind most, explosions aren't nearly as bad, but as has been stated before people are generally comfusing skipped frames for lag. If you have a quick blast at some N64 shooters, this is common throughout a lot of games, it just since the post 128bit era we've been used to near perfect 60Hz running speeds for all games.

it just since the post 128bit era we've been used to near perfect 60Hz running speeds for all games.

Hmm. I actually had an impression that nearly every visually complex game that came after 16-bit era was susceptible to lag (not counting PC games, obviously).

OK for those who are interested here's a video. For the people who've already seen it, it may well be worth your while to watch it again.

Question: Why even submit runs here if you're going to upload them to googlevideos/youtube? This isn't only directed to AKA but to all who do that.

Question: Why even submit runs here if you're going to upload them to googlevideos/youtube? This isn't only directed to AKA but to all who do that.

A different site took his submission and published it for their reasons. AKA posted that link because some people may be using wrong plugin, and he's making sure you can watch the movie the way it was intended. There is a lot of people who constantly browse youtube and googlevideo. a Megaman fan might put in Megaman in their search, and offhandedly discover a TAS of it. For those who use youtube/googlevideo: I have two points, of which I know you have a problem with. 1) published runs simply put, it helps the movie itself be watched by a much wider audience. Only people on TASvideos.org will see the movies if they're published only at this site. There is an incredibly huge audience on both youtube/googlevideo for tool assisted movies, on the basis that many people know about the runs but don't look at the site where they originate from. With the published runs I've seen on youtube/googlevideo, there's, for even the not popular ones, at least 10,000 views from non-tasvideos.org members. with more popular movies, I've seen as much as 50,000 to even more than 100,000 separate views from different people not associated at the site. so it's a great demonstration of publicity. 2) WIPs I know of your gripes of encoding WIPs, but the main reason why it's done, is that there are thousands of invisible members that browse the forums. Most sit around without emulators on their computers, and await for the published AVI. encoding WIPs is their way of seeing the progress being made, because they may not have the emulator/ROM. it helps everyone watching the progress of a run be able to able to see it. the other logistical reason, mentioned somewhere her eon the site, is that sometimes it's helpful to encode a WIP and use it to watch a segment over and over in high quality to spot mistakes.

I voted 'Meh'. Just wanted to say that =/ The movie was somewhat interesting, but kinda boring to watch. It's probably not too good of a game to TAS =/ It was kinda cool though ^_^

So what was it, "somewhat interesting", "kinda boring", or "kinda cool"? %)

Dear Comicalflop, nice essay, but you forgot one really important fact. About 97.236% (I made that up but I think it's not far from the thruth) have 2 reactions that aren't good for the site: 1) They go "OMG YOUR THE GRTEAST PLAAYEER IN THA WORLD!!!!1" and so on. So they think that it's a normal speedrun, which isn't good because then they start comparing them with SDA speedruns and because SDA speedruns are of course slower, they'll start mocking them. That's really not good. 2) They go "You cheaters i bet u couldnt even get past title screen lol xiit" Most of those 97.236% of people won't even bother checking the disclaimers or the description. Some do, but still don't get the idea of TASing. That's really not good and that's why I'm against posting these videos to Youtube/Googlevideos.

We cannot be held responsible if anyone is ignorant. We have labelled our runs as long, repetitive, informativ and thorough as possible. Each individual is responsible for his or her own act. And in this situation, it means if you do not understand the difference and purpose of a speedrun and a tas then its your responsibility to increase your knowledge or settle your curiosity and find out what the deal is, like I did when I saw my first timeattack. Conclusion: we have done what we can and the rest is up to the viewers. Also, there are people who cannot view some wips of certain games through Mupen (like me in this case) so I thank AKA for uploading his run. I will vote yes on this run because I wasnt that bothered with the speed. I could pretty often understand what was going on.

I highly doubt the majority of the thousands of invisible members are so lazy as to avoid downloading the emulator and rom.

I know of your gripes of encoding WIPs, but the main reason why it's done, is that there are thousands of invisible members that browse the forums. Most sit around without emulators on their computers, and await for the published AVI. encoding WIPs is their way of seeing the progress being made, because they may not have the emulator/ROM. it helps everyone watching the progress of a run be able to able to see it. the other logistical reason, mentioned somewhere her eon the site, is that sometimes it's helpful to encode a WIP and use it to watch a segment over and over in high quality to spot mistakes.

I'm not sure where you obtained this information about lurkers on the forums. I would imagine that most people who follow the forums to see progress will have the emulators and such. I would imagine that those who are less focused on the forums and more on the main page would be the ones who do not have the emulators. To clarify, I don't see a problem with someone taking their own time to create an AVI of a work in progress, or uploading it to youtube or similar sites, but I do think it's bad for the site to ask other encoders to do it for you. Even for the N64 games that have a lot of sync problems, time and effort spent on resolving those sync issues by those who want to watch would be much less than the time spent by others making an AVI every couple weeks with updated progress. The problem is that all these viewers are lazy and want others to fix their problems, and I fail to sympathize with that. Yeah, I'm looking at you, Ocarina of Time thread. Also, encoding a WIP to watch it for mistakes is a really, really inefficient (and I would imagine, frustrating) way of doing so. I would recommend just using the emulator and its read-only toggle function with the frame counter to get whatever information is necessary. (Unless by mistakes, you meant mistakes in encoding quality)

Oh and Comicalflop missed my whole point.

Question: Why even submit runs here if you're going to upload them to googlevideos/youtube? This isn't only directed to AKA but to all who do that.

Meaning, if you just want be known by others, get more credit from your work, be "famous" I see no point submitting runs here because you can more easily submit them to Googlevideos with a bigger audience.

If fame is what you want, isn't submitting your movie to as many places as possible the best choice? Besides, submitting it here is as easy as it gets since you don't even need to encode it yourself. Personally I don't see why videos shouldn't be uploaded to other places. I'm glad this one was at Google videos so I could get to see it. I just can't get Mupen to work properly.

You may as well ask why we should bother to upload to sites like Youtube when other people are already scooping up the published videos from this site and uploading them to those other sites.