All right, I've just spent an afternoon watching this, and... well, at first I was really wanting to vote yes for Star tier, but I don't know... the apparent unoptimised movement kinda lets this run down. I'll abstain from voting for the moment.

I liked this movie. Even if it may be not that optimized, I think it's optimized enough for publication.

I really enjoyed this movie, especially having played through 151 stars a couple years ago. One thing that is, unfortunately, highlighted by this TAS is how annoying it can be to keep getting back into levels. The start locations are very far away from some levels. I don't understand why this TAS used different approaches to repeatedly get back into levels. If one was faster, that one should have been used repeatedly. I assume it could have just been hex edited in once it was done once (maybe not after the fact but at least while making the TAS). This was a huge achievement for a single TASer and first attempt on the full game completion. Yes vote. P.S. Is Extreme Edition very different from this? How does it differ and why was this version not used?

P.S. Is Extreme Edition very different from this? How does it differ and why was this version not used?

Extreme Edition are same levels but lava or quicksands or water has been added. And i don't know why i didn't choosed this version...

Homerfunky, I thought I read somewhere that extreme edition also had some extra stars. Is that true?

Homerfunky, I thought I red somewhere that extreme edition also had some extra stars. Is that true?

http://mario64hacks.wikia.com/wiki/Super_Mario_74_Extreme_Edition According to this page, yes.

I can't get this to sync past the 95th star. Tried the v8 and the one suggested by the author... any ideas on what I am doing wrong?

GoddessMaria15, after homerfunky corrected me earlier I used this version and had no issues: http://www.emucr.com/2009/09/mupen64-rerecording-v8-reset-v2.html

Homerfunky, I thought I read somewhere that extreme edition also had some extra stars. Is that true?

oh yea i forget to say that, yes , there some extra strars . the extreme has 157 stars

I can't get this to sync past the 95th star. Tried the v8 and the one suggested by the author... any ideas on what I am doing wrong?

Some people got desync too at 95 stars and some other people didn't. I really don't know why that happens. Try to use the same CRC as mine in the m64, maybe that can fix the issue or use the same settings (video plugin, RSP) with the default settings.

I have just checked the CRC of the both my ROM and the movie; both are the same.

I'm having the same desync problem after the reset, even with the build thecoreyburton posted. I have seen the run thanks to sonicpacker's encode, but it would be nice to help verify sync for this run in Mupen. I also followed TASeditor's instructions for syncing the run in BizHawk. The movie desyncs around frame 54300 while trying to get the 23rd star. Mario kills all three Pokeys but only collects one of their blue coins, then grabs a tree and eventually runs into a wall. The file is here if anyone wants to see it.

Do you guys have the emulator sped up in anyway during the reset? If you haven't, try letting it run at regular 100% speed through that section

I haven't touched the speed settings at all during the playback so it's playing at "100%" by default.

Aren't mupen desyncs notorious for being computer-dependent? Maybe sonicpacker has just the right computer speed and everyone else doesn't.

My only suggestion to people who can't get it to sync is savestate as Mario is grabbing MIPS (or around there), and reload it in read-only until it hopefully syncs. I've never had one desync myself, and I am assuming homerfunky and I have totally different CPUs (his is older if I recall, and mine is not which is a reason I encoded).

I don't think the problem is with this run; I have the same desync on reset with the Ocarina of Time MST run, even with a fresh download of reset-recording Mupen. I'm pretty sure Mupen-reset-rec runs used to work on my old computer a few years ago, but I haven't gotten them to work on this one. Maybe it is computer-dependent.

People who have desyncs at the reset: does it always desyncs at the same spot or does it desyncs at different spots ? someone told me he got desyncs at different spots just after the reset : one in mario screen and one in file select. So like sonickpacker, i advise you to make a savestate when catching the rabbit and playback again and again until it syncs. And also, by saying it desyncs, you mean there was a bad input or the file A hasn't been saved ? And if it desyncs, maybe try to use the pre-patched rom wich can be officially found here: (MOD EDIT: Read the rules regarding ROM links; that includes hacks that still contain copyrighted content. -Mothrayas)

I could never get the Bizhawk M64 reader to get close to finishing runs without quite a lot of desync. As for this run on Mupen, knowing I'd had it working previously I tried to play it using a few different settings and options and the results were inconsistent. For instance, it'd desync on Glide no matter what I did, then I'd switch to Jabo and it'd sync, then back to Glide and there'd be no issue. Whilst I'm not sure which of these exact steps is significant, here's the process I took to get it to sync whenever it wasn't working and here's a link the exact build of Mupen I was using (config files included). Make sure to use the correct executable, if you're unsure, it's the one with the blue icon: https://www.mediafire.com/?bjddzaylczi6jis I patched Super Mario 64 (U) !: 20b854b239203baf6c961b850a4a51a2 With the patch found here: http://www.romhacking.net/hacks/1425/ And got this checksum: 15d688de0d23bb437d95c358c635465f To test and see if the desync is present, go into the graphic plugin settings and set the windowed resolution to as low as possible, make sure "Limit FPS" is off in settings > general and when the run starts, turn off "Dynamic Audio Sync" in the audio options. This will play the run as fast as possible so you can get to the point quicker and is easier for testing it, I find. If you get through a large amount of frames without a desync, you can also make a save state so that you can load it next time and not have to sit through however many frames you successfully got through the first time. When I was testing for desyncs, I just did this every 50,000 or so frames. If the run doesn't sync with my settings, it could be a computer-specific problem or it could be one of the things I mentioned above. I'd suggest restarting the program and swapping to Jabo's Direct 3D 1.6.1 and seeing if it still occurs. If not, then swap back to Glide and see if there is still a problem. And lastly, I think if you set the movie to pause at 230728 you'll be just after the reset but before the opening of the next bit, I was testing a 1440p Mupen encode and this is how I did it. Hopefully I covered everything and didn't trip over what I was saying too much.

I think I got it working now! The input timings didn't match with Speed. I had to lower it once during before the reset, then increased it back to normal after the title screen. Btw homerfunky, that was me who said that via Skype.

I played that hack to completion (+ save states for the end of the game). Seeing that someone spent time doing a 100% TAS of that game made quite excited and I ended up spending the following 2h watching the video. Though some purists will probably say that the TAS itself isn't good enough (you can more or less see ways to optimize a few sections), I totally support you and congratulate you one more time for this amazing and entertaining work! Thanks :)

I would like if this movie is published that the movie link goes to the main upload

I'm not a fan of the idea in this case since it has neither 1440p nor 60fps

I would like if this movie is published that the movie link goes to the main upload

That just feels so lazy. :P

I would like if this movie is published that the movie link goes to the main upload

I'm not a fan of the idea in this case since it has neither 1440p nor 60fps

60fps? Isn't SM64 30fps anyway?