VarZat Posted January 30, 2023 Posted January 30, 2023 So when doing Low level, or even high level bombing profiles and attacks, i find the ranging in the HUD is inaccurate, most likely because it stems from where either the TGP or radar is looking, but not the actual range to steerpoint. This makes it so that i have to look at the EHSI to give me the ranging i want. This is very unpractical, as i have to be heads down, when i really want to be looking for terrain, my wingman, and the target. Is there a way to change this?
llOPPOTATOll Posted January 31, 2023 Posted January 31, 2023 Look for the XXX>XXX The Xs to the left of the > indicate the range to the current steerpoint. The Xs to the right of the > indicates the current steerpoint. Say for the example of 30>003 you can think of it like theres 30nm -> stpt3 to remember which number is which
VarZat Posted January 31, 2023 Author Posted January 31, 2023 5 hours ago, llOPPOTATOll said: Look for the XXX>XXX The Xs to the left of the > indicate the range to the current steerpoint. The Xs to the right of the > indicates the current steerpoint. Say for the example of 30>003 you can think of it like theres 30nm -> stpt3 to remember which number is which Problem with this is it rounds up to the closest full number or something like that, so if im doing a popup at 6,3 NM, it wouldnt work.
Lace Posted January 31, 2023 Posted January 31, 2023 5 hours ago, VarZat said: Problem with this is it rounds up to the closest full number or something like that, so if im doing a popup at 6,3 NM, it wouldnt work. That's what VIPs and VRPs are for. 1 Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs, pit WIP (XBox360 when traveling). Quest 3S. Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.
_SteelFalcon_ Posted January 31, 2023 Posted January 31, 2023 38 minutes ago, Lace said: That's what VIPs and VRPs are for. This.
AvroLanc Posted January 31, 2023 Posted January 31, 2023 6 hours ago, VarZat said: Problem with this is it rounds up to the closest full number or something like that, so if im doing a popup at 6,3 NM, it wouldnt work. You get a decimal distance x.x anytime the distance to the current SPI (you want a pre planned Steerpoint here) is less than 10nm. Look for BX.X in the lower right data block. Make sure you Cursor Zero. You can set up a PUP with either VIP or VRP, but this isn’t strictly needed for what you want.
VarZat Posted January 31, 2023 Author Posted January 31, 2023 12 minutes ago, AvroLanc said: You get a decimal distance x.x anytime the distance to the current SPI (you want a pre planned Steerpoint here) is less than 10nm. Look for BX.X in the lower right data block. Make sure you Cursor Zero. You can set up a PUP with either VIP or VRP, but this isn’t strictly needed for what you want. Yes, but the problem with this is that it is not accurate. I dont know if it is a bug or not, but the range i am looking for is only on the EHSI. I definitly prefer using VIP or VRP, i am trying to get better at doing them more on the fly without having to do alot of planning.
AvroLanc Posted January 31, 2023 Posted January 31, 2023 1 hour ago, VarZat said: Yes, but the problem with this is that it is not accurate. I dont know if it is a bug or not, but the range i am looking for is only on the EHSI. I definitly prefer using VIP or VRP, i am trying to get better at doing them more on the fly without having to do alot of planning. Ok, so the Bx.x range in the hud is slant range, rather than ‘along ground’ range - is that your issue? But you said you were doing low level, so effectively they are going to be very similar. I’m not sure why you want to be looking at the EHSI during a low level attack when the same information is presented better elsewhere.
VarZat Posted January 31, 2023 Author Posted January 31, 2023 33 minutes ago, AvroLanc said: Ok, so the Bx.x range in the hud is slant range, rather than ‘along ground’ range - is that your issue? But you said you were doing low level, so effectively they are going to be very similar. I’m not sure why you want to be looking at the EHSI during a low level attack when the same information is presented better elsewhere. They are similar but not similar enough. I find i always ended up crooked when i looked at the range in the HUD, or "slant range" (range with altitude difference added?) The target might be at another elevation even though i am running in low, which is probably what gets me crooked. Especially when doing high altitude dive bomb attacks at 20000FT this difference starts becoming very big. So that is the reason i have to look at the EHSI instead of looking at the HUD which is what i really want to be looking at.
Recommended Posts