#PAB-80 range are too low
24 messages · Page 1 of 1 (latest)
I fail to understand what the bug here is... Is it the range readouts?
the range ladder calculates max range based on factors like velocity and altitude, but actual range is consistently longer than what is shown
I concur. Pablo doesn't have it's own thrust so it will crash on the water if you launch them at that height and speed
but before it was shown like it has to be
yeah they redid the range tape calculations
and apparently it isn't mathing right for the 80LR
i've also found the range indicator slowly updating itself. occasionally i'd get range in yards (target in sight, more than 10 degrees below horizon, nose level) before slowly increasing to nmi a few seconds later
30km estimated range from less than 500 meters altitude at landing speeds is significantly more incorrect than the current estimates.
I'm also having this issue sometimes, I could be going 0.8 mach at like 1km altitude and sometimes it'll tell me that my glidebombs will only go an oddly specific very short distance (E.g. 457 meters, 283 meters, not actual numbers, but gives an idea). Makes me think the issue is to do with the new range/NEZ estimation. I find it happens a lot more often against air targets (don't ask why I'm dropping glide bombs on aircraft) than it does against ground targets, but can still happen. Like posted in here earlier, it seems to happen a lot more at low altitude.
FInd out one more thing about bug, sometimes when it displays max range like 500 meters, after you drop them they start self-destructing mid-air after flying like 400-600 meters
I'd had this issue tonight at 600 m/s and 2.5km altitude
same issue here. Said what I could in another thread from Reithan
I've been having the same issue in the latest update, weirdly specific hundreds of meters ranges on 80s despite then having them hit targets kilometers away