Video Plugin glN64 v0.4.1
Sound Plugin Jabo's DirectSound 1.6
Input Plugin TAS Input Plugin 0.6
RSP emulation Plugin
This run is 3 seconds faster than the previous submission. All the time comes through frame shaving. I have decided to do Whompas Fortress at first. There are many parts which where difficult to make like the star behind the gate, Dire Dire Docks (I hate the levels where you can swim) and other.
Thanks to all and a BIG THX to AKA
Bisqwit: Game is "Super Mario 64", "USA version"; not "USA Super Mario 64", "any version". Changed submission headers as such.
Also, accepting.
Also, processing.
I'm using VLC, and the video is playing pretty bad... It lags, speeds up, and looks choppy, overall. I haven't really had any trouble playing previous movies (except that arkanoid game, and that was only a volume issue).
This is borderline SDA quality ;).
Strange, it playes perfectly fine for me (MPC+ffdshow, Athlon 64 3400+), aside from several-frames-long freezes on nearly every fade-in and fade-out (but it can hardly be the video's fault).
Joined: 12/22/2006
Posts: 193
Location: Flowood, MS
Yeah, it's only the transitions that are freezing, which leads me to believe that it's an emulation glitch rather than anything to do with the encoding.
<adelikat> tony hawk is porn for me
<Comicalflop>my mom is hot
First let me say this run was amazing! All the movements looked like it was really squeezing every frame out though apparently there are still improvements to be had :)
I also had problems with the video freezing during transitions. Its not a big deal since the gameplay was unaffected but I hadnt had any problems with previous avis.
This signature is much better than its previous version.
Joined: 8/26/2006
Posts: 1139
Location: United Kingdom
The AVI appeared fine to me.
The run itself; good run and all that, but certainly improveable. I think that whoever runs this next should really go for perfection so that it isn't beaten by three seconds two weeks after submission.
You see, without a "perfect" benchmark, I believe that each runner believes his or her previous run was close to frame perfect. If you have a better benchmark, or a more perfect run to start off with, you have a reference to go from. Using this reference, it's often a lot easier to spot improvements, especially if the person tasing it is not the same person.
A big point of improvement in this run, however, was the pole glitch, which was discovered after AKA had submitted his run to the workbench, which was delayed, and then subsequently cancelled.
However, with this movie, I'm sure another movie will arise, and another, and then two more. As I said, perfection begets perfection.
I like how these movies asymptotically approach perfection :)
While you might think that 99% is just as good as 99.9%, one has 10 times as many errors and it makes the other look all the better.
This signature is much better than its previous version.
Well from watching, I think most of the improvements came from the bowser stages and most notably the first bowser fight, everywhere else in terms of input was a frame there a couple of frames there, but it does add up.
I have an AMD Athlon X2 3800+ with 2GB of RAM and it still ran poorly for me. I must need to up update my codec package. What do you recommend I install?
I recommend a re-record. If every other frame is indeed a dropped frame, then there is no excuse whether or not some people can view it. It should be fixed to a quality AVI.
I recommend a re-record. If every other frame is indeed a dropped frame, then there is no excuse whether or not some people can view it. It should be fixed to a quality AVI.
The frames may appear dropped due do decimation, otherwise the encode is fine.
Warp wrote:
Edit: I think I understand now: It's my avatar, isn't it? It makes me look angry.
Why is it that I've seen videos, on youtube for example, of people ariving at the second bowser battle WITHOUT bouncing on top of the green circle leading to the warp... just bounce off lava and land inside. Is that slower than the method used in this video?
Why is it that I've seen videos, on youtube for example, of people ariving at the second bowser battle WITHOUT bouncing on top of the green circle leading to the warp... just bounce off lava and land inside. Is that slower than the method used in this video?
The reason for landing inside the filter is for a softer bounce.
素人がごく普通に16枚でプレイすると30分くらいかかってしまいますが、TASでプレイするとなぜ時間を縮めることができるのでしょうか?
[Translation by Bisqwit:
When an amateur plays the 16-star completion, it takes about 30 minutes. How is it possible for a TAS to become so much shorter?]
素人がごく普通に16枚でプレイすると30分くらいかかってしまいますが、TASでプレイするとなぜ時間を縮めることができるのでしょうか?
[Translation by Bisqwit:
When an amateur plays the 16-star completion, it takes about 30 minutes. How is it possible for a TAS to become so much shorter?]
About 20 minutes, actually: http://www.archive.org/details/Mario64_16stars_1947
When making a TAS (i.e. using tools), much higher precision can be achieved. Using almost impossible paths. Mistakes do not exist in the product.
When using VLC, the video would be almost totally unwatchable. Stutters and everything, as mentioned by other people.
So I tried watching it with Windows Media Player 10 with FFDshow codec installed, and it worked fine, except for the sound which sometimes is too loud (mainly on star selection screens) and then comes back to normal volume.
Weird... at least I got to watch it completely.
windows media player 6.4.x (latest version in v6 series) played it back fine and dandy unlike VLC which surprised me... im thinking of switching to it :) but i HAVE noticed that WMP 10 desyncs on some movies and am not 100% certain WMP 6.4.x is affected the same way or if it does indeed use more then the default WMP codecs.