Too lazy for proper testing, I'm just trying to match WR's on 30 FPS instead. This is not accurate down to hundredths of a second, nor the attempts are good. But it's good enough to paint the picture. FPS difference is not that big as people make it to be. Accurate testing would need a lot more runs to eliminate skill issue, mistakes, maybe avarage the runs out. It would take too long, it's boring af, and I'm not really 30 FPS enjoyer. Tbh input lag from 30 FPS was worse than speed itself. It took a while to adjust. If I spent more time on this, I'm sure I could close down the gap. Anyone could.
Running speed is not tied to FPS, or it's at the edge of a margin of error. I went on GTA V speedrun discord, asked for more info about it, and they said the same thing. Didn't test tab running because I'm not sure how to make a foot race with weapons available, and laziness. I doubt FPS makes any difference anyways. If you think otherwise, feel free to test yourself.
___________________________________________
tl:dw
Fleeca drive:
WR: no video
2nd: ~1:42:xxx (100%)
My attempt: 1:43.299 (101.27%)
HLR drive:
WR: no video
2nd: no video
3rd: ~1:00.xxx (100%)
My attempt: 1:02.706 (104.5%) - half of it is probably skill issue. Last jump way too high, landing cost a lot of speed too. Getting used to input lag is pain, so it's good enough.
Pac drive:
WR: no video
2nd: 2:27.xxx (100%)
My attempt: 2:29.064 (101.4%) - no cops, but smol crash, so I consider it balanced.
Barrage:
WR: no video
2nd: no video
3rd: 1:41.xxx (100%)
My attempt: 1:47.467 (106.4%) - w/o pushing, and worse water jump. Barrage felt the slowest on 30 FPS out of them all. It might be one of those vehicles that benefit greatly from curb boosting/suspension compaction. Idk. Would need a pusher to really see how it performs.