[INVESTIGATING]STT missing target extrapolation

while in STT, targets do not move smoothly (via extrapolation) accross the radar screen.

Instead, target motion appears as discrete jumps from position to position in both range and azimuth(when turning).

This becomes very noticeable at range scales below 20 miles.

Track previously posted:

https://forums.eagle.ru/attachment.php?attachmentid=232898&d=1587174323

The problem is not with extrapolation but with the draw rate of all HAFUs on both the radar and SA screens. I don't know why but the way it's coded means HAFUs are redrawn at a relatively slow refresh rate compared to something like bricks. I'll see if it can be fixed, it doesn't happen in the Viper.

The problem is not with extrapolation but with the draw rate of all HAFUs on both the radar and SA screens. I don't know why but the way it's coded means HAFUs are redrawn at a relatively slow refresh rate compared to something like bricks. I'll see if it can be fixed, it doesn't happen in the Viper.

I see. Yes, I dont see this in the viper either.

Indeed, I assume the devs ran into this limitation and once they got to the Viper they coded it in a better way that allows a smooth draw rate for all tracks. I'll definitely see if this can be improved.

The problem is not with extrapolation but with the draw rate of all HAFUs on both the radar and SA screens. I don't know why but the way it's coded means HAFUs are redrawn at a relatively slow refresh rate compared to something like bricks. I'll see if it can be fixed, it doesn't happen in the Viper.

Does this have anything to do with the datalink update rate I posted before? The outcome sounds the same, doesn't it?

Does this have anything to do with the datalink update rate I posted before? The outcome sounds the same, doesn't it?

Everything at 12 sec?:D j/k

Does this have anything to do with the datalink update rate I posted before? The outcome sounds the same, doesn't it?

Bump. I'm very interested in this question. What I posted about the 12 secs was wrong as proved by the community and Santi. But I wonder if it is related.

The problem is not with extrapolation but with the draw rate of all HAFUs on both the radar and SA screens. I don't know why but the way it's coded means HAFUs are redrawn at a relatively slow refresh rate compared to something like bricks. I'll see if it can be fixed, it doesn't happen in the Viper.

For off-board only HAFUs on the radar display (off-board tracks should still move smoothly in azimuth if ownship is changing heading) and for the SA page, I agree with you, there appears to be an issue with the draw rate.

But I'm thinking that the STT issue is different, because it's an on-board track and on-board tracks extrapolate properly in other radar modes besides STT.

The HAFUs move smoothly on the radar display in LTWS and TWS though. The issue appears only in STT mode.

For off-board only HAFUs on the radar display (off-board tracks should still move smoothly in azimuth if ownship is changing heading) and for the SA page, I agree with you, there appears to be an issue with the draw rate.

But I'm thinking that the STT issue is different, because it's an on-board track and on-board tracks extrapolate properly in other radar modes besides STT.

Yeah, the only case when they are smooth is when it's either a brick or an onboard HAFU outside of STT. It's pretty much the same bug with STT as you can see it updates at the same rate as the SA page when you turn. So whatever is making bricks and onboard HAFUs smooth in RWS/TWS is not working in STT or for offboard HAFUs.

Yeah, the only case when they are smooth is when it's either a brick or an onboard HAFU outside of STT. It's pretty much the same bug with STT as you can see it updates at the same rate as the SA page when you turn. So whatever is making bricks and onboard HAFUs smooth in RWS/TWS is not working in STT or for offboard HAFUs.