saw this youtube thumbnail and wondered what they were doing, given that this is a game that infamously takes as long as it takes with very little way to speed it up
and the youtube upload is just point 1 of a run going for the maximum score of 99
the whole run is 33 days long.
some highlights from the submission comments.
Now for actual issues with this submission: while this movie was originally intended for 2.8, it requires a dev build to actually play back. Simply be, BizHawk will crash if you load a movie with more than 134217728 frames. This wasn't an explicit limitation, but rather it was due to implementation details with .NET. [1] The issue has been fixed in 2.9 development builds. No sync related changes for gpgx have actually occurred which particularly affect, and there probably will not be when 2.9 is released (as the core isn't particularly active in maintaining). If absolutely needed, I can simply re-run my bot with 2.9's gpgx.
Another fun issue for this TAS was that previously submitting this would crash the site parser. This was due to it reading the ENTIRE input log file at once, UNCOMPRESSED, into a single string. The input log file here is 2.7GB uncompressed (and as a fun bonus, .NET stores strings as UTF16 rather than UTF8, so reading the file into a single string resulted in a 5.4GB sized string!). This easily hit .NET's 2GB limit, and thus crashed and resulted in a "general error." This has been fixed of course (otherwise this submission could not happen :P)