Florida, USAThere should be some category updates coming relatively soon, if not within the next few days. I've had to rely on other people keeping me in the loop about this kind of thing due to life keeping me busy, and my focus kind of scattered.
As a sort of addendum, the issue that caused the leaderboards to screw up their time was the board being set to prioritize all load removed times above any run that had the load removed time set blank, so it defaulted to using an obsolete run, making it just look like it had overwritten what I set it to with something worse. This has been fixed, along with the weird prioritization the board had with loadless runs being superior (something I agree with, but not to such an insane extent as to consider something 2nd place that should be 6th). All should be corrected now, you know where to reach me if something looks wrong.
Finally biting the bullet, and just powering through all the incorrect times caused by having a load remover implemented into this game's speedrun scene quite late. For some reason, when I modify a run's time to have no "Without Load Times" it completely screws up the actual time posted, unless I tell it to set that time over and over. I tried to fix this a long time ago to no avail, but it seems just brute forcing my way into telling the leaderboard what the correct time is does get it to concede eventually.
If any of your times were changed to something you believe is incorrect, please contact me through Telegram (@PlasmaMan) or Discord (PlasmaMan#2396) because I seem to be like the old solo guardian of these leaderboards, considering my other mod hasn't contacted me since WR, and I'm your best bet for getting in contact with anyone associated with these leaderboards.
Confirmed it myself, it's about as consistent as you could hope for in speedrunning. Personally, I found it easier to jog across the edge of the dumpster, then mash the climb button when I head to the right, instead of risking being caught in the stutter. Irritatingly enough when I recorded proof with controller inputs, OBS wasn't set up correctly to record sound, so it's a silent video, but is still confirmed to work.
Possibly, my theory is more how close you can get to her via that jump, as I'm thinking being airborne while entering the designated area that flips the game's dialogue trigger is what scrambles her AI into not activating. This could possibly mean that burning time by hunting down and hijacking a faster car could mean getting the skip more consistently, leading to a faster split. I'll definitely get around to testing this more once I get some IRL bullshit surrounding moving and college cleared up this week and report back here with what I find, if someone doesn't beat me to this.
Don't know if anyone still cares about this, but I was able to get a beautiful example of the famous Patsy Skip in a run that ended up dying really badly towards the end. Sadly I was also not recording my mic, so you don't hear me screaming "PATSY SKIP! PATSY SKIP!" over and over.
I've sliced up the original recording of my run to just start when you first enter the car Ricky gives to you, and end on the ending of the Uncle Po split. It really does seem to have something to do with that jump you can do off the stairs, possibly distance.
I managed to fix this for myself by lowering my 144hz monitor down to 60. Try messing with framerate caps, vsync, or your monitor's refresh rate if it goes past 60hz. Some video proof that this worked for me:
Side note, why do so many GTA-like games have gameplay issues tied to high framerates? Off the top of my head I immediately remember being unable to dive in GTA:SA and unable to fly a plane in GTA: Vice City because the framerate was uncapped.
(also thank you for the video guide, been trying to run this myself recently)
