i really like how you had the awareness to pull yourself up to the right on last rope, if you try to go left there the hammer would slip for sure
i'm shocked how the level 3 glitch worked with so little space between the hammer and the floor
wow i completely forgot how insane the level 4 is here, iirc i was going for ship skip on even/close runs and i got this run... And here i was casually trying to beat this shit playing on and off for the past 3-4 days xd best i got is a low 23
bruh the only obvious timesave is a better start and that's just so difficult to do this run is cooked
You didn't make a mistake chip it's just, confusing xd also i updated every leaderboard except any% leaderboard, i'll start now and complete it this evening. Takes a bit longer than i thought with all the obsolete runs
because of how nice the frame counting in-game timer is, we needed to change how we time runs and that's ok :D
I will admit I don't love bumping this thread but it has to be done :)
We have an in-game timer now! The way it works is it counts game frames and converts them into seconds. Sexy Hiking runs at 50 frames per second. So each frame is 0.02s long. The in-game timer is great because it makes recording and timing your runs a lot easier when you don't have to deal with an external program like livesplit.
However there's a couple small issues about this method which make the runs that use the in-game timer look 0.04s slower for each level. So a full run would look 0.16s slower than it actually is. The good news is this situation is consistent. The bad news is the timer isn't easy to fix.
Our top priority is to make sure what a runner sees on their screen compares correctly with the times on the leaderboard. It would be confusing and mentally taxing to force the runner to do unnecessary math each time.
So the solution is adding +0.16s to each full run and adding +0.04s to each individual level run. It sucks to make runs appear slower but it's for a good cause.
Why is frame counting causing the runs to look slower?
The way we manually timed runs equates to whichever frame a level ends on minus whichever frame it started at and adding up all 4 levels. So for example in first level that would look like Frame 251 - Frame 1 = 250 frames. Our example run is 5 seconds long. However the in-game timer would show 5,02. And then on the second level, it doesn't start from 5,02 again, it starts from 5,04. just like level 1 started at 0,02 instead of 0. it doesn't make sense as 0.02s haven't passed. but it's a new frame, the 252nd frame. so it shows 5,04.
Ok, but that only adds up to 0.08s for 4 levels. Where does the other 0.08s come from?
Turns out when you touch the angry spinny red face to end a level, the game skips a frame! Going frame-by-frame on recordings, when the runner ends a level, one can see that the timer jumps 0.04s instead of 0.02s like it should. It's also visible if you pay attention to how fast the red face spins, its animation skips a frame. This can be seen in versions without the timer as well. So that's where the other 0.08s comes from.
i will post another message when i'm done adding to non-igt runs.
here i go unnecessary necroposting woe is me (thanks julian)
it doesn't change anything about how the game plays people can use whatever client as long as the game is the same it's fine not a big deal
Ok let's do it! I don't know how any of this works though xd Looks like extensions are a seperate leaderboard. As any game that has category extensions have a different url(goiwbf_extra for getting over it as opposed to goiwbf) and different(lower amount for getting over it) moderators. So let's ask spener to create it i guess. I will leave him a message
Hi carotina, remember we talked about the "sexy hiking practice version" limiting monitor to 60Hz and after I saw SixthStep submit a run using this client you posted in here I was curious if this client also did that. I checked and it doesn't limit to 60Hz, i was able to play at 120Hz however while opening and closing the game it still does dark flashes like rebooting the monitors. Woahbust's client in the "better sexy hiking" thread doesn't do that.
I love the score, it is amazing to not worry about using livesplit and it's easier to time runs. If you could either fix the monitor rebooting behaviour of this client or implement the score to Woahbust's client it would be the giga speedrunning client we recommend to everyone! :D