+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
I wonder how it's gonna affect Newgrounds.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
YouTube is not supposed to show the subscribe button on channels whose users have already subscribed to.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
This last case though makes me slightly doubtful that TASVideos actually cares that much about graphical corruptions in their videos, considering
+fsvgm777 never censoring anything.
another artifacts error encode, this one is Gradius by adelikat:
+fsvgm777 never censoring anything.
We do not allow save-anchored movies However, there are certain games with unlockable modes, second quests, or other things of interest that can only be accessed if a save file (or an otherwise "dirty" SRAM) is present. If you really wish to submit a movie made on such a mode, you will need a verification movie made and provided alongside it. Any input file that starts from power-on (for example, a previously submitted movie for that game) and creates the exact circumstances for your submission to sync will generally do.
+fsvgm777 never censoring anything.
The only objections were against the fact itself of skipping the repeating loops, without even giving a reason of why, which I find kind of paradoxical.
For me it should go through all iterations needed to unlock Dr. B, and not start with all the keys collected.
+fsvgm777 never censoring anything.
Why walking the whole time instead of jumping? Short answer: In this game, walking for the whole level (especially stage 0,10,20,30) is ~100 frames faster.
Now, I'm not skilled at doing TASes for platformers.
But anyone can assess that you weren't on the ground soon enough.
Also this game has cycles, so something like 7 can have a different starting compared to another 7 (like this submission and feos having the same 7 compared to mine).
I wasn't holding this information for 2 weeks I swear.+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
I changed my strategy in a huge way. Instead of letting the board fill up and using the color-changing powerup to instantly clear the level, I tried keeping the tile count as small as possible at all times.
+fsvgm777 never censoring anything.
This TAS features Solo Mode completed in 7 minutes and 37 seconds, from the moment I selected Solo Mode to my final hexagon match of the game.
This TAS features Solo Mode completed in 14 minutes and 14 seconds, from the moment I selected Solo Mode to my final hexagon match of the game.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
<Spikestuff> The addition to the description is unnecessary.
<feos> is it clear already?
<Spikestuff> yes
<feos> but is the addition bad, or just not so good?
<Spikestuff> both.+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
I took it upon myself to watch that SMB2J submission. Here is my feedback: For all levels, I noticed that he did not correctly implement the subspeed manipulation to save half of a pixel at the start of every level. I did not check for whether he manipulated subspeed to shorten the walk to the castle by a frame. 1-1: Optimization looks fine, but it was copied from HappyLee's TAS. 1-2: The beginning of the level was copied from HappyLee's TAS. I did not notice any optimization issues here. 1-3: A framerule can be saved here with better optimization on the mushroom grab. 1-4: Fast acceleration at the start of the level is suboptimal; unoptimized fire flower grab; suboptimal movement around first firebar; suboptimal movement around pillars; still has minor slowdowns during Bowser fight that needs to be corrected. The left-right movement for extended durations may have cost a couple of frames or even a framerule starting here because it slows Mario down to 39.5 subpixels per frame. If I see it, I will refer to it as L+R. 2-1: There is a slowdown at frame ~10060 that is unnecessary; L+R. 2-2: There is a lag frame at the ~12660 frame mark that can be avoided. The wall jump is suboptimal. 2-3: I'm not sure if you can spawn a late cheep-cheep here to glitch through the floor, but if it can be done, it would save seconds; L+R. 2-4: Fast acceleration at the start of the level is suboptimal; duck jump to the platform with the koopa is suboptimal; did not use the ground left+right acceleration after performing the clip; unnecessary slowdown after exiting the wall; L+R; still has minor slowdowns during Bowser fight that needs to be corrected. Based on what I've found here, I wouldn't be surprised if you could cut off 1.5 to two seconds in the first two Worlds alone. 3-1: There is a slowdown around the ~18900 frame mark that was unnecessary. 3-2: No fast acceleration at the start of the level. That clip around frame 21,700 does not save time. 3-3: Always use flagpole glitch; L+R. 3-4: There was an unnecessary slowdown around frame 25,930; suboptimal movement through the one block gaps; L+R; still has minor slowdowns during Bowser fight that needs to be corrected. 4-1: There is an unnecessary slowdown around frame 29,080. 4-2: Nothing pops straight out at me in this level. There are a few micro optimizations that I would have if I made my own TAS, but they wouldn't save time. 4-3: Nothing pops straight out at me in this level. There are a few micro optimizations that I would have if I made my own TAS, but they wouldn't save time. 4-4: Fast acceleration at the start of the level is suboptimal; there is no fast acceleration after clipping into the wall; the Bowser fight was clearly suboptimal and can be done without slowing down. I've seen enough.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
I am confused as to what youre talkin about
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.