Cycle comparison

PBs accurate as of 2020-01-04

https://docs.google.com/spreadsheets/d/1r4nmTff8_IqiIjbOloK9wuWS3ZbW_12skeneAmaEB2o/edit#gid=0

Finding out your loadless time

[Guide is under construction to reflect the current developments.]

The easiest way of finding out your loadless time is either using the [auto splitter for Livesplit](http://www.speedrun.com/140/guide/gehlh) (Windows only) or the [ingame timer mod](https://github.com/Dalet/140-speedrun-timer/releases) (Windows/Mac/Linux). If, however, you play on console or did a run without knowing of the aforementioned methods, here's a way to determine the loadless time without these tools from your run video.

**Before everything else, it is important now that you know which framerate you recorded in. The next steps will describe the retiming steps for both 30 and 60fps, so be sure you know which method you will need to use!**

You need to get yourself some software for frame perfect video editing. Using Windows Movie Maker or iMovie ¤might¤ work if you edit your original local recorded video and not rip it from twitch/youtube yourself.¤  Any program you have for video editing will do, I even use my DAW (Digital Audio Workstation, so not primarily for video) for timing.¤¤  Be sure that you have set the grid to your recorded framerate, which should be either 30 or 60fps. Once you prepared the session and loaded the video file into it, you can proceed. **It is important now that you know which framerate you recorded in! The next steps will describe the retiming steps for both 30 and 60fps.**

**These reference images are subject to change, the autosplitter has the final say here.**

[First Frame Image](https://drive.google.com/file/d/0B_--WRWWqpO7b2Z0Z3BSVXFxR28/view?usp=sharing)
http://gdurl.com/3K-S

This is the very first frame your video inside of the editor must have. If two frames look like the same, use the first one. Cut away everything that is before this frame.

[Last frame image](https://drive.google.com/open?id=0B_--WRWWqpO7ZndOUWtQcHkwMVk)
http://gdurl.com/R9GH (of course, the direction of the last shot can vary.

This is the very last image your video must include. The time of this frame is to be included to the video. Cut away everything that appears after this frame.

After you've done these two things, you've gotten your exact RTA time. Now for loadless, you need to cut out the loading times which happen after orb activations from the hub until you land on the ground for the level and can move again. The first frame of the segment to be cut out is the one where the hub orb disappears. Cut the video file on the left end of that frame. Depending on the framerate you recorded, it could look slightly differently.

[It either looks like this for all of the levels](https://drive.google.com/open?id=0B_--WRWWqpO7RE14aHFMMHBUazg)
http://gdurl.com/8Xhv

or

[like this for level 1,](https://drive.google.com/open?id=0B_--WRWWqpO7UEt2dHVoa05UNW8)
http://gdurl.com/MQC4

[like this for level 2,](https://drive.google.com/open?id=0B_--WRWWqpO7OEN2ZHQ4dkVBWkE)
http://gdurl.com/2Pee

[like this for level 3.](https://drive.google.com/open?id=0B_--WRWWqpO7aHI0WmJyclhZSFU)
http://gdurl.com/XLE3

The last frame of the to be cut segment is the one where the avatar is not fully landed on the ground yet. You will see that it flies "into the ground" for a few frames and emerges out of it again. The first frame where it has gained its full square size again is the first frame that is NOT cut away. Cut the segment just left from this very frame.

[like this for level 1,](https://drive.google.com/open?id=0B_--WRWWqpO7ZmlHUXlaSlJZa2c)
http://gdurl.com/4P25

[like this for level 2,](https://drive.google.com/open?id=0B_--WRWWqpO7a0VhbnViZzZhUGM)
http://gdurl.com/1CJ6

[like this for level 3.](https://drive.google.com/open?id=0B_--WRWWqpO7dk9HdFR1c084bVE)
http://gdurl.com/38fg

Now your video file should have a passage in between that can be deleted. Go ahead and delete the cut out segment (should be around 5 seconds long) and then grab the rest of the video which is to the right, if not automatically, and connect it to the cut segment. Repeat this process for all of the levels. If you're done and everything went right, you should now have your frame perfect time for loadless. It should be around 23 seconds faster than the RTA timing. Note that this time can vary significantly depending on your setup.

If all of this is too complicated for you but you still want your run to be verified, just contact us on the discord and send us the original video recording, we can do that for you. :)

We're sorry that this loadless timing takes away the fun from 140 a bit but we realized, that in the higher places of the leaderboard, hardware makes a difference instead of actual skill and we want the leaderboards to be fair at first. Once the autosplitter is out, Windows runners (of the Unity3 version, which is faster anyway) can simply use that one and don't need to go through the pita process described above. But once you get the hang of it, it really doesn't take THAT much time. :)

Cheers!
Zet

¤It is recommended to locally record your runs while streaming them, since the video quality is always better and more frame accurate than when you stream! Besides, if you lose connection during a pb and don't have a local recording as a backup, your run is usually invalid. ;)

¤¤There's demo versions of DAWs around that can be used WinRAR like, if you need help, you can ask me about it.

Game versions

Hello everyone,

very quickly I'm giving you an overview of the different available versions of 140, as there are actually quite a few with actually relevant differences. According to the year of their release, they're referred to as "2013", "2016" and "2017" although this might not be the year these specific versions had gotten their latest update.

2013: First release of 140. Used Unity 4 (or 3?) Engine. No edge catches possible, some skips extremely hard and tight. Only available on Windows, macOS (32-bit) and Linux. If you have the game on Steam, you can access this version as the "Legacy" branch in the Betas tab.

2016: Update to the game to the Unity 5 Engine along with the console versions. This is the game's version the consoles have. Most skips and early activations still work as well, except the old GameGuy bridge in level 3 is super hard and next to impossible. Eevee skip is a lot easier. Steam version was never officially updated to this version, but GOG and Humble Bundle releases were this version of the game after the console version release.

2017: Most recent update, first available for Windows, macOS and Linux, later also on Nintendo Switch. This includes the introduction of level 4. As of now it seems all early activations of version 1.0 are still possible EXCEPT for the anyway ultra hard 3-4. Cornerjumps no more possible but those are except for nice swag useless anyway. Early activation 2-3 is way easier due to more generous orb catch detection. This is the default version you have installed on Steam. Widows trick at the level 3 bridge impossible but OG bridge works quite well. Slightly different physics. This is the only version which includes edge catches, making it the fastest known available version.


I hope this little overview helps. Cheers!

Link to SDA thread

Rather than updating the info in both places, I'll just link the SDA thread here for now

https://forum.speeddemosarchive.com/post/1402.html

Orb activation cycles

LEVEL 4 WILL BE ADDED SOONISH!

The "first generation of 140 runners" on the SDA forums soon discovered that the activation animations of orbs can vary by about 0.25 seconds, also that the starting animation's length wasn't consistent either. After a long time and a shift of active 140 runners these issues had been figured out and confirmed by the developer. For all upcoming runners, I want to explain here how the engine works and what the requirements for a quick (or rather "early") orb activation are.

The moment the beat of the title music starts, an internal metronome of the game at 140bpm (hence the title, 140) is started within the engine and it will continue to run throughout the gameplay the whole time (except at one scene but I'll get back to that later). The orbs will only activate on **full beats of the music** (1-2-3-4, as the music is in a 4/4 time signature). That is, if you reach an activation panel shortly after a beat, the animation will start but it will take a few more frames to start the activation on the next beat. If you reach the panel shortly before a beat of the music, the animation will be played much quicker and the orb will be activated one beat earlier. This means, you can only get activations every ~0.43 seconds - except for orb 1-5 which for some reason resets the metronome and will always activate quickly.

After knowing this for some time, I have observed the orb activations and sought their fastest activation cycle. I'll try to list them here and update if I made any errors/new early activations get found. The activation beats refer to the optimal movement after catching the orb and reaching the panel.

1-0: 1 (No bgm, tested with metronome; guaranteed early activation when you press and hold the space bar by booting up the game)
1-1: 2 (probably; tested with metronome)
1-2: 3
1-3: 1 (very tight)
1-4: 2 (tight)
1-5: Always quick, optimal movement would make it start shortly after 3.
2-0: 4 (tight; no bgm, tested with metronome)
2-1: 4
2-2: 1
2-3: 1 (super tight)
2-4: 4 (very tight)
3-0: 3 (no bgm, tested with metronome)
3-1: N/A; no beat music, not tested with metronome yet; also gameguy bridge being almost impossible in version 2.0 makes it hard to find the optimal beat there
3-2: 3 (according to the music, not the global metronome)
3-3: 2 (with quick Eevee skip), 4 (with quickZet skip)
3-4: 2 (in the latest version; until it's now not proven early 3-4 from old version is possible!) in legacy: 3 (super tight and very risky)

Hope that gives you an idea on how to plan the runs. Happy running!

Skip and area names

**Level 1 skip**
Starts when you stand on this block and ends when you catch the orb. // TODO video link
http://imgur.com/b5Ip3w3.png

**Leap of Faith**
Previously called Level 2 Skip. // TODO video link
http://imgur.com/glayMdq.png

**Widow and Bride**
The Widow is the single version of The Bride. // TODO video link
http://imgur.com/3GKfwlb.png

**Bear trap**
Can be done in a single cycle. // TODO video link
http://imgur.com/XgKx29j.png

**Marathon**
Has two parts - short and long. // TODO video link
http://imgur.com/bdqEAST.png
http://imgur.com/sXWLpGG.png

**Wheel of Fortune**
http://imgur.com/XRgrCRH.png

**Zet / Eevee skip**
There are two options here. Zet Skip and Eevee Skip. // TODO video link
http://imgur.com/qFv9HRi.png

**Dream Crusher**
// TODO video link
http://imgur.com/fHpQdzx.png

Timer Mod

You can find it here:
https://github.com/Dalet/140-speedrun-timer/releases

For instructions on how to install and use the mod, see:
https://github.com/Dalet/140-speedrun-timer

Namn	Författare
Cycle comparison	-7 5 years ago
Finding out your loadless time	Zet 8 years ago
Game versions	Zet 4 years ago
Link to SDA thread	jymotion 10 years ago
Orb activation cycles	Zet 8 years ago
Skip and area names	psvm 8 years ago
Timer Mod	psvm 4 years ago