Hitman: Absolution (load time remover)

Interesting. So I again looked for anything that relates to Rosewood elevator. Found something. Put it into a code. Tested. Same issue. Timer doesn't start after the cutscene (unless it's closed by ESC). So I checked my previous scans - all of the values were 0 after the loading. So where was the issue?
Well, it was me forgetting to add prevIsRosewoodCutscene = IsRosewoodCutscene. Awesome
Well, it's fixed. Don't know what to do with the rest.

OK, here it is. Version 0.9.5, which is the biggest update so far.

The majority of code is new, taken from Dishonored's autosplitter or written by myself.
It is also the most ambitious and complex project I've written so far. Because of that, I've decided to keep old component until I've sure everything is working fine. The download link is accessible on the first page.

So here's what's new:
- There is not a configuration tab, accessed under layout settings.
- Added autosplitter component with a total of 53 splits (you can configure it in a new tab).
- Added autostarting a timer on a first level (can be disabled in a new tab).
- Added autoreseting a timer on a first level (can be disabled in a new tab).
- Added Presets (accessible under a new tab), to easily configure autosplitting.
- Added a condition that stops a timer with the game isn't running.
- Improved a logic for Terminus Elevator (it is still going to be inaccurate on fast PCs, but on slower it should work just fine).

Also on a sidenote:
What Segments you have chosen to split at, are saved inside of your layout files for LiveSplit. (basically it's an XML). So if you don't want to configure it each time, make a separate layout file for Hitman: Absolution. It's really easy to switch between multiple ones in LiveSplit.

Oh and bad news:
I'll be removing the old pointer for Terminus Elevator. It's because, it was it that was mostly pausing a timer for a bit too long in Kottidor (Mansion, 2nd floor), I could add additional condition - that's not a problem. The problem  And it never was accurate, anyway. But now, it turns out entire scene where 47 is in elevator (camera over his shoulder) is in a separate section, so I pretty much consider this is actually where entirety of loading happens and I can just consider it's loading and count out the time like this. Pretty much perfect. And once you can skip it, the section changes to from 1 to 2 nd the timer starts. So sorry, the times at first mission are going to be like ~1sec longer if I do that, but it should be more fair like this for everyone. On a flip side, if you were getting load times in Terminus elevator - you'll get that second back in Terminus Elevator
Ignore that, I'll just add a condition so it works only in Terminus sections 0. I figured, that the loading actually only happens in section Terminus Section 1, so basically the pointer to a junk value became obsolete, but... that'd introduce like 7 additional seconds to a speedrun (first part of elevator cutscene). So yeah, just to not introduce such inconsistent icy now,  you'll still loose like a second in Kottidor, but... that's about it. Nothing else. The value is still going to be used to figure out when the player presses a button and to split, but it's not going to be used in Terminus Section 1 (since the entire section number is enough to figure out, the player is in the area where loading happens). And it will get rid off issue with a timer paused for too long on fast PCs.

Gonna be just fine.

Updated it. Also thinking really serious about official release via LiveSplit.

Big news: I did some updates and pushed my component to LiveSplit. So it's now easily accessible directly through LiveSplit (1.4 or newer). If you have not installed it yet, simply edit splits, type in Hitman: Absolution as a name, press Activate and the component will download via LiveSplit itself

This game and it's engine.... it's sooooo horrible. Looking into it.

-- EDIT --
So here's a thing with older version. For Terminus elevator it uses a pointer, which I considered once to be responsible for it. Turns out it's not, but it doesn't matter much in a new version, because - it's only considered only in Level 2, Section 0 (which is the bottom area). The loading is Level 2, Section 1. And area past loading Level 2, Section 2. So after section 0, I use a section number to distinguish whatever the game is loading or not. So that's not an issue with a new version.

The issue, for me is "I tried it but it did not restart itself after game crash. So I reverted back to the old one."
I tested it multiple times and it seemed to have been working just fine for me with crashes, so I'm very surprised you had issues with it. Well it had problems with resetting splits, when the game crashed, so I disabled it (since knowing how the often the game crashes, I considered a player should have an opportunity to continue from a point where the game crashed and the timer should be paused and stay paused (as much as possible) until the player is back in game. That should be solved automatically without player interaction, however. That was entire point of it. But if you mean, the timer stayed paused even after returning to a game [as in - player being actually on the level], I'm very much surprised, cause that should not have happened).