hein22

The thing here is the incoherence between PPLI and AWACS data transfer, that should be addressed soon so at least they are the same. If ED decides it is 100nm then 100nm it is, but coherently with each other.

Lol! I'm getting tired of talking about terrain database in the hornet, it's time ED clarifies this once and for all. But yes, hornet does have DTED instead of the DTSAS of the hog. Back to topic, I understand the bug now, and paradoxically it is exactly due to the fact I use to say that it isn't a bug. So it seems that the HMD LOS limitation are taking over a predefined tgt and clears its elevation data like it had beed created there in the first place, therefore jeopardizing the spot. Common bug in first stage of a feature.

I tried it and cannot reproduce. What is the issue exactly?

+1

This isn't a bug, it is due to the hmd LOS not being able to determine elevation at high ranges. There is a paper online explaining this, quite long.

Changing a waypoint also does this. This bug makes really difficult to operate in a complex combat environment.

Ok, it appears to be a bug for all sensors, not only the HMD.

When you command a markpoint with a tgt made by the hmd the tgt dissapears. Track attached. ag hmd mk bug.trk

yes you can

for the time it's taking to be up, I think it maybe contain ag hmd feature. Oh wait, no, that's my wish.

I don't see any reason why you would want to have that.

I strongly feel the same way. It is unacceptable that ED forces us to live FOR SO LONG with a very buggy sensor just because some day in the extremely long term we COULD have an improved FLIR coding. This practice applies to many more aspects in our customer experience.

I can't either. IMHO I think that if that diagram was applicable to radar ranging method then it'd be useless. On the other hand, I do not know exactly how narrow a mechanical radar is able to shoot a beam. But seeing the upper and bottom altitudes at 1BAR scan and 40nm range it would suggest very narrow.

I think it would be healthy if BN or ED could state if we are going to get TAMMAC and DTED modeled or not.

I think I was trying to ask about the TAMMAC and DTED features but I didn't clarify it, sorry I was a little sleepy. What does the dev team say about those?

Thanks BN. Have that moment occurred already? I think the answer given before not only doesn't make sense but also goes against the module fidelity, which if ED started to go that path then my intentions on future modules might change as well.

I agree. Without DTED our hornet will be nothing but a fast A-10A with radar. Not to mention that many current systems are using DTED like CCIP, TGP, etc. I just wish ED says something about this... someday.

Wait what? Our hornet DOES have DTED. When did ED say that? Link?

Press it longer and it will work

It only works if there are donors around. If you have no awacs will not show HAFUs unless L&S and DT2. F/F with AI is bugged right now and will only feed DL when in STT.

Good catch. A track will be needed though.

What refresh rate bug are you talking about? I didn't know of any and there are no mids refresh rate bugs discussed here.

Hey! I forgot to mention that the EW symbols do present this bug clearly (for ages now), as for the helmet I guess the report is done so if it's a bug and I'm wrong then it'll be fixed in two weeks.

Interesting! I didn't particularly find anything wrong in the video, so at least we know we are talking about different perspectives here. At the end they drifted heavily but I guess that's due to a refresh rate not being real time. I don't think there is anything wrong in your DCS, we just differ in our lens, which is totally fine.

Actually I didn't start anything nor stated that there is a bug at all. Just the way you explained things seemed strange to me. I guess I'm entitled to an opinion, no matter correct or not, otherwise this would not be a forum. Forgive me for my skepticism, I've seen many "real life" pilots here so I tend to take things carefully. Thank you for your reply.