Emulator used: "antids-mupen" (not the same as v2 apparently)
Video plugin: Jabo's Direct3D8 1.6
Sound plugin: Jabo's DirectSound 1.6 (you can use zilmar too if you want)
Input plugin: TAS input plugin 0.6
RSP emulation plugin
Aims for fastest ingame time
Abuses death to save time
This is a TAS of only the Obstacle course, in which you drive through different obstacles. The ingame time is 1:30.519.
The m64 starts from a savestate, you can download it here: [dead link removed] (I'm not sure where I should upload it so that it stays there forever)
The beginning was pretty hard to get through without having to stop. I didn't think it would be possible at first so I didn't do it, but later found out it was possible (but had to change tires to 'slick', but they didn't seem to be any slower than 'pro slick'), so I redid the beginning. I used death to get through the 5th obstacle faster. The WR on this level is 1.43.118, so it's about 13 seconds faster.
DarkKobold While I'm not sure the exact reason for such a negative audience reaction - whether it be the cheat code, or the savestate debacle, or if the audience just doesn't like Single Track movies - they've spoken pretty loudly against this run. Runs with much higher percentages than 50% have been rejected due to viewer feedback. Thus, I am following the audience guidance for this. Also, the conversation in the thread echoes the votes.
Joined: 11/18/2006
Posts: 2426
Location: Back where I belong
From my standpoint as a judge, I think this a fine demonstration of a tough track. However, not knowing the game, is it only selectable as a stand-alone track, or can you play it as a normal track (i.e. included in a grand prix type game-play)?
Also, I'm somewhat at a toss-up between using selectable codes vs. a save-state. Either way this would end up in the demos/hacks section, but if the codes that nfq used produce the same results as achievements that can be unlocked, I think starting from a clean SRAM and just using the input cheats would be preferable to having to host both a .m64 and savestate. But it's close to 50/50, since we have a lot more movies that start from dirty SRAM than use cheats. Just my $.02
Joined: 6/23/2009
Posts: 2227
Location: Georgia, USA
I think the goals of this movie have been well-enough explained in the discussion here. If anything, there shouldn't be any hurry for rejection for technical reasons concerning savestates, as p4wn3r said.
I liked this run. This really is a standalone track, it seems, so it's more understandable to run that track alone. It probably also shows off the best of the game. I find it entertaining enough to vote Yes on it for publication as a concept demo, provided people find some way to cater to the rules that makes everyone happy.
Used to be a frequent submissions commenter. My new computer has had some issues running emulators, so I've been here more sporadically.
Still haven't gotten around to actually TASing yet... I was going to improve Kid Dracula for GB. It seems I was beaten to it, though, with a recent awesome run by Hetfield90 and StarvinStruthers. (http://tasvideos.org/2928M.html.)
Thanks to goofydylan8 for running Gargoyle's Quest 2 because I mentioned the game! (http://tasvideos.org/2001M.html)
Thanks to feos and MESHUGGAH for taking up runs of Duck Tales 2 because of my old signature!
Thanks also to Samsara for finishing a Treasure Master run. From the submission comments:
Shoutouts and thanks to mklip2001 for arguably being the nicest and most supportive person on the forums.
Cheats are better than a savestate. I apologize for being so harsh. That said, I am not going to give my opinion on the actual run until I get an encode. I know of the rule about playing all tracks, but I think it is up for discussion if it applies here. It is a different mode after all.
From my standpoint as a judge, I think this a fine demonstration of a tough track. However, not knowing the game, is it only selectable as a stand-alone track, or can you play it as a normal track (i.e. included in a grand prix type game-play)?
To the extent of my recollection, it is stand-alone. It never shows up in a grand prix or largely anywhere else outside of the obstacle course selection. It is a unique track that doesn't loop like the races, and is not an arena for stunts or battles.
It's been a while since I last played this game, however. My memories have since faded. But remembering the trouble I once had just getting through is still just enough to make me enjoy this run.
As for the thought of a rejection based on the presence of a savestate (popular topic), that can be fixed by replacing the file with one that begins from power-on. This would take some effort by the author to try to have things sync up, however. If it can't sync, that would make things a bit more of a problem, then.
As long as you can match the time, I don't think anyone would notice the tire smokes are in a different pattern.
that can be fixed by replacing the file with one that begins from power-on. This would take some effort by the author to try to have things sync up, however.
are you sure you don't mean a Hellish amount of effort? i've tried to do it, but the smoke seems pretty hard to manipulate.
As long as you can match the time, I don't think anyone would notice the tire smokes are in a different pattern.
lol... but i think the different pattern of smoke causes it to desync (because that's the only thing that's different). N64 games are pretty complex, so such a little detail can cause a desync, and it's hard to get to sync, because who knows how many patterns of smokes there are. the game has variable framerate, so if something is different it can cause it to skip or duplicate frames in different places, causing a desync.
here's the m64 with syncing spikes, but desyncing smoke, if someone knows how to get it to sync: http://dehacked.2y.net/microstorage.php/info/1653860035/new-spikessynchrem1.m64 (i even changed to the same colors of the car, same music etc, although i don't think those should affect the sync)
the patterns of smoke can be manipulated by starting the level once and then going back to the menu.
I don't particularly care about starting from savestate in this instance, and I think the topic has been thoroughly covered anyway. However, I think this kind of run merits a very thorough documentation of the tricks and things seen. It looks sloppy to me; you wreck once and scrape against walls repeatedly, and at least once drift for no apparent reason. It might be my lack of experience with this game here, but I'm sure I'm not the only one who hasn't played SF Rush 2049, and without a reason why it's better (or even that it's OK) it looks messy and hand-done.
I get that the track is difficult. But for a TAS, there is no difficulty--only possibility and impossibility.
This may be grued, but I'd like to say that I liked watching this movie. It had a nice sense of speed, and the graphics were good too.
thanks, i thought the graphics were pretty good too, especially on the ordinary tracks. not so much on this level. the framerate suffers from the graphics a bit though, even dropping down to 10 FPS occasionally. common problem in n64 games.
Priam wrote:
It looks sloppy to me; you wreck once and scrape against walls repeatedly, and at least once drift for no apparent reason.
i scraped against the wall to reduce my jump height so that i don't hit the wall above (compare how high i jumped on the jump before that one where i didn't scrape against the wall). i'm not sure if it even slowed down my speed actually, so it's much better than slowing down before the jump.
also, i explained in the submission text why i wrecked my car in 5th obstacle: it saves time. either i would have to wreck my car or slow down to get through there, and slowing down was (much) slower than wrecking my car.
It might be my lack of experience with this game here, but I'm sure I'm not the only one who hasn't played SF Rush 2049, and without a reason why it's better (or even that it's OK) it looks messy and hand-done.
yeah, i guess should explain things more detailed in the submission text.
