I remember this being a godly hard game. Thus I was never able to beat it back in the 90's. This game is long overdue, and I'm glad it eventually ended up on the Work Bench.
When I was playing poker last week I ran into a situation where I lost with quad tens against a royal flush, but that situation presented above is far more unlikely.
I find the category too arbitrary. Yes, I'm well aware of what an underflow glitch is, but the fact is uses just about every other glitch out there makes it too similar to currently published runs.
Except that it's hardly even a playaround. It's a demo. It may have been injected into the console via a game, but it's still pretty much just a demo.
So, I ask once again, where do you draw the line? How many of these are too many? What would happen if ten more people were to submit similar demos using this particular game? Accept all of them indiscriminately? Accept only some of them? Based on what criteria?
If a future movie is more technical, interesting or entertaining, then it should obsolete this submission.
I will admit I'm using a 7 year old laptop, but I can't imagine it ever struggling to run a GameBoy emulator. After all, it does a pretty good job at running N64 games, and yes I will admit it's not up to emulating GameCube/Wii games or anything similar to that. I was only wondering if the AVI was an accurate representation of how movie would run on authentic hardware. Due to the intense nature of the inputs being fed, and what is being outputted.
Just want to clarify when the emulator starts running as low as 1fps. Especially in the Spongebob part, which I will admit must of required intensive inputs to produce. Would it actually run at that speed on console, or is it just emulation inaccuracy?
When I watched this back on emulator I noticed my emulator was getting the crap lagged out of it. By falling to speeds as low as 1fps. So just to clarify after frame advancing through the movie while observing the inputs. It seems you're creating your own video and audio. I mainly come to this conclusion for two reasons. Firstly, the lack of any directional buttons being held and secondly. When I loaded a savestate during the gold/silver section. The ROM instantly crashed. It's still extremely impressive and must have taken a long time to plan out.
I'm still more interested in watching it go to Kill Screen as this is the Arcade version.
But if it becomes its own thing and has 2 different branches for the Arcade version so be it.
Voting a week Yes on Entertainment.
I'm pretty sure the glitch shown in the first stage of the TAS could get around the kill screen. Personally, I'd much rather see a score attack on this game. As opposed to a speedrun.
Can't you just use sub pixel references? I remember when I was doing a Super Mario Bros 3 TAS. Where I'd often get misleading speed values. However when I looked at pixel coordinates I'd find I was clearly ahead/behind.
New description:
They said there was nothing else to skip. It was thought impossible to find a better route. Sub five minutes was a pipe dream. And now this comes along and cuts out 44 seconds.
Unless there is a viable ACE method. The only theoretical thing they can do now is find a way to open the moat door without using VCUtM.
Thanks for the console verification run. As I would have taken issue had the camera itself gone out of bounds. I was very impressed with how you entered the moat and equally so with how you built up a BLJ in the Vanish Cap, without the need to use a PLJ.
It's like a chicken and egg thing. What came first, the acceptance or the encoding? After all, how can you encode a run without first accepting it, and how can you accept a run without having first encoded it?
