Hello! I'm currently learning the Hard 100% run, and while going through Dim Hideout, in the room with the dudes who poke downwards, I had somehow gotten my head stuck in the ceiling, and I slowly started to raise up into it until I ended up on the platform along side those guys. Has anyone else encountered this before? It was the strangest thing, wish I could have gotten a recording of it.

A bit of a gripe on my end, as I'm currently working through every level in the game trying to beat the time/tie it (have about 20 levels done so far), and seeing levels like Remix 1 level 1 have the record be a few milliseconds below the next one and not having any proof to their time (afaik) is a bit annoying.

So, as the new moderator for this sub, I have changed a rule (or rather started a rule) that I feel necessary for this game. Now, while I don't think anybody is cheating, I ask that from now on runs be accompanied by a video, else they will not be accepted. There are plenty of easy and free video recording softwares out there (OBS being a good one) that can easily record this game, so I ask all runs be recorded with timer as well so that all runs can be verified.

Thank you and have a great day!

Basically, the all collectibles part of the run is redundant, and 107% is no longer something you need to go out of the way to get, so the run is rather redundant right now. I propose that we transition the run over to only needing to kill all the enemies (minus the ships at the start) so we can have the run be clearer in scope and more concentrated in what it is trying to do. Plus, since the run only deals with kills, all the runs in 107% would work for it, so a transition would keep all the runs we currently have.

Hey all,

While I was recording a short tutorial on how to do GBJs (will be up tomorrow, I can hardly talk right now), I accidentally discovered a couple of things in the tower:

One: There's a breakable block in the bottom right corner of Crumbling Sector. Two: Its probably frame perfect, but you can jump on the breakable blocks right before they break.

Now what does that mean to us? Well I managed to record a quick video showing what I mean by all this:

Basically, there are two GBJs that you can do in the tower, that seem to save in total close to (now this is just a guess) 1-1.5 seconds. The first one being in Upward Sector, you can just jump onto the ledge instead of going around the other way, and in Crumbling Sector it is possible to GBJ from the beam onto the block that the blue beam would normally connect with and bounce off that block to skip having to do the jump on the blue beam. Plus, if you break the blue beam block while you're going up the green beam then a recovery from there is easy.

I don't think this has been posted yet, nor do I see people doing this, so I hope you guys get something out of this! :)

(Notepad so pasting might be chunky. Will fix as necessary.)

So I was doing the ship thing for the umpteenth time since my hand has decided it doesn't like to play the game anymore, so I decided to mess around at the start to see if I could find a faster way to kill the ship.

I found one way that might have been faster but I wasn't sure, so I recorded myself doing the way, and compared that to the normal way we are doing now, more or less the perfect execution of it.

Link to the video comparing the two ways: https://www.youtube.com/watch?edit=vd&v=nTH6lmCk8E0

Before I go into any of that, we need to do a little math first. Now my recording equipment is rather low-end, so every frame had some jumpiness to it. Here's a recording of fourteen frames, or the amount of frames it takes for the player ship to go from the first moment of being able to move till when the text box pops up stopping its movement.

(These numbers were taken based off my more or less perfect execution of how to kill our ship now). 3 16 08 (Everything is 3 16 so will drop those for the remainder) 13 16 21 24 27 32 37 41 46 51 54 58 62

Now the 58 and the 62 frame didn't actually have any recorded movement in them, so we are given a range of two numbers to work from: 3.1-3.5 ms a frame.

Now how far do we move then per frame?

Here's the distance, in units given by A Ruler For Windows, which supposedly tracks pixels on screen. For these purposes, they will be refered to as units, but they most likely pertain to pixels. Each distance pertains to the frames mentioned above.

0 20 50 70 105 120 160 175 205 225 255 275 310 310

Also note that these numbers are also approximations within 1-2 units of their actual values. If we average those out, we get approximately 27-29 units. Dividing those numbers by the approximations of ms per frame above, we get a range about 8.3-8.7 units/ms, so approx 8.5 units/ms. NOTE, this number could be slightly off as I had another measurement earlier at 6.9-7.1 having approx 7 units/ms being another number, however in this instance the semantics are not truly necessary since the end points should not be any different. A comparrison shall be given using both results.

That being said, lets look at some values then.

First the normal way, the way we currently do it.

3 16 08 First Frame avail

3 16 62 Text Pop Up ~~ Roughly .54 seconds Actually going in and measuring movement stopped exactly at .5 seconds, which means half a minute to move. This can be proven in the code if we have access to that.

Textbox frames then

3 18 46 - 3 18 50 Regain Movement ~~ 1.84 seconds until regained movement, this is given that rough estimate due to recording issues.

3 20 46 Death Screen

.54 seconds 2 seconds more or less to get to death 2.54 seconds

Now, the .04 seconds given there relates to the values above, from the 58 frame to the 62 frame. No movement is captured there, so the true value lies from 2.5-2.54. On the low end, 2.5 seconds RTA to kill yourself using this way.

Now, lets look at the math done my new way.

2 43 54 First Control (First frame available)

2 44 04 Text Pops Up

2 45 92 Regain Control of Movement ~~1.88 seconds to regain control so .04 seconds variation

2 47 54 Death

.50 seconds ~~.04 variation as seen in the last numbers. 1.62 seconds to kill self 2.12 seconds total movement ~~ Roughly since screen grab ain't too fast

So just over 2.1 seconds to kill yourself this way. One thing that had to be accounted for was variation in how long it took to exit screens and such, so theres about a .04-.05 delay that needs to be taken into account.

Other information to note: I showed in another video which is linked here: that if you move up and down during the starting phase, it does NOT affect your x movement. The most you can move during the starting half a second was calculated at 397.5 units, which is basically 400 units.

So as shown above and as can be seen in the video, it is approximately .4 seconds faster to kill yourself this way. Note, this is not perfect and can be potentially done faster, and the way I did it was not quite perfect either. However, it is at least .2 seconds faster to do this.

In honor of how little time you'll save executing a maneuver that I find difficult to do, I call this move the Kappakaze.

Hey all, in the recent sticky of pilot runs, I made a proposal for what I like to call All Achievements (thanks to BeardedBusker for the name!).

In this run, your main goal is to get every single achievement in one run, with resets allowed. I currently have a path I take that allows for this to be possible, but I am confident that there are a multitude of paths available to complete it.

I also noticed, after my year-long expenditure from this community, that we have at least doubled in size since I last participated. I think that's really awesome that we have grown so much! I'd like to have us keep growing as well, so I want to advertise that I am currently sitting on 7 extra copies of the game that I would like to give out to players who currently don't have the game in order to invite more members to our community. Now I am not too aware of what steps I can take in order to distribute said games, minus going on /r/speedruns and advertising there that more members are wanted (unless we already have too many, although I doubt that is the case?).

Either way, I want to propose a race to the members of this community. I don't know how many can participate in a race on speedrunslive, but on Friday, July 22nd, I'd like to race any number of people in this category, in order to gauge interest on whether or not people would want to run it in the first place. To make things more interesting, I offer as a prize for the winner of the race (or if need be brackets) any game under $5 on Steam (I'd do more but that's all from card sales :P ). If anybody is interested in said race, please comment in this thread, so I can organize how many people would want to participate.

Take care all, and if you have any questions about the category, ask away on this thread or feel free to check it out in the Pilot Runs sticky as well.