HUD closure rate

[derodo]

Is the closure rate displayed in the HUD (when you have a lock) working as expected?

 

I mean, I know it was broken in the past; and I'd swear I read it was fixed in some update. But it seems it's still off.

 

AFAIK, if I'm going faster than the target, the number displayed should be negative; and if the target is faster than me, the number should be positive, right? If that's the case, then it's still bugged; but maybe I just got it wrong.

[myHelljumper]

When closure rate is positive it means that you are closing, AFAIK it work as intended :)

[escaner]

The closure rate is the number to the left of the range scale? If so, sometimes it gives me weird reads to the point that I was doubting what it actually is.

 

I think it happens when closing in a bit fast to my locked target (more than 100KT closure, less than 1NM range): it then displays negative numbers and I was sistematically overshooting my leader in the campaign.

[myHelljumper]

The closure rate is the number to the left of the range scale? If so, sometimes it gives me weird reads to the point that I was doubting what it actually is.

 

I think it happens when closing in a bit fast to my locked target (more than 100KT closure, less than 1NM range): it then displays negative numbers and I was sistematically overshooting my leader in the campaign.

 

Yes, I see it too. The behavior might be realistic when in PID lock as the radar does not have continuous information, but in PIC the closure rate should be accurate.

[derodo]

Yeah I must be tripping when I wrote the post and siwtched postive/negative values.

 

Anyway, it seems the values shown are not consistent. I’ll try to have a closer look at it today; maybe it’s only when you are very close to the target as the other poster said.

[derodo]

Ok...I just checked again and I'm confused. Does the closure rate indication change sign depending on wether the target is hot/cold?

 

Targeted (TWS) my flight leader (mission 6 in the campaign), and I'm 100% sure the closure rate is negative when I'm closing in (going faster than him), and positive when I'm slower (and he's going away).

 

Didn't check against a hot target yet; I guess the actual indication on the HUD is the relative speed of the target with respect to me? That is, if he's cold and I'm following him faster, his_speed - my_speed will be negative (his_speed being positive as we're going in the same direction).

 

But then, if we're head on, how would that go? Will his_speed be negative (he's in the opposite direction), so his_speed - my_speed is still be negative? That would seem ok to me, but as myHelljumper said, if you're closing in, the closure rate is positive.

 

What am I missing here?

[jaguara5]

I have very often wrong closure rates during dogfights (don't know if this is CCM related).

As an example negative values while i obviously close in to the target.

So i don't rely on the indication but try to determine visually the situation.

[jaguara5]

Attatched are 2 screenshots I captured within 2 - 3 seconds in MP 5 min ago.

Negative value, target closing in (the 0.7 distance is the first picture, the 920 m the second as you can see form the event list on the left side). Happens all the time

Edited February 14, 2018 by jaguara5

[derodo]

I understand that might happen when dogfighting; if you’re pulling Gs the computatiions will vary wildly. That’s fine. I don’t usually look at the values in that situation.

 

The thing is you will still get negative closing values when flying level, no Gs, no ECM. I’m just targeting the flight lead in front of me, and the readings are conistent and steady. If I’m closing in, they are negative; if he’s going away, they’re positive.

 

Is that the expected behavior?

[jojo]

I understand that might happen when dogfighting; if you’re pulling Gs the computatiions will vary wildly. That’s fine. I don’t usually look at the values in that situation.

 

The thing is you will still get negative closing values when flying level, no Gs, no ECM. I’m just targeting the flight lead in front of me, and the readings are conistent and steady. If I’m closing in, they are negative; if he’s going away, they’re positive.

 

Is that the expected behavior?

 

No, it should be the opposite.

 

And it works fine for me when I'm closing in on the tanker (positive value).

[derodo]

Ok, I think I know what's going on; or at least It can be reproduced.

 

Take off behind the leader, turn on radar, wait for it to show, and lock it once (TWS); as long as you keep it locked in TWS the closure rate readings are negative; lock again to switch to STT, and then the closure rate goes positive.

 

I have a track file, but it's 12MB and I can't attach it, so I uploaded it to WeTransfer (https://we.tl/AVQ6hWhEPe). Skip to take-off; you can see how the closure rate reading changes sign as I switch back and forth from TWS to STT.

 

Maybe that's how it is IRL; I don't know (it seems odd if it is though :)

[escaner]

I checked it too and weird readings only happened in TWS at close range. Beyond 1-2 NM, they are OK, but less precise than in STT. In this last mode, it was always fine, even at very close range.

[myHelljumper]

I checked it too and weird readings only happened in TWS at close range. Beyond 1-2 NM, they are OK, but less precise than in STT. In this last mode, it was always fine, even at very close range.

 

To me it could be realistic, but overdone.