Finally got to watch it all the way. It's spectacular! Talk about some ingenious route planning with the jiggies and notes. Those 2.5 years were definitely necessary to make it so good, knowing how big this game is from the B-K LP. I give it a 9.5/9.5 I noticed that a few times after diving into the water, usually after using that zip to the bottom method, your first stroke gets Banjo run into a wall. Is that faster than aiming properly for the first stroke?

- Kazooie has to be the strongest fucking bird in history. Seriously, she's able to carry a bear on her back for ridiculously long stretches, not to mention being able to somehow maintain her aerodynamic abilities whilst half her body is stuffed in a rucksack and said bear putting quite a load on her back. Let's see Charles Atlas do THAT!

wouldn't it have been faster to open the beaver's house in spring using eggs? then you wouldn't need to watch that cut scene.

He still needs the two notes and mumbo token from behind the boulder in Summer.

Just a comment... I wonder if Mupen64 does not use floating points for positioning or something because there were many times that the movement of Banjo was quite jerky... This has nothing to do with your run's quality, but it makes me wonder why the movement was so jerky...

It's actually a problem with most plugins rendering this particular game. I'll try to explain. If instances of time of Mupen's 60fps are numbered 0,1,2,3,4,5,6,7, most 30fps games would show the following: 0,0,2,2,4,4,6,6. That's all well and good. In fact, some plugins even do that with Banjo-Kazooie, but they have problems like blacking out the screen when underwater, and discolored stuff and missing effects. Unfortunately, the best video plugins treat BK's 30fps like so: 0,0,0,2,4,4,4,6. If you try to ignore it, your eyes kinda adjust. But yeah it's fucking awful and I don't know what to do about it except pretend that it isn't a problem.

I suppose a perfect encode would use a plugin that does the 30fps properly everywhere except specific parts that it doesn't work in, like puzzle transitions and underwater areas and such, and jabo 1.6 for those parts. But jeez, this run is crazy long and the capture is already taking up 50GB. Splicing all those moments in from 2 sources would be a nightmare. :P ...I think I'm going to splice in the ending from some other plugin though, because jabo1.6 with the rdram option on still does a terrible job of showing those "picture" framebuffer objects that mumbo holds up.

I like. As above, "good because i t's a TAS rather than because it's B-K"- most of the funny dialogue is cut out in speed-play. :( Gobi's Desert had some particularly nice segments, like skipping over the maze. I forget which map it was, but I liked when you jumped with a jiggy into water to avoid the animation. Item and health management were good,though only red feathers and health needed it. That said, there were a few apparent errors- On the way to Mad Monster Mansion's puzzle pic (1:06:_ or after frame 119000), you swim along the bottom for most of a chamber, then angle up. Wouldn't it be faster to turn up immediately to take a straighter swimming course? Same issue of not taking direct line after completing Rusty Bucket Bay (~1:46:00/190500, two rooms with odd swim lines). And, though not so easy to fix, I think the mumbo token in the Snarebear you pass on the way out of Click Clock Wood-Fall might be faster than one of the others. "Yes." 9/8

Just a comment... I wonder if Mupen64 does not use floating points for positioning or something because there were many times that the movement of Banjo was quite jerky... This has nothing to do with your run's quality, but it makes me wonder why the movement was so jerky...

It's actually a problem with most plugins rendering this particular game. I'll try to explain. If instances of time of Mupen's 60fps are numbered 0,1,2,3,4,5,6,7, most 30fps games would show the following: 0,0,2,2,4,4,6,6. That's all well and good. In fact, some plugins even do that with Banjo-Kazooie, but they have problems like blacking out the screen when underwater, and discolored stuff and missing effects. Unfortunately, the best video plugins treat BK's 30fps like so: 0,0,0,2,4,4,4,6. If you try to ignore it, your eyes kinda adjust. But yeah it's fucking awful and I don't know what to do about it except pretend that it isn't a problem.

On the way to Mad Monster Mansion's puzzle pic (1:06:_ or after frame 119000), you swim along the bottom for most of a chamber, then angle up. Wouldn't it be faster to turn up immediately to take a straighter swimming course? Same issue of not taking direct line after completing Rusty Bucket Bay (~1:46:00/190500, two rooms with odd swim lines).

If you mean that first stroke when Im starting the diving then check previous page, I aswered that already. And that plant token in fall, you need to make same things as getting the notes in the plants so ist kinda slow.

Could you use AVISynth to cut out the duplicate frames then double all of them?

Couldn't you do something in post-processing to remove every other frame to get that 30 fps fidelity across the whole movie? (theoretical question -- not a gripe)

(or apply interframe blending if you wanted to be really fancy)

On the way to Mad Monster Mansion's puzzle pic (1:06:_ or after frame 119000), you swim along the bottom for most of a chamber, then angle up. Wouldn't it be faster to turn up immediately to take a straighter swimming course? Same issue of not taking direct line after completing Rusty Bucket Bay (~1:46:00/190500, two rooms with odd swim lines).

If you mean that first stroke when Im starting the diving then check previous page, I aswered that already. And that plant token in fall, you need to make same things as getting the notes in the plants so ist kinda slow.

No, it's not that-you're not taking a direct line to where you need to surface, instead taking two longer legs, both before the MMM painting and the RBB witch-switch jiggy like so:

----Surface---
             /
            /
Path       /
__________/

I hope that made sense. And, that first stroke on diving seems to be aligned to your momentum on entering the water, but I don't think that'll lead to any serious optimizations.